delete_bind
Deletes a specified key binding from DDNet game configuration, solving the need to remove unwanted key mappings.
Instructions
删除bind
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| bindkey | Yes |
Deletes a specified key binding from DDNet game configuration, solving the need to remove unwanted key mappings.
删除bind
| Name | Required | Description | Default |
|---|---|---|---|
| bindkey | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fails to disclose any behavioral traits such as irreversibility, scope of deletion, or potential side effects; it only states the action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely brief but at the expense of completeness; the single sentence is tautological and provides no useful information, making it under-specified rather than concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete tool with one parameter, the description should at least clarify what 'bindkey' represents and the effect of deletion; it does neither, leaving the agent uninformed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The parameter 'bindkey' is completely unexplained despite 0% schema coverage; the description adds no meaning beyond the raw JSON schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description '删除bind' is a direct tautology of the tool name 'delete_bind', restating the verb and resource without adding new information.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus siblings like add_bind or check_bind; no context for when deletion is appropriate or what prerequisites exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SilverHi/ddnet-mcpserver'
If you have feedback or need assistance with the MCP directory API, please join our Discord server