Skip to main content
Glama
Sign In

Courier

by io.github.trycourier
OverviewDiscussionsAdmin

get_routing_strategy

Read-only

Retrieve a routing strategy by ID. Returns the full entity including routing, channels, and providers.

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": {
      "routing_strategy_id": "<routing_strategy_id>"
    },
    "name": "get_routing_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
routing_strategy_idYesThe routing strategy ID (rs_ prefix)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds value by disclosing the return payload composition (routing, channels, providers) beyond what annotations provide, which helps predict behavior. No contradiction with annotations.

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?

A single sentence that front-loads the verb and resource, then adds one useful clause about return contents. No filler, no repetition of schema details, and highly scannable for an agent.

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 simple 1-parameter read operation with a readOnly annotation, the description covers the operation, the identifier to supply, and the expected return contents. Nothing an agent needs to invoke it correctly is missing, especially given the absence of an output schema is mitigated by the stated return structure.

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 coverage is 100%, with the parameter documented as 'The routing strategy ID (rs_ prefix)'. The description's 'by ID' adds no substantive meaning beyond the schema, so the baseline score of 3 applies.

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?

States the specific verb 'Retrieve', the resource 'routing strategy', and the retrieval key 'by ID', which distinguishes it from list and archive siblings. It also specifies the return composition ('routing, channels, and providers'), making the tool's scope clear.

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?

The phrase 'by ID' implies the use case: when an agent has a known routing strategy ID and wants the full entity. However, it provides no explicit exclusions or alternatives, such as recommending list_routing_strategies to discover IDs first.

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

All Courier toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources