Skip to main content
Glama

Meridian Trace — Medical Device Registrations

Find 510(k) predicates

find_predicates
Read-onlyIdempotent

US 510(k) predicate lineage, from the predicates actually cited in each clearance's own summary document — not a similarity guess. 64,567 clearances, 1992-2026. By k_number: what that device cited, AND which later devices cited IT as a predicate — the reverse direction shows whose clearances rest on your device and how contested a space is. By product_code: the predicates that code leans on most, ranked by how often they are cited, plus recent clearances. Use when choosing a predicate, assessing substantial equivalence, or mapping who is clearing devices in a classification.

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": {
      "reason": "<reason>",
      "user_intent": "<user_intent>"
    },
    "name": "find_predicates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows per list (default 20, max 50)
reasonYesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
k_numberNoA 510(k) number, e.g. "K191275"
user_intentYesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.
product_codeNoAn FDA product code, e.g. "LIT"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / reason
      Added value: +{
      +  "description": "A short phrase saying why you are calling this tool, for example: find unpaid invoices.",
      +  "maxLength": 128,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / user_intent
      Added value: +{
      +  "description": "One sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.",
      +  "maxLength": 256,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "reason",
      +  "user_intent"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that: data provenance (citations from each clearance's own summary), corpus size and date span, and the reverse-citation direction that shows downstream devices. It does not mention rate limits, latency, or what happens when a query returns nothing, so it does not reach the top of the scale.

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?

Reasonably front-loaded: the provenance claim and the sibling distinction land in the first sentence, and the two query modes are explained in order. The '64,567 clearances, 1992-2026' figure is useful scope information but the sentences are long and carry multiple clauses each, costing some efficiency.

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?

There is no output schema, so the description must convey the return shape, and it does: forward citations, reverse citations, ranked predicate lists, and recent clearances. For a two-mode lookup with a fully documented schema and complete annotations, it covers what an agent needs to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description earns above baseline by explaining what each selector actually returns: k_number yields both what the device cited and which later devices cited it (the reverse direction), while product_code yields the most-cited predicates for that code ranked by citation frequency plus recent clearances. It says nothing about limit or the boilerplate reason/user_intent parameters, which the schema already covers.

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?

States a specific verb and resource ('US 510(k) predicate lineage, from the predicates actually cited in each clearance's own summary document') and explicitly distinguishes itself from similarity-based siblings with 'not a similarity guess', which separates it from find_similar_devices without needing the schema.

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

Usage Guidelines5/5

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

Gives explicit use cases ('choosing a predicate, assessing substantial equivalence, or mapping who is clearing devices in a classification') and implicitly routes away from find_similar_devices by framing the data as citation-derived rather than guessed. It also tells the agent which of the two query modes (

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