Skip to main content
Glama

Delete resource

delete_resource
Destructive

Remove a resource from a project; the events that took it no longer do. Anybody who may write in the project.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "id": "<id>"
    },
    "name": "delete_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe resource's id.
projectYesThe project key, e.g. TH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered structurally. The description adds the authorization requirement ('Anybody who may write in the project'), which is genuinely useful context not in the schema. However, the claimed side effect on events is phrased so poorly that an agent cannot tell whether related events are deleted, orphaned, or preserved, leaving reversibility and cascade behavior unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the action, which is good, but the second clause is ungrammatical and fails to convey its point economically, so brevity here comes at the cost of clarity rather than from it.

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?

For a destructive, irreversible-looking mutation with two required parameters and no output schema, the description should state consequences (what happens to dependent events), irreversibility, and any error behavior. It gestures at consequences but does so unintelligibly, and says nothing about reversibility or outcome.

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 coverage is 100%, with both required parameters (id, project) fully documented in the schema, so the baseline is 3. The description's phrase 'from a project' loosely echoes the project parameter but adds no format, scope, or validation detail beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource combination ('Remove a resource from a project') identifies the object, but the following clause ('the events that took it no longer do') is garbled and obscures rather than clarifies what deleting actually means. An agent can guess the intent from the name and title, but the description itself doesn't cleanly differentiate this from the many sibling delete_* tools.

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?

There is no when-to-use guidance, no alternatives named (e.g. set_resource vs delete_resource), and no preconditions beyond the permission note. 'Anybody who may write in the project' describes who can call it, not when to call it.

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.

Resources