Skip to main content
Glama

SolvingHealth federal health data

caregiver_questionnaire

Get the questions for ClinicalSwipe's family caregiver navigator: who is being cared for, their coverage, family doctor, what is going on, military service, money and state. Returns each question with its answer codes, plus the full resource catalog, each resource with its official source URL and the date it was checked. format "fhir" returns the FHIR R4 Questionnaire instead. Call this before caregiver_plan so the answers use the codes it lists.

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_questionnaire"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo"json" (default): plain questions and the catalog. "fhir": the FHIR R4 Questionnaire.

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?

With no annotations, the description carries the burden and does well: it discloses the return payload in detail (questions with answer codes, full resource catalog with official source URL and checked date) and notes the alternate FHIR R4 Questionnaire shape. It does not discuss auth, rate limits, or pagination, but for a read-only getter the behavioral picture is substantially complete.

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?

Front-loads the purpose, then the return contents, then the format switch, then the call-order hint — a sensible priority order. The middle topic list is somewhat run-on, but every element conveys real information about scope.

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 single-parameter, no-output-schema tool, the description covers purpose, return shape, both format values, and inter-tool sequencing. The only real gap is that error or empty-result behavior is unstated, which is minor at this complexity.

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% and the single enum is already documented, so the baseline is 3; the description earns an extra point by restating that 'fhir' returns the FHIR R4 Questionnaire, giving the agent a reason to pick that value rather than just a list of allowed strings.

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?

States a specific verb and resource ('Get the questions for ClinicalSwipe's family caregiver navigator') and enumerates the topic areas covered (care recipient, coverage, family doctor, military service, money, state), which lets an agent distinguish this from siblings like caregiver_plan or find_providers without opening the schema.

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?

Gives explicit sequencing guidance: 'Call this before caregiver_plan so the answers use the codes it lists,' which tells the agent both the ordering and the reason. It lacks any when-not or exclusion guidance, but the positive guidance is clear and actionable.

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.