Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

standard_routing_get

Retrieves the standard routing for a specific entry using its ID, enabling clients to look up routing details for a given record.

Instructions

Get the Standard Routing for a particular entry by specifying its ID.

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": "standard_routing_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStandard routing ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/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. 'Get' reasonably signals a non-mutating lookup, but the description says nothing about what happens when the ID does not exist, whether the returned routing includes its operations/steps, or any permission requirements.

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?

One sentence, front-loaded with the verb and resource, with no filler or hedging. The trailing 'by specifying its ID' is mildly redundant given the schema already requires an id, which keeps it just shy of a 5.

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?

For a one-parameter read lookup with full schema coverage, no annotations, and no output schema, an agent has everything needed to invoke it correctly. The remaining unknowns (return shape, not-found behavior) are modest for a simple getter and would be visible in the response.

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 a single required 'id' string already documented in the schema. The phrase 'by specifying its ID' restates rather than extends that, adding no format, source, or validation detail beyond the structured field.

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 ('Get') and a specific resource ('Standard Routing') scoped to a single record identified by ID. That single-record retrieval framing implicitly separates it from standard_routing_find (search) and standard_routing_create, though it never names either sibling.

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: an agent can infer it should call this when it already has a routing ID. There is no explicit statement of when to prefer this over standard_routing_find or what to do when the ID is unknown, so the routing decision is left to inference.

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