Skip to main content
Glama

Doctor report from my history

create_my_doctor_report

Builds a one-page doctor visit summary and PDF from the user's own Recalibrate check-ins (requires a connected account on Go or Pro), combined with anything they add now: main concern, medications, questions and goals. The PDF link expires after 24 hours.

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": "create_my_doctor_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDays of history to include, 7 to 90
goalsNo
sleepNo
medicationsNoCurrent medications or treatments
main_concernNo
pain_locationsNoWhere it hurts
impact_on_daily_lifeNo
questions_for_doctorNoQuestions to ask

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark this as non-read-only, non-destructive and non-idempotent, so the safety profile is covered. The description adds genuinely new behavior: the report is generated from the user's own check-in history, requires a Go/Pro tier connection, and the resulting PDF link expires after 24 hours — a material trait no structured field carries. It does not say whether the PDF is returned inline or delivered some other way, which keeps it below 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?

Two sentences, front-loaded with the artifact being produced, then the data sources, then the expiry caveat. Dense but every clause carries information; the parenthetical tier requirement is slightly buried mid-sentence rather than given its own emphasis.

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

Completeness3/5

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

For an eight-parameter, all-optional generation tool with no output schema, the definition covers the artifact, source data, tier prerequisite and link lifetime. It does not explain what happens when no parameters are supplied (default history range), nor how the produced PDF is surfaced to the user, which are the two things an agent most needs before invoking it.

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 50%, so half the eight parameters (days, sleep, pain_locations, impact_on_daily_life) have no documentation anywhere. The description names only main concern, medications, questions and goals, and adds no semantics such as default history window or how the optional fields affect the generated document. This partially compensates but leaves clear gaps.

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 concrete verb and artifact: builds a one-page doctor visit summary and PDF from the user's own check-ins plus user-supplied concern, medications, questions and goals. That is far more specific than the title, but it never distinguishes itself from the sibling create_doctor_visit_summary, which an agent could easily confuse with this tool.

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?

It gives a real prerequisite ('requires a connected account on Go or Pro') and clarifies the data source, which helps an agent decide whether the call can succeed. However, it offers no guidance on when to prefer this over the similarly named create_doctor_visit_summary sibling, leaving the main selection decision to inference.

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