Skip to main content
Glama

review_time

Read-onlyIdempotent

FDA 510(k) review time for a product code since 2021 (latest 1,000 decisions): median days, middle half, and China applicants vs others. Review time = decision date minus date received.

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": {
      "product_code": "<product_code>"
    },
    "name": "review_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_codeYesThree-letter FDA product code, for example "LLZ"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the results are a sample capped at the latest 1,000 decisions and only since 2021, which warns the agent about coverage limits, and the metric formula makes the unit (days) unambiguous.

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?

Two tightly-packed sentences: the first front-loads scope and the returned statistics, the second defines the metric. No filler, and every clause carries information an agent needs.

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 one-parameter aggregate read with no output schema, the description does the work of explaining what comes back (median, middle half, China vs others) and the sample window. The only soft spot is the phrase "middle half," which is not plainly identified as an interquartile range, leaving a small ambiguity about the second statistic.

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% and the single parameter already documents the three-letter format with an example ("LLZ"), so the schema carries the load. The description adds only that the code defines the cohort being measured, which is marginal beyond the schema; baseline 3 applies.

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?

The description names the concrete resource and measurement: FDA 510(k) review time per product code, returning median days, a middle-half spread, and a China-vs-others breakdown. It even defines the metric (decision date minus date received), so an agent knows exactly what number it gets. It does not explicitly contrast itself with siblings like latest_clearances, but the aggregate-metric framing is distinct enough to separate them.

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 implied rather than stated: the reader infers this is for benchmarking review durations for a given product code, and the embedded scope constraints (since 2021, latest 1,000 decisions, 510(k) only) implicitly bound when the answer applies. There is no explicit when-to-use/when-not guidance and no alternative tool is named for related questions.

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