Skip to main content
Glama

Typebar (formerly SuperDocs)

delete_user_template

Soft-deletes the template; only the owner (user or organization) can delete. Once deleted, the template no longer appears in list_user_templates and cannot be referenced by the AI for new documents. Existing documents already drafted from the template are unaffected.

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": {
      "template_id": "<template_id>"
    },
    "name": "delete_user_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/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 and does substantial work: soft-delete semantics, ownership authorization, disappearance from list_user_templates, and unavailability to the AI for new documents. It also clarifies the blast radius ('Existing documents already drafted... are unaffected'). The main unexplained trait is whether a soft delete can be undone and what happens on a non-owner call.

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?

Three compact sentences, each carrying distinct information: what happens, who may do it, and what the consequences are. The core action is front-loaded with zero preamble.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter mutation with no annotations and no output schema, the description covers effect, authorization, and side effects well enough to call it safely. Restorability and failure behavior remain unstated, which is a real but modest gap at this complexity level.

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 0% — template_id is an untyped title with no description — so the description is the only source of meaning. It gestures at template identity by referencing list_user_templates (the likely source of the ID) but never states the ID format or how to obtain it, leaving half the gap unfilled.

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?

Opens with a specific verb+resource combination ('Soft-deletes the template') that also encodes an important semantic detail — the delete is soft, not hard. It further distinguishes itself from the sibling list_user_templates by naming it as the surface where the deleted template disappears, so an agent can place the tool without reading the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the precondition explicitly ('only the owner (user or organization) can delete'), which tells the agent when the call will succeed. It does not name an alternative/restore path, but no competing delete tool exists among the siblings, so the routing gap is minor.

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.