Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_route_delete

Delete a static route from the routing table. Apply changes with opnsense_route_apply to activate.

Instructions

Delete a static route. Run opnsense_route_apply afterwards to activate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesUUID of the route to delete

Implementation Reference

  • Handler for opnsense_route_delete: parses args with DeleteRouteSchema (expects UUID), then calls POST /routes/routes/delroute/{uuid} to delete the static route.
    case "opnsense_route_delete": {
      const { uuid } = DeleteRouteSchema.parse(args);
      const result = await client.post(`/routes/routes/delroute/${uuid}`);
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
  • DeleteRouteSchema: Zod schema validating that the input contains a 'uuid' field matching the UUID format.
    const DeleteRouteSchema = z.object({
      uuid: UuidSchema,
    });
  • Tool definition registration for 'opnsense_route_delete' - defines name, description, and input schema (uuid required).
    {
      name: "opnsense_route_delete",
      description:
        "Delete a static route. Run opnsense_route_apply afterwards to activate.",
      inputSchema: {
        type: "object" as const,
        properties: {
          uuid: { type: "string", description: "UUID of the route to delete" },
        },
        required: ["uuid"],
      },
    },
  • src/index.ts:67-67 (registration)
    Binding the routing tool definitions (including opnsense_route_delete) to the handleRoutingTool handler in the central toolHandlers map.
    for (const def of routingToolDefinitions) toolHandlers.set(def.name, handleRoutingTool);
  • UuidSchema helper used by DeleteRouteSchema to validate the UUID input parameter.
    export const UuidSchema = z
      .string()
      .uuid("Invalid UUID format");
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the need to apply after deletion, which is a behavioral trait. However, it omits details like irreversibility or impact on active routes.

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 sentences, front-loaded with the action, no unnecessary words.

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?

Adequately covers action and follow-up for a simple delete tool with one parameter and no output schema. Could mention permanence or prerequisites.

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?

The description adds no meaning beyond the input schema, which already fully documents the uuid parameter. Baseline 3 applies due to high schema coverage.

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?

The description clearly states 'Delete a static route', using a specific verb and resource, which distinguishes it from sibling tools like add, update, list, and apply.

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?

It provides clear guidance by instructing to run opnsense_route_apply afterwards to activate, but does not explicitly exclude other uses or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/itunified-io/mcp-opnsense'

If you have feedback or need assistance with the MCP directory API, please join our Discord server