Skip to main content
Glama

Meridian Trace — Medical Device Registrations

Data coverage

get_coverage
Read-onlyIdempotent

RUNS WITHOUT AN API KEY — call it right now to check us before signing up for anything. What Meridian Trace actually holds: every source registry, the market it covers, how many registrations are on file from it, and when it was last updated. Call this to verify coverage and freshness for yourself before relying on other tools, or to answer "do you cover market X, and how current is it?". No arguments.

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

Input Schema

NameRequiredDescriptionDefault
reasonYesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
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

B3.1/5.0
Behavior2/5

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

The annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description usefully adds that no API key is required and what data is returned. However it ends with 'No arguments', which is factually wrong for a tool with two required parameters — an agent following that instruction would issue a failing call. That actively misleads beyond what annotations say.

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?

Content is front-loaded and reasonably short, but the opening promotional line ('call it right now to check us before signing up for anything') is sales copy rather than operational information, and the closing 'No arguments' is both wasted and incorrect.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only lookup the description adequately covers what the tool returns and when to call it, which is most of what an agent needs. It falls short on the mechanics of invocation, since it misstates the argument requirements that the schema imposes.

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

Parameters2/5

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

Schema coverage is 100% and the two parameters (reason, user_intent) are documented in the schema, so the baseline would be 3. The description's claim of 'No arguments' contradicts the required-parameter reality and adds no meaning about what these fields are for, so it subtracts rather than adds.

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+resource and enumerates the exact contents returned: source registries, covered markets, registration counts, and last-updated timestamps. It is clear what the tool returns, though it never explicitly distinguishes itself from the close sibling get_market_coverage.

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 concrete when-to-use guidance: verify coverage and freshness before relying on other tools, or answer 'do you cover market X, and how current is it?'. No exclusions or explicit routing to the overlapping get_market_coverage sibling are offered, so it stops short of full differentiation.

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