Skip to main content
Glama

MedaRep

Add, move or close a follow-up

set_follow_up

Add a follow-up for a surgeon, due by a day (what to do, without patient information); close one with done and its id from my_follow_ups; or move one to another day or reword it with move, its id, and the new due or what.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_follow_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNoYYYY-MM-DD, today or later.
npiNo10-digit NPI; use search to find it.
doneNoA follow-up's id to mark done, instead of adding one.
moveNoA follow-up's id to move to the new due day or reword with what, instead of adding one.
whatNoWhat to do, e.g. "bring the cementless knee sizing guide".

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?

The annotations declare this is a non-read-only, non-destructive, non-idempotent mutation, and the description adds genuinely non-obvious behavior: mode switching is driven by the presence of done/move (replacing an add), and 'what' must exclude patient information. What's missing is failure behavior and whether a move/reword overwrites prior text.

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, front-loaded with the default action (add) and then the two alternative modes signaled by semicolons. It earns nearly every clause, though the semicolon-chained packing of three modes makes it slightly harder to parse at a glance.

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 5-parameter, all-optional mutation tool with full schema coverage and no output schema, the description supplies the mode logic and the privacy constraint that the structured data lacks. The only shortfall is silence on what a successful call returns or confirms, which matters slightly more given there is no output schema.

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 goes further by explaining the cross-parameter relationship between modes that no single property description conveys ('done ... instead of adding one', 'move ... instead of adding one'). It doesn't restate types or formats, which is correct since the schema already does.

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 names a specific resource (a follow-up) and three concrete operations (add, close, move), so the agent knows exactly what the tool does. It also implicitly separates itself from my_follow_ups by citing it as the source of ids for closing, which makes the read-vs-write boundary clear.

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?

Each mode is tied to the parameters that select it: 'done and its id' for closing, 'move, its id, and the new due or what' for moving, otherwise adding. That is explicit conditional guidance for a multi-mode tool. It doesn't cover error or exclusion cases (e.g., what to do if the id is wrong), which keeps it 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