Skip to main content
Glama

federation_read

Read-onlyIdempotent

Run a free read without a confirmation (CO 756): catalog, inventory, bookings, your orders. Addressing, schemas and authority are exactly federation_act's. A write, a priced tool or an open-web tool is refused with not_a_read: call it through federation_act, which asks first. 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

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses the confirmation-gating difference from federation_act, the refusal error code not_a_read, and that the result is the inner tool's own output passed through. It does not explain what other failure modes return or how nested arguments are validated, but the behavioral contract that determines tool choice is clear. No contradiction with the annotations.

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?

The routing rule and refusal behavior are front-loaded, and the return contract plus example are packed into short clauses with no filler. Density is high and the internal reference '(CO 756)' adds little for an agent, but no sentence is wasted.

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?

For a three-parameter dispatcher with a nested arguments object and no output schema, the description covers what gets returned, when it is refused, and whose addressing rules apply. Remaining gaps — error shapes for non-not_a_read failures and behavior when tenant_id is supplied for a root tool — are minor given the schema's own tenant_id documentation.

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 each parameter (tool, arguments, tenant_id) is already documented in the schema, and the description defers to federation_act for addressing/tenant semantics rather than re-explaining them. The inline example clarifies that 'arguments' carries the inner tool's payload, which is a small value-add, but no additional constraint or format detail is provided. Baseline 3 is appropriate.

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?

States a specific verb and scope ('run a free read without a confirmation') and enumerates the covered domains: catalog, inventory, bookings, your orders. It explicitly distinguishes itself from federation_act by saying addressing, schemas and authority match that tool. The only slight weakness is that the underlying resource is indirect (it dispatches an inner tool), so the purpose is described by delegation rather than by a single concrete resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both the when ('free read without a confirmation') and the when-not ('a write, a priced tool or an open-web tool is refused with not_a_read'), plus the exact alternative to use in that case ('call it through federation_act, which asks first'). Nothing is left for the agent to infer about routing.

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.