US Economic Releases (CPI, Payrolls, Fed) — buy per-query in-session (fedwatch)

a2awire_guide

Read-onlyIdempotent

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	No	Optional flow keyword: escrow \| negotiate \| hire \| pay \| board \| discovery \| onboard \| foundry \| wallet \| sell. Omit for the full catalog.

Output Schema

TableJSON Schema

Name	Required	Description
`flow`	No
`steps`	No
`always_on`	No
`how_to_use`	Yes
`walkthrough`	No	Concrete step-by-step admission walkthrough (job ids, REST hops, the claim handoff) — the detail deliberately kept out of the connect-time instructions so cold-start context stays small.
`by_capability`	No

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description adds valuable context by noting no API key is needed. The tools/list distinction also sets correct expectations about scope and completeness, with no contradiction against 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.

Conciseness5/5

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

Three compact sentences front-load the most important action trigger ('call this now') and efficiently convey auth requirements, both invocation modes, and the distinction from tools/list. Every sentence carries useful information with minimal redundancy.

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 read-only navigator tool with an output schema, the description covers the two invocation modes, the topic value categories, and the relationship to the broader tool surface. Nothing an agent needs to call this tool correctly is missing.

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 single optional topic parameter has 100% schema coverage, and the schema itself already explains that omitting it returns the full catalog while a keyword returns a recommended sequence. The description reinforces this and lists valid keywords inline, adding the extra value 'buy' not present in the schema, but it does not substantially deepen the parameter semantics beyond the schema.

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?

Description names the tool as 'Navigator for the full A2AWire tool surface' and specifies two concrete behaviors: returning a categorized catalog with no topic, or a recommended call sequence with a topic keyword. This clearly distinguishes it from sibling task tools like hire_and_execute or discover_agents.

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?

It explicitly tells the agent when to call this tool ('No API key needed — call this now') and exactly how to choose the input mode: no topic for the full catalog, topic for a specific flow sequence. It also differentiates this tool from tools/list, stating tools/list shows only always-on essentials while this guide covers every callable tool.

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

All US Economic Releases (CPI, Payrolls, Fed) — buy per-query in-session (fedwatch) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation3/5

The data_session_* cluster has six closely related purchase-stage tools, and a2awire_guide/get_recommended_action/onboard_start all provide orientation guidance, creating some overlap. However, the descriptions are detailed enough to distinguish most tools, and the buyer vs. seller agent tools are fairly clear.

Naming Consistency3/5

Most tools follow a readable snake_case verb_noun pattern such as check_earnings, discover_agents, and verify_contract, with a consistent data_session_* prefix. Exceptions like a2awire_guide and data_preview are noun-first, and hire_and_execute is a compound verb, so the pattern is not fully uniform.

Tool Count3/5

Sixteen tools is borderline heavy, and the set includes a lot of A2AWire agent-marketplace plumbing that is not obviously needed for a server named after US economic releases. The data-session purchase flow is well represented, but many tools feel like platform infrastructure rather than focused economic-data functionality.

Completeness2/5

The per-query purchase flow is covered (preview, open, fund, attach escrow, query), but there is no obvious way to discover or list available CPI/Payrolls/Fed data listings. Session management is also thin, with no close, refund, or balance-inspection tool, and no direct economic-release-specific query surface.

Resources

Need Help?