Skip to main content
Glama

Meridian Trace — Medical Device Registrations

Market coverage and gaps

get_market_coverage
Read-onlyIdempotent

THE cross-market question, answered in one call: every market where this manufacturer IS registered and every market where they are NOT. Returns per-market registration and active-registration counts and the source registries, plus the markets absent from their footprint — which is the gap a market-access team is usually looking for ("registered in Indonesia and Thailand, missing in the Philippines"). Prefer this over get_registrations when the question is about market presence rather than individual products. A marketAccess block may also appear. It is NOT a registration and is excluded from marketCount and every count in this response: it reports market access held on another basis — currently PMDA foreign manufacturer accreditation, which licenses a manufacturing SITE to make devices for Japan, precedes product approval and outlives individual products. When it is present alongside Japan in absent, both are true and the distinction matters: the company can supply the market but has no Japanese product approval visible to us. Do not describe that as being registered in Japan, and do not add it to a market count. A singaporeClassAListings block may also appear: self-declared Class A listings in Singapore, not registrations; HSA does not verify them (Class A is exempt from registration). Its count is of LISTED MODELS; it is never in marketCount or registered, carries no dates (nothing in it is new), and its attribution must be quoted with any figure from it. A notJudged block lists markets that register only decree-listed categories (Chile): a company with no rows there is NOT missing there — most devices need no registration — so never report it as a gap.

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_market_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCompany name, as an alternative to manufacturer_id. Resolves the same way search_manufacturer does and uses the best match.
reasonYesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
tickerNoListed ticker (e.g. "MDT"), as an alternative to manufacturer_id or name. Covers US-listed registrants; many large device makers are private or listed only outside the US and cannot be reached this way.
user_intentYesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.
manufacturer_idNoThe Meridian Trace manufacturer _id, from search_manufacturer

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description goes well beyond that by explaining the three auxiliary blocks (marketAccess, singaporeClassAListings, notJudged), their exclusion from marketCount, and the quoting requirement on attribution — but since this overlaps output-shape disclosure rather than behavior beyond annotations, it sits at solid-but-not-exceptional rather than top marks.

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?

Front-loaded with a punchy lead sentence and then organized by output block, with the sibling routing instruction placed early. It is long, but most sentences carry real disambiguation value; the marketAccess explanation in particular is stretched across several clauses that could be tightened.

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 carries the full burden of explaining return values — and it does, covering counts, source registries, the absent-markets gap, and three special-cased blocks with their counting rules. Nothing an agent needs in order to call or interpret this tool is missing.

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 all five parameters carry their own descriptions, including the manufacturer_id provenance and ticker coverage limits. The description adds no parameter-level meaning at all, so the baseline 3 applies.

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 — returns every market where a manufacturer is registered and every market where it is not, with per-market registration counts and source registries. It explicitly contrasts itself with get_registrations for the market-presence vs. individual-product question, so an agent can route without opening another 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 an explicit alternative and the condition that selects it ("Prefer this over get_registrations when the question is about market presence rather than individual products"). It also supplies when-not guidance for output interpretation — do not treat marketAccess as a registration, do not report notJudged markets as gaps — which is usage guidance for the result set.

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