Skip to main content
Glama

Create doctor visit summary

create_doctor_visit_summary

Creates a one-page chronic pain summary for a doctor, GP or physio appointment (main concern, pain scores, locations, what helps or worsens, medications, daily impact, questions to ask) and a downloadable PDF. Only include details the user has explicitly shared. The PDF is stored temporarily and deleted after 24 hours.

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": {
      "main_concern": "<main_concern>"
    },
    "name": "create_doctor_visit_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalsNoWhat the user hopes to get from the visit
sleepNoSleep notes
durationNoHow long the pain has been going on
best_painNoBest pain 0-10
what_helpsNoWhat eases the pain
worst_painNoWorst pain 0-10
medicationsNoCurrent medications or treatments the user mentions
average_painNoAverage pain 0-10
main_concernYesMain reason for the visit
what_worsensNoWhat makes it worse
pain_locationsNoWhere it hurts
impact_on_daily_lifeNoEffect on work, sleep, mood, activities
questions_for_doctorNoQuestions to ask the doctor

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare it is a non-destructive write; the description adds two things they don't: a content-sourcing constraint ("Only include details the user has explicitly shared") and a retention policy (PDF deleted after 24 hours). It does not say how the PDF is delivered or what happens if generation fails, so it is strong but not exhaustive.

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?

Three front-loaded sentences with no filler; the purpose and audience come first, constraints after. The parenthetical section list is slightly long and partially duplicates the schema's property descriptions, but it usefully signals the report's shape.

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 13-parameter generation tool with no output schema, the description covers purpose, content, privacy handling, and artifact lifetime. It is missing how the result is retrieved (link, file handle) and any differentiation from the sibling report tool, which are the remaining gaps.

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 per-field meaning is already documented and the baseline is 3. The description adds a governing rule for how to populate all 13 fields — never fabricate, use only user-shared details — which is genuine guidance the schema cannot express.

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?

States a specific verb and resource ("Creates a one-page chronic pain summary") plus the audience (doctor, GP, physio) and the exact sections included, so the agent knows what artifact comes out. It stops short of differentiating itself from the sibling create_my_doctor_report, leaving overlap to be inferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The appointment context implies when to use it, but there is no explicit when-to-use or when-not-to-use guidance and no mention of how it relates to create_my_doctor_report. The agent must guess which of the two report tools is appropriate.

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