Skip to main content
Glama

thanaton_manage_routes

List, set, or delete edge routing rules, redirects, and HTTP security headers for a project. Use it to control URL rewrites, redirect status codes, and response headers.

Instructions

List, set, or delete edge routing rules, rewrites, custom redirects, and HTTP security headers.

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_id": "<project_id>",
      "action": "<action>"
    },
    "name": "thanaton_manage_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoRoute rule type (default: rewrite)
actionYesAction to perform
sourceNoIncoming path regex or pattern (for set, e.g. /api/(.*))
statusNoHTTP redirect status code (e.g. 301, 302, 307, 308)
route_idNoRoute ID (required for delete)
project_idYesTarget project ID
destinationNoTarget URL or rewrite path (for set, e.g. /$1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It signals that set and delete mutate state, but says nothing about permissions, whether set overwrites existing rules, whether delete is irreversible, or what a list returns. For a three-action mutation tool with zero annotation coverage, this is a significant gap.

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

Conciseness4/5

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

A single front-loaded sentence with the verb list leading, which lets an agent grasp the action space immediately. It is efficient, though the enumeration of rule types is slightly redundant with the type enum in the schema.

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?

Seven parameters across three actions with no annotations and no output schema demand more than one sentence. The description never states the action-dependent requirements (route_id for delete; source, destination, and status for set) or what listing returns, leaving the agent to reconstruct call shape from the schema alone.

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%, so every parameter already has documented semantics including enums and per-action usage notes. The description only restates the resource families that map to the type enum and adds no format or behavioral nuance beyond the schema, which sets the baseline at 3.

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 gives specific verbs (list, set, delete) against a specific resource (edge routing rules, rewrites, redirects, HTTP security headers), which is enough to separate it from siblings like thanaton_manage_domains or thanaton_configure_waf. It stops short of stating scope details such as whether rules are per-project or global, so it does not reach a 5.

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?

No guidance on when to choose this tool over alternatives, no prerequisites, and no exclusions. The description does not explain when a redirect belongs here versus configure_waf or manage_domains, even though those siblings plausibly overlap on headers and host-level routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools