Skip to main content
Glama

Meridian Trace — Medical Device Registrations

Recent registrations

get_recent_registrations
Read-onlyIdempotent

Registrations newly added to Meridian in the last N days, optionally filtered by market, risk class or device type — the competitor-monitoring feed. Ordered by when we first saw the record, so it surfaces market entries as they appear rather than by approval date. US PMA supplements are excluded: they are labeling and site changes against an existing approval, not new registrations. Records that arrived in a bulk load (a registry's history or a first load) are excluded too and named in meta.basis.bulkLoadsExcluded; meta.basis.note says what was left out — repeat it rather than calling the list complete. Filtering by market is much faster — unfiltered across all markets can take up to 15 seconds, a market or two returns in about a second.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window, 1-180 (default 30)
limitNoMax results (default 50, max 100)
reasonYesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
marketsNoISO2 codes, e.g. ["TH","ID"]
risk_levelNoLow | Medium | High
device_typeNoResolved GMDN device type
user_intentYesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.

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.6/5.0
Behavior5/5

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

The annotations already declare this to be a safe, idempotent read, so the description adds genuinely new context. It states the ordering rule, two concrete exclusion classes (US PMA supplements, bulk-load arrivals), the meta.basis fields that name what was left out, and the instruction to repeat that caveat rather than claim completeness, plus latency differences (about 15 seconds unfiltered versus about 1 second with a market filter).

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 definition is front-loaded with the core purpose, then the ordering, exclusions, and performance caveat follow in a logical sequence. It is dense and each sentence earns its place, though the meta.basis caveat is repeated in slightly redundant wording.

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 are seven parameters at full schema coverage, this is a read-only tool with annotations, and there is no output schema. The description still discloses the shape of the return caveat (meta.basis.bulkLoadsExcluded, meta.basis.note), so an agent knows how to interpret and report results.

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, but the description adds meaning by explaining that the days window is measured from when records were first seen and by tying markets filtering to a large latency difference. It adds no further detail for risk_level or device_type beyond the schema, which keeps this at 4.

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 uses a specific verb and resource: registrations newly added in the last N days. It also scopes that resource explicitly, saying the feed is ordered by first-seen rather than approval date and is the competitor-monitoring feed, so it clearly differs from a general registration lookup even though no sibling is named.

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

Usage Guidelines4/5

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

It gives clear context for when to use the tool: competitive monitoring of market entry and newly added records. It adds a performance rule, telling the agent to filter by market and avoid unfiltered cross-market calls. It does not name an explicit alternative for historical or approval-date queries, so it falls just short of a full 5.

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