Skip to main content
Glama

Coline

Delete event template

delete_event_template
DestructiveIdempotent

Deletes an event template. Events made from it stay.

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": {
      "workspace": "<workspace>",
      "templateId": "<templateId>"
    },
    "name": "delete_event_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
templateIdYesTemplate id from list_event_templates.

Output Schema

NameRequiredDescriptionDefault
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds a genuinely non-obvious consequence beyond them: events already created from the template remain in place. It does not say whether the action is reversible or what happens to a template's attachment-style associations, which keeps it from a 5.

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?

Two short sentences, zero filler, with the operation stated first and the important consequence second. Nothing is buried or repeated.

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

Completeness5/5

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

An output schema exists and both required parameters are fully documented in the schema, while annotations carry the destructive/idempotent semantics. Combined with the description's note that existing events persist, an agent has everything needed to call it correctly.

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%, with both workspace and templateId documented in the schema including where to source them (workspaces.list, list_event_templates). The description adds no parameter meaning beyond that, so the baseline 3 applies.

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

Purpose4/5

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

The description uses a specific verb and resource ("Deletes an event template") and the second clause implicitly separates it from delete_event by clarifying that instances survive. It stops short of naming sibling tools like update_event_template or delete_event outright, so an agent still infers the boundary rather than being handed it.

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

Usage Guidelines3/5

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

Usage is only implied: the tool is for removing a template, and the reassurance about existing events hints that it is safe when you want to stop future use rather than clean up existing events. There is no explicit when-to-use, when-not-to-use, or pointer to create_event_template / update_event_template as alternatives.

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