Skip to main content
Glama

Meridian Trace — Medical Device Registrations

Check a reported problem

check_issue
Read-onlyIdempotent

Where a report you filed with report_data_issue stands — Received, Looking into it, Fixed, Not changing or Already reported (with the reference it repeats) — and Meridian's reply, if any. Only the API key that filed a report (or another key on the same account) can read it. Needs an API key.

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

Input Schema

NameRequiredDescriptionDefault
refYesThe reference report_data_issue returned, e.g. MT-1042
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"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "ref"
      -]New value: +[
      +  "ref",
      +  "reason",
      +  "user_intent"
      +]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, closed-world profile, and the description adds genuinely new context: the access-control rule that only the filing API key or another key on the same account may read the report, and that a reply from Meridian may be attached. It omits error behavior for an unknown or foreign ref, which is the main remaining gap.

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 status enumeration is front-loaded and the access caveat is compact, with no filler. The single em-dash-chained sentence is slightly harder to parse than split sentences would be, but nothing is wasted.

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 describing return values and does so by enumerating possible statuses and the optional Meridian reply, plus the auth constraint. It stops short of saying what happens on an invalid or unauthorized ref, which an agent would want to know before calling.

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%, so the baseline is 3. The description adds a little meaning to ref by noting that an 'Already reported' status returns the reference it duplicates, but it says nothing about the required reason and user_intent parameters beyond what their schema descriptions already provide.

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+resource ('Where a report you filed... stands') and enumerates the exact status values returned (Received, Looking into it, Fixed, Not changing, Already reported). It also links itself to the sibling tool that creates the resource (report_data_issue) and names the identifier it consumes, so an agent can tell it apart from report_data_issue without opening either schema.

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?

The reference to report_data_issue plus 'with the reference it repeats' makes the use case — checking on a report you previously filed — unambiguous. There is no explicit when-not guidance or polling/evaluation advice, so it falls short of a 5.

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