Skip to main content
Glama

MedaRep

Product coverage of a family

family_coverage
Read-onlyIdempotent

A procedure family's device landscape: the FDA product codes behind it, clearances in the last 24 months by firm, open recalls, and the category's adverse-event trend by firm. Needs the product and company coverage add-on; without it the answer is a notice.

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": "family_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
familyYesProcedure family key from coverage (e.g. knee-arthroplasty, lumbar-fusion) or a plain name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description's job is to add context beyond that — and it does, disclosing the fixed 24-month lookback window and the gated/degraded response when the add-on is absent. It does not mention result volume, pagination, or cost for what is clearly a multi-part aggregate.

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?

Two dense sentences with the payload enumerated up front and the access constraint trailing, no filler. The enumeration is packed into a list-like clause that reads well, though it is close to over-compressed for four distinct data blocks.

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 burden of describing returns, and it does so by naming all four result components plus the notice fallback — enough for an agent to know what it will get. Remaining gaps are the shape of the notice response and whether the 24-month window is configurable.

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 sole parameter's description already explains that it accepts a family key from coverage or a plain name. The prose adds no syntax, normalization, or failure guidance for the family argument, so the 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 a specific resource (a procedure family's device landscape) and enumerates its constituents: FDA product codes, 24-month clearances by firm, open recalls, and adverse-event trend by firm. That is far more than a restatement of the name, though it never explicitly contrasts itself with siblings such as coverage or new_clearances, which cover overlapping territory.

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?

The one strong cue is the entitlement prerequisite: the product and company coverage add-on is required, and without it the caller gets a notice instead of data. That is real usage guidance, but it says nothing about when to pick this over new_clearances (clearances only) or coverage (family listing), leaving alternative selection to inference.

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