delete_material
Deletes a material by its unique ID. Provide the material ID to remove it from the system.
Instructions
Delete a material.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID of the material to delete |
Deletes a material by its unique ID. Provide the material ID to remove it from the system.
Delete a material.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID of the material to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not add any behavioral information beyond what the annotations already provide (destructiveHint=true, idempotentHint=true). It does not disclose whether deletion is permanent or soft, or any cascading effects.
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?
The description is a single, clear sentence with no unnecessary words. It is maximally concise while conveying the essential purpose.
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?
Given the simplicity of the tool (single parameter, no output schema), the minimal description is adequate but does not exceed expectations. It provides the bare minimum needed to understand the operation.
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 input schema covers the single parameter 'id' with a description, achieving 100% coverage. The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.
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 clearly states the action (delete) and the resource (material), which is sufficient to identify the tool's purpose. It distinguishes itself from sibling delete tools by the specific resource type.
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?
The description provides no guidance on when to use this tool versus alternatives, such as delete_material_group or other delete operations. No context about prerequisites or side effects is given.
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/martijnpieters/eduframe-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server