delete_tool
Delete a tool from a project
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tool_id | Yes | The ID of the tool to delete | |
| session_id | Yes | The anonymous session ID |
try
by md.install
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the action 'Delete' but does not disclose irreversibility, cascading effects, or permission requirements. For a destructive operation, additional behavioral context is needed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence with no filler or redundant phrasing. It is appropriately sized for a straightforward tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has low complexity with two parameters and no output schema, but it is destructive. The description omits important context like permanence of deletion, relationship of session_id to the project, or potential impact on related data, leaving the agent under-informed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline of 3 applies. The description adds no extra meaning beyond what the schema already provides for tool_id and session_id; 'from a project' is vague relative to the actual session_id param.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Delete' and identifies the resource ('a tool') along with scope ('from a project'), which clearly distinguishes it from sibling tools like delete_data_source and delete_project.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives like toggle_tool or update_tool. There are no prerequisites, exclusions, or context to help decide the appropriate tool beyond what the name implies.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.2/5.0
Disambiguation4/5
Most tools are clearly distinct, targeting specific resources (projects, data sources, tools) and actions (add, create, delete, update). Slight overlap exists between toggle_tool and update_tool, and between add_data_source and add_tool, but descriptions clarify the differences.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with snake_case, such as add_data_source, create_project, delete_tool, and reorder_steps. No mixing of conventions or vague verbs.
Tool Count5/5
13 tools is within the ideal range for a project management server. Each tool serves a clear purpose in managing projects, data sources, tools, and sessions, without unnecessary redundancy.
Completeness4/5
Core CRUD operations are covered for projects and tools, with additional operations like reorder and toggle. Minor gaps exist: data sources lack an update operation, and there's no explicit list/get for tools or data sources, but project details likely cover this.