Skip to main content
Glama

MedaRep

New FDA clearances, read for a rep

new_clearances
Read-onlyIdempotent

A procedure family's new FDA 510(k), De Novo and PMA decisions from the last days (default 90), read weekly from FDA: each as a new entrant (the company's first here), a new system (a name it has not cleared before) or a line extension (more of a line it already sells), with the basis, what it means for the rep (soWhat, from their side when the company is one of their lines) and FDA's page. Optionally one company. Needs the product and company coverage add-on.

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": {
      "family": "<family>"
    },
    "name": "new_clearances"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow far back, in days (default 90).
familyYesProcedure family key from coverage (e.g. knee-arthroplasty, lumbar-fusion) or a plain name.
companyNoOnly this company (part of its name, e.g. Stryker).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningfully on top: the data origin (FDA, refreshed weekly), the default 90-day window, how results are classified (first entrant / new system / line extension), and the extra soWhat field framed from the rep's perspective. It does not discuss result volume, pagination, or what an empty family returns, which keeps it off 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.

Conciseness3/5

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

It is front-loaded correctly, leading with what the resource is before the classification detail. But the whole definition is one sprawling sentence studded with parentheticals, which makes the agent parse nested asides to reach the entitlement note at the end. The content mostly earns its place; the packaging does not.

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?

With no output schema, the description carries the return-value burden and does so: each result is a decision with a basis, a rep-facing soWhat, and an FDA page link. Freshness, default window, and the coverage add-on prerequisite round out what an agent needs. Missing only volume or truncation behavior for a potentially long weekly feed.

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%, so all three parameters are already documented, including the default 90 days and the company substring filter. The description reinforces that the family is a procedure-family key sourced from coverage and that company is optional, but adds no syntax, format, or edge-case detail beyond the schema. Baseline 3 is the right landing point when the schema does the heavy lifting.

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 a specific verb and resource: new FDA 510(k), De Novo and PMA decisions for a given procedure family, and even enumerates the three classification buckets each result falls into. That is far beyond a restatement of the name. It stops short of a 5 because it never explicitly contrasts itself with likely-adjacent siblings such as changes_since or new_surgeons, leaving disambiguation to inference.

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 prescribed: you supply a procedure family, optionally narrow to one company, and results cover a trailing window defaulting to 90 days. The prerequisite 'Needs the product and company coverage add-on' is a genuinely useful gate an agent should know before calling. However, there is no explicit when-to-use versus another tool, nor any statement about when this tool is the wrong pick.

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