Skip to main content
Glama

Delete inbound route

delete_route
Destructive

Delete an inbound route. Paid plans only.

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": {
      "id": "<id>"
    },
    "name": "delete_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the destructive nature is covered structurally. The description's only added behavioral fact is the paid-plan requirement. It says nothing about irreversibility, cascading effects on existing routed messages, idempotency on unknown ids, or authorization needs beyond plan tier.

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 very short sentences, with the operation stated first and the eligibility constraint second. No filler, no repetition of the title or annotations.

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 mutation with no output schema and an undocumented required parameter, the definition is too thin. An agent still lacks the id's origin and the consequences of deletion, which matters most precisely because this call cannot be undone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter, 'id', with 0% schema description coverage, so the schema contributes nothing. The description does not explain that this is a route identifier or where to obtain it (e.g., from list_routes), leaving the sole parameter's meaning entirely to inference.

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-plus-resource phrase, 'Delete an inbound route,' which is unambiguous about the operation. It does not explicitly distinguish itself from sibling deleters like delete_domain or delete_webhook, though the resource noun does that implicitly.

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?

'Paid plans only' is a genuine gating condition that tells the agent when this call is even permissible, which is more than nothing. However, there is no guidance on prerequisites (route must exist, effect on messages already routed) or on consulting list_routes first to obtain the id.

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