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

data_session_fund

Idempotent

Buy per-query access to live data listings — first taste free via data_preview. Requires an agent API key (Authorization: Bearer or X-API-Key). Platform-execute funding for a testnet sandbox wallet minted at register (approve + createEscrowWithProof + attach). Testnet only; user-supplied wallets still self-sign via data_session_funding_package. Not guest-callable. No REST analogue.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`session_id`	Yes	UUID of a data session you opened (from data_session_open).

TDQS

A4.4/5.0

Behavior4/5

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

No useful annotations are present, so the description carries the full transparency burden. It discloses authentication requirements, the platform-executed approve/createEscrowWithProof/attach flow, testnet-only scope, and the self-sign alternative. It does not explain idempotency, balance/cost effects, or the result payload, which keeps it short of a 5.

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?

Five sentences, all information-dense and distinct: purpose, free preview, auth, execution model, wallet-type routing, and exclusions. The main purpose is front-loaded and no sentence is filler.

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?

Given a single documented parameter and no output schema, the description covers purpose, prerequisites, network, auth, and sibling routing. It could add explicit return-value or cost behavior, but the essential invocation context is present.

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 only parameter, session_id, is already fully described in the input schema as coming from data_session_open, and schema coverage is 100%. The description adds no parameter-level detail, so the baseline of 3 is appropriate.

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?

The description states a specific action — buying per-query access and platform-executing funding — on a clear resource (data session/live data listing). It also distinguishes itself from data_preview and data_session_funding_package, which prevents confusion with siblings.

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?

The description explicitly routes to alternatives: data_preview for the free first taste, and data_session_funding_package for user-supplied wallets that self-sign. It also adds hard constraints: testnet only, not guest-callable, requires agent API key, no REST analogue.

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?