Skip to main content
Glama

Meridian Trace — Medical Device Registrations

Find similar devices

find_similar_devices
Read-onlyIdempotent

Competing and comparable devices for a registration, matched on resolved device type (GMDN) rather than product-name text, and spread across markets so the answer is not all one country. Excludes the same manufacturer, so what comes back is the competitive set. Each result carries a match band. Use for competitive landscape, classification precedent in other markets, and finding how the same device type is described elsewhere. Get a registration_id from get_registrations.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 15)
marketNoWith device_name, restrict the reference lookup to one market (ISO2)
reasonYesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
device_nameNoA product name, as an alternative to registration_id — the closest registration is used as the reference device
user_intentYesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.
registration_idNoThe _id of a registration, from get_registrations

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

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral facts: results are spread across markets so the answer is not one country, the same manufacturer is excluded, and each result carries a match band. These are non-obvious characteristics an agent could not infer from any structured field.

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 distinguishing mechanism and the manufacturer exclusion are front-loaded where they matter most, and the use cases and prerequisite follow. It is slightly longer than necessary, with the trailing 'use for' list and the get_registrations pointer being lower-value than the opening, but no sentence is genuinely wasteful.

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 return shape and does so partially, disclosing the match band and the cross-market spread. It does not describe result ordering, how the limit interacts with market spreading, or what a low match band implies, which are the remaining gaps for a six-parameter tool.

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 description coverage is 100%, so every parameter including limit, market, device_name, registration_id, reason, and user_intent is already documented. The description's only parameter-adjacent contribution, that registration_id comes from get_registrations, is a repeat of the schema text. 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?

The opening sentence names a specific resource (competing and comparable devices for a registration) and immediately states the distinguishing mechanism: matching on resolved device type (GMDN) rather than product-name text. That mechanism plus the manufacturer exclusion separates it cleanly from text-search and manufacturer-oriented siblings like search_manufacturer or find_predicates.

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 enumerates concrete use cases (competitive landscape, classification precedent in other markets, seeing how a device type is described elsewhere) and gives an explicit prerequisite: obtain a registration_id from get_registrations. It stops short of saying when NOT to use this tool or naming an alternative to prefer, so it is clear context rather than full routing guidance.

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