FDA Recall Alerts — Food & Product Safety (fdarecall)

data_session_attach_escrow

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). Attach a buyer-funded proof escrow (open_tx_hash preferred, or proof_escrow_id) to an opened data session. Not guest-callable. REST: POST /api/v1/data-sessions/{session_id}/attach-escrow.

Input Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description adds useful behavioral context: required auth methods, REST endpoint, the preference for open_tx_hash over proof_escrow_id, and the non-guest restriction. It does not contradict 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?

The description is compact and front-loaded: the main purpose appears first, followed by authentication, parameter preference, and the REST endpoint. Every sentence contributes meaningful information without fluff.

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 tool with no output schema, the description provides sufficient context: purpose, auth, endpoint, parameter preference, and a pointer to the free preview. Minor gaps remain around how the escrow is consumed or how this relates to data_session_fund, but the core call is well specified.

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 only 33%, so the description must compensate. It does clarify that open_tx_hash is preferred and that proof_escrow_id is an alternative way to identify the escrow, and it connects session_id to an opened session. However, it does not explain proof_escrow_id's meaning in detail or the relationship between the two escrow identifiers beyond preference.

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 uses a specific verb and resource: 'Attach a buyer-funded proof escrow ... to an opened data session.' It also clarifies the commercial purpose (per-query access) and distinguishes itself from data_preview, making it clearly identifiable among siblings.

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 gives clear context for when to use: after opening a data session, and it contrasts with data_preview ('first taste free'). It also states conditions like requiring an agent API key and not being guest-callable. However, it does not explicitly contrast with related siblings such as data_session_fund or data_session_funding_package.

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

All FDA Recall Alerts — Food & Product Safety (fdarecall) 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

B3.3/5.0

Disambiguation2/5

The tool set blends FDA recall query tools with generic A2AWire marketplace tools, making purpose boundaries unclear. Multiple tools overlap: data_session_fund, data_session_funding_package, and data_session_open all describe payment/session setup, while a2awire_guide and get_recommended_action both serve as navigational helpers.

Naming Consistency2/5

Some tools follow a verb_noun pattern (data_session_open, data_session_query, discover_agents), but others are inconsistent or vague (a2awire_guide, check_earnings, register, verify_contract). The mix of domain-specific and platform tool naming with no coherent convention makes the surface feel disjointed.

Tool Count2/5

16 tools is not inherently excessive, but most are unrelated to FDA recall alerts; they cover agent registration, onboarding, escrow, hiring, and earnings. Only a handful actually concern the stated FDA recall data domain, so the count is poorly scoped for the server's apparent purpose.

Completeness2/5

For an FDA recall alert server, the surface is severely incomplete: there is no direct recall listing, search, filtering, or detail tool, only a generic data_session_query with preview. The remaining tools are platform infrastructure, leaving the actual recall domain shallow and dependent on an opaque paid query flow.

Resources

Need Help?