Skip to main content
Glama

SolvingHealth federal health data

caregiver_plan

Build a family caregiver's plan with ClinicalSwipe's navigator: public programs first, then what to ask the family doctor, then neighbor help, then what is not open yet, labeled as such. Every step names its source page and the date it was checked. A step that needs a clinician says who, what and why, and signs: true marks only the steps a program requires a clinician to sign or certify. General information from official program pages, not medical, legal or financial advice; each program decides its own eligibility. The answers go to clinicalswipe.com, which does not store or log them. Send no names or identifiers.

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

Input Schema

NameRequiredDescriptionDefault
formatNo"json" (default) or "fhir" for a FHIR R4 CarePlan. A QuestionnaireResponse always gets a CarePlan.
answersNoPlain answers keyed by the questionnaire's question ids, using the codes caregiver_questionnaire lists, e.g. {"coverage":"medicare","doctor":"yes","state":"CO","situation":["memory"]}
questionnaire_responseNoA FHIR R4 QuestionnaireResponse to the navigator questionnaire, instead of answers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: answers are sent to clinicalswipe.com, are not stored or logged, steps cite source page and check date, and "signs: true" flags only clinician-certified steps. It also disclaims medical/legal/financial advice and notes each program sets its own eligibility. It stops short of saying what the returned artifact looks like or whether the external submission is irreversible.

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 purpose is front-loaded and the sentences are information-dense with little filler; the disclaimers and privacy note each earn their place. Some phrasing is awkward and run-on ("then what is not open yet, labeled as such"), and the output-format details crowd the purpose statement.

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 tool with no annotations, no output schema and three optional parameters, the description supplies privacy behavior, disclaimers, source-citation convention and the clinician-sign flag. The notable gap is how the plan is returned and how the optional answers vs. questionnaire_response paths relate to the format enum, which only the schema clarifies.

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 description coverage is 100%, so format, answers and questionnaire_response are fully documented in the schema, including the enum values and an example answers payload. The description adds no parameter-level meaning of its own. Baseline 3 applies when the schema does the heavy lifting.

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?

A concrete verb and resource are stated up front: "Build a family caregiver's plan," followed by the ordered structure of the plan (public programs, doctor questions, neighbor help, not-yet-open items). The agent can tell what the tool produces. It does not differentiate itself from the sibling caregiver_questionnaire, which is only referenced inside the answers schema, not the description.

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

Usage Guidelines2/5

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

There is a data-handling rule ("Send no names or identifiers") but no statement of when to call this versus caregiver_questionnaire or find_providers, and no prerequisites or exclusions. The ordering sentences describe the output plan, not the invocation context, so the agent must infer when this tool is the right choice.

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.