MiniMax-AI / MiniMax-AI/MiniMax-Coding-Plan-MCP
The MCP tool descriptions should not try to steer the client agent
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 102
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Right now, the MCP's tool descriptions say the client agent MUST (!!!) use its tools, which is crazy. As a user, I like to have the MCP tools available but I don't want the tools telling me I MUST use them. The tool descriptions should only describe the tool capabilities, and not try to steer the behaviour of the client agent.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file or test; start by locating the MCP server's tool registration and description definitions. Review each affected description and ensure it states capabilities without directing the client agent's behavior, then verify the resulting descriptions no longer contain mandatory-use language.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100