delete_data_source
Delete a data source from a project
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | The anonymous session ID | |
| data_source_id | Yes | The ID of the data source to delete |
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 available, and the description only states the core action. It omits important behavioral details such as whether deletion is permanent, if permissions are required, or potential side effects. This leaves the agent without critical safety context.
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 redundancy. It is front-loaded and efficient, making it easy to parse quickly.
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?
With no annotations and no output schema, the description is the only source of context. It does not mention return behavior, error cases, or what happens to associated data. Given this is a deletion operation, more context is needed for safe and correct usage.
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?
The schema covers 100% of parameter descriptions, so the baseline is 3. The description adds no extra parameter meaning; it only repeats 'data source' and 'project' without explaining session_id or data_source_id semantics beyond the schema.
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 explicitly states 'Delete a data source from a project' with a clear verb ('Delete') and specific resource ('data source'). This distinguishes it from sibling tools like 'delete_tool' 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 provided on when to use this tool versus alternatives, or any prerequisites or exclusions. The description merely states the action without context that would help an agent decide between this and sibling delete tools.
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.