ESA MCP Server

route_delete

Remove a specified route from an Edge Routine to manage routing configurations and maintain security policies.

Instructions

Delete a specified route associated with an Edge Routine (ER).

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": {
      "siteId": "<siteId>",
      "configId": "<configId>"
    },
    "name": "route_delete"
  }
}

Input Schema

Name	Required	Description	Default
`siteId`	Yes	The ID of the site
`configId`	Yes	The ID of the config

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a deletion operation, implying it's destructive, but doesn't specify if the deletion is permanent, reversible, requires specific permissions, or has side effects (e.g., impacting associated configurations). This is a significant gap for a mutation tool.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action ('Delete') and resource, making it easy to scan and understand quickly.

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?

Given this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks critical details like what happens post-deletion, error conditions, or confirmation requirements, which are essential for safe and effective use by an AI agent.

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 the schema fully documents the two required parameters (siteId and configId). The description adds no additional meaning beyond implying these parameters identify the route to delete, which is already clear from the schema. This meets the baseline for high coverage.

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 clearly states the action ('Delete') and the resource ('a specified route associated with an Edge Routine'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'route_update' or 'route_get', which would require mentioning it's specifically for removal rather than modification or retrieval.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing route), exclusions, or related tools like 'route_create' for creation or 'route_get' for checking before deletion, leaving usage context implied at best.

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