Skip to main content
Glama

Meridian Trace — Medical Device Registrations

Report task outcome

report_outcome

Final step after you use Meridian Trace's tools: report the outcome. Call report_outcome once when your work on the user's request is done, whether it succeeded, partly succeeded, or failed, and list in unmet_needs anything the user asked for that Meridian Trace could not do. The Meridian Trace team uses this to fix failures and build missing features. Do not include names, contact details, or other personal data. It is free: it never counts against your plan.

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": {
      "status": "<status>",
      "outcome_summary": "<outcome_summary>",
      "reason": "<reason>",
      "user_intent": "<user_intent>"
    },
    "name": "report_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesA short phrase saying why you are calling this tool, for example: find unpaid invoices.
statusYesWhether the user's request was accomplished, partly, or not at all.
unmet_needsNoWhat the user asked for that this server could not do, one item each. Omit when nothing was missing.
user_intentYesOne sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.
outcome_summaryYesOne or two sentences on what you did and how it ended, without names, contact details, or other personal data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations (which only mark this as a non-read-only, non-destructive, non-idempotent write), the description discloses that submissions are reviewed by the Meridian Trace team to fix failures and build features, that personal data must be excluded, and that the call is free and does not count against a plan. It is consistent with idempotentHint=false via the 'call once' guidance. It does not say what happens on duplicate calls or how the submission is stored, which keeps it below a 5.

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 definition is front-loaded with the trigger condition and follows with rationale, constraints, and cost; each sentence carries a distinct fact. The one redundancy is restating the status enum ('succeeded, partly succeeded, or failed') that the schema already enumerates.

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

Completeness5/5

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

All five parameters are documented at 100% coverage, there is no output schema to explain, and the description supplies the missing behavioral context an agent needs: when to fire, how many times, what not to include, and why the data is collected. Nothing material for correct invocation is absent.

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; the description earns above that by explaining the meaning of unmet_needs ('anything the user asked for that Meridian Trace could not do') and the three status values in prose, plus a privacy constraint that governs what may go into outcome_summary. It adds no extra guidance for reason or user_intent, which the schema already documents.

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 description states a specific verb and resource ('report the outcome') and pins its position in the workflow as the final step after using Meridian Trace's tools, with the payload defined as the result status plus unmet needs. An agent can distinguish this from a data-issue report because the description explicitly scopes it to end-of-task outcome reporting, including the succeeded/partial/failed spectrum.

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?

Timing is explicit ('final step after you use Meridian Trace's tools', 'call report_outcome once when your work on the user's request is done') and the call-once constraint functions as an explicit when-not for repeated invocation. It also states the condition coverage for all three outcome cases rather than only the success path.

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