Skip to main content
Glama

FDA MQSA certified mammography facilities in one US state

health_mammography_facility_fda
Read-only

FDA MQSA certified mammography facilities in one US state (FDA public search): facility name, phone, city, ZIP and FDA facility ID. Parsed from the FDA results page, which shows the facilities on the first results page only. Radiation safety data is not included. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "state": "<state>"
    },
    "name": "health_mammography_facility_fda"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many facilities, 1 to 50 (default 10)
stateYesTwo-letter US state code, e.g. VT

Output Schema

NameRequiredDescriptionDefault
stateNo
sourceNo
checkedAtNo
facilitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description still adds real behavioral context: results come from the FDA results page and cover 'the first results page only', radiation safety data is absent, and pricing/billing behavior (per successful call, x402 payment, failed calls free) is disclosed. The main uncovered trait is error or empty-result behavior, plus the interaction between the first-page cap and the max parameter.

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 core capability is front-loaded in the first clause, followed by returned fields, then limitations, then billing. It is a dense but readable block; the pricing sentence is long but relevant to callers since it affects invocation decisions.

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 two-parameter read-only lookup with an output schema, the description covers what data is returned, the coverage limitation (first page only), explicit exclusions, and cost model. Nothing essential to correct invocation 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?

Schema description coverage is 100%, so both parameters (state, max) are already documented in the schema. The description reinforces state scoping but adds nothing about the max parameter; the first-results-page note is about result coverage rather than parameter meaning.

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 names a precise resource and scope: 'FDA MQSA certified mammography facilities in one US state', and enumerates the returned fields (facility name, phone, city, ZIP, FDA facility ID). No sibling tool overlaps this resource, so an agent can identify the right tool immediately.

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

Usage Guidelines3/5

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

Usage is only implied by the scope statements ('in one US state', 'Radiation safety data is not included'). There is no explicit when-to-use or when-not-to-use guidance and no named alternative, though the exclusions implicitly tell the agent not to come here for radiation safety data.

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