Skip to main content
Glama

federation_read

Read-onlyIdempotent

A free read with no confirmation (CO 756), addressed like federation_act; a write or priced tool answers not_a_read. Buying for someone? First read order_quote, arguments {"items":[{"product_id":"","quantity":1}]}: price, stock, which of YOUR tenants can pay in Coms, the pay link. Returns: The inner tool's own result, or not_a_read. Example: call federation_read with arguments {"tool":""}.

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": {
      "tool": "<tool>"
    },
    "name": "federation_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesThe read to run, e.g. 'catalog_search'.
argumentsNoThe inner tool's own arguments.
tenant_idNoThe tenant, for a branched platform tool; omit for a root tool. As federation_act.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: no confirmation prompt, the not_a_read rejection path for non-read targets, and that the return value is the inner tool's own result. It does not cover errors beyond not_a_read, but that is a minor gap given the annotation coverage.

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

Conciseness3/5

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

The opening clause and the returns statement are front-loaded and useful, but the middle 'Buying for someone?' passage injects a different tool's argument example into this tool's definition, interrupting the flow. Several parenthetical codes (CO 756, Coms) are not explained and add length without clarity.

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?

With no output schema, the description correctly states that the result is the inner tool's own output. It covers the read-only contract, the rejection behavior, and the dispatch shape. The main shortfall is that the order_quote digression muddies rather than completes the picture for a dispatcher tool.

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%, so 'tool', 'arguments', and 'tenant_id' are already documented in the schema, making 3 the baseline. The description adds an example call shape and clarifies that arguments is passed through verbatim to the inner tool. However, the embedded order_quote JSON sits ambiguously between the two tools and risks being read as this tool's own argument example.

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 states a specific behavior: it performs a free read (no confirmation) by dispatching an inner tool addressed the same way as federation_act, and returns that inner tool's result. This distinguishes it from the sibling federation_act, which handles writes. Jargon such as 'CO 756' and 'not_a_read' adds noise but the core verb+scope is legible.

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 explicitly routes the agent: use this for reads; a write or priced tool responds with not_a_read, so those belong elsewhere. It also advises reading order_quote first when buying for someone. The guidance is concrete, though the order_quote detour is only loosely connected to this tool's own purpose.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources