Skip to main content
Glama

MedaRep

Say what was done about a reason to call

handle_reason

Record what the rep did about a surgeon's reasons from my_day: called (off the list for 90 days), not_now (30 days) or not_relevant (for good). A new kind of reason brings the surgeon back. For a call or visit that happened, also log it with log_visit.

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": {
      "npi": "<npi>",
      "action": "<action>",
      "kinds": "<kinds>"
    },
    "name": "handle_reason"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiYes10-digit NPI; use search to find it.
kindsYesThe reasons' kinds as my_day lists them (reasons[].kind), e.g. ["switch_risk", "expand"].
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive write, and the description goes well beyond them by disclosing the consequence of each action (90-day removal, 30-day deferral, permanent removal) and the recomputation rule that a new reason kind brings the surgeon back. What it does not cover is repeat behavior — whether re-submitting the same action/kind is harmless or re-triggers the timer, which matters given idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core operation and followed by the routing hint to log_visit; each parenthetical (90 days, 30 days, for good) carries distinct information. Nothing is padded or repeated from the schema.

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 small three-parameter write with no output schema, the description covers the operation, per-action effects, and the sibling relationship well. It does not say what the call returns or how partial outcomes are reported when the kinds array holds up to 20 entries, leaving the agent to infer the result shape from the action values.

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 67%, and the description compensates for the least obvious parameter by giving each action value a concrete meaning and time window, which the enum alone does not convey. kinds is tied back to my_day's reasons[].kind (already in the schema) and npi is left to the schema, so the added meaning is real but concentrated in one parameter.

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?

"Record what the rep did about a surgeon's reasons from my_day" names a specific verb (record/handle) and a specific resource (my_day reasons), which separates it from the other write tools in the sibling list. The three action values are spelled out, so an agent knows exactly what state change it is performing. It stops just short of a crisp one-line differentiation from log_visit, which is instead explained in the second sentence.

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?

It states the selection rule explicitly: use this tool to dispose of a surgeon's reasons, and use log_visit when an actual call or visit happened ("also log it"). That is a clear when-to-use plus when-to-use-the-alternative statement with the triggering condition, not just implied context.

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