Skip to main content
Glama

Meridian Trace — Medical Device Registrations

Report a data problem

report_data_issue

Tell Meridian that a record you got from this server looks WRONG — a registration, a manufacturer or a licence holder whose field disagrees with the official registry or the company's own documents. Name the record (registration_id from get_registration / get_registrations, or manufacturer_id, or registry_key such as "TH_FDA:64-2-1-2-0001234"), the field, what we show, what it should be, and where the right value is (source_url, and source_quote copied word for word). Meridian checks every report by hand; nothing changes until we have. Returns a reference like MT-1042 — pass it to check_issue later. Needs an API key. At most 50 reports per key per day. Use it for wrong data, not for questions about what a field means.

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

Input Schema

NameRequiredDescriptionDefault
noteNoAnything else that helps — one or two sentences
fieldYesWhich field is wrong, as this server named it (e.g. expiryDate, manufacturerName, deviceClass)
shownNoWhat this server returned for that field
reasonYesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
expectedNoWhat it should be
source_urlNoWhere the right value is published (http/https)
user_intentYesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.
registry_keyNoWhen you have no id: the source registry and its own number
source_quoteNoThe words on that page that show it, verbatim
manufacturer_idNoThe manufacturer's id as this server returned it
registration_idNoThe registration's id as this server returned it
license_holder_idNoThe licence holder's id as this server returned it

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: -[
      -  "field"
      -]New value: +[
      +  "field",
      +  "reason",
      +  "user_intent"
      +]
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the mutation/safety profile; the description adds the operational context that matters: every report is human-reviewed, no data changes as a result, the return value is a reference like MT-1042, an API key is required, and the cap is 50 reports per key per day.

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 the action and the evidence requirement, and the rate limit and return value come in a logical order at the end. It is a dense run-on paragraph that could be broken into lines, but nearly every clause carries operational information.

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?

For a 12-parameter mutation tool with no output schema, the description covers the review workflow, the return reference, auth, and rate limit. Remaining gaps are minor: it does not say which identity parameters are strictly needed (license_holder_id is unmentioned) or what happens to a rejected or duplicate report.

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 real meaning by tying identifiers together (registration_id fetched from get_registration / get_registrations, registry_key with a worked example 'TH_FDA:64-2-1-2-0001234') and by requiring source_quote be copied verbatim. It omits license_holder_id, which the schema does expose.

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 (report a wrong record to Meridian) and enumerates concrete field-level examples (registration, manufacturer, licence holder disagreeing with the official registry). It also distinguishes itself from read siblings by naming get_registration / get_registrations as the source of the id, so an agent can place it immediately.

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 when-not: 'Use it for wrong data, not for questions about what a field means.' It also prescribes the inputs to gather and routes the follow-up to check_issue with the returned reference, leaving nothing to inference about sequencing.

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