Skip to main content
Glama

Meridian Trace — Medical Device Registrations

Licence holders

get_license_holders
Read-onlyIdempotent

The local entities that actually hold a foreign manufacturer's registrations — the importers, distributors and regulatory consultants named on the licence in each market. In Malaysia, Indonesia and Thailand the registry names this local party rather than the OEM, so this is the only way to see who controls market access for a product, who a competitor is partnered with, and whether a manufacturer uses one partner or many.

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

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.
manufacturer_idYes

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"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "manufacturer_id"
      -]New value: +[
      +  "manufacturer_id",
      +  "reason",
      +  "user_intent"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is domain framing — that results come from local registry naming rather than OEM records. Beyond that it says nothing about coverage gaps, result size, or what happens when a market is unsupported, which matters given the market-dependent nature it describes.

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?

A single dense sentence that front-loads the definition and then justifies it with concrete use cases. A few emphatic phrases ('actually hold', 'the only way') add emphasis without adding information, but there is no filler paragraph.

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 does the work of naming what comes back (importer/distributor/consultant entities on a licence) and where the data originates. Lacking is any sense of result shape per market or limits on coverage, though for a simple three-parameter lookup this is close to sufficient.

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 67% and manufacturer_id carries no schema description; the description implies the ID refers to the foreign manufacturer/OEM (not the local holder), which is a useful disambiguation. It adds nothing about expected ID format or how reason/user_intent are used, so the gain over the schema is marginal.

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?

Specific noun+resource: 'the local entities that actually hold a foreign manufacturer's registrations — the importers, distributors and regulatory consultants named on the licence in each market.' It defines the entity class and how it differs from the OEM, so an agent knows exactly what is returned. It does not explicitly differentiate from the sibling find_distributors, which is a plausible point of confusion.

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?

Gives a real usage condition: 'In Malaysia, Indonesia and Thailand the registry names this local party rather than the OEM', which tells the agent when this tool is the right lens. It also states the analytical questions it answers (who controls market access, who a competitor partners with, one partner vs many). No alternative sibling is named as an explicit fallback.

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