Skip to main content
Glama

Pain flare check-in

check_pain_flare
Read-only

Runs a quick chronic pain flare check-in: rates flare severity against usual pain, screens symptoms for warning signs that need urgent medical care, and returns a step-by-step flare plan plus trigger insights. Use when the user is having a flare-up or their pain is worse than usual. Does not store data.

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": {
      "pain_level": "<pain_level>"
    },
    "name": "check_pain_flare"
  }
}

Input Schema

NameRequiredDescriptionDefault
symptomsNoSymptoms the user describes
pain_levelYesPain right now, 0-10
hours_sleptNoHours slept last night
usual_pain_levelNoUsual everyday pain, 0-10
possible_triggersNoThings that may have triggered it (sleep, stress, weather, overdoing it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds meaningful behavior beyond them: it screens symptoms for warning signs requiring urgent medical care, returns a step-by-step flare plan and trigger insights, and explicitly does not store data. It is slightly thin on what the output looks like when warning signs are detected, but overall adds substantial behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with zero waste: purpose first, then usage condition, then a key data-handling note. Everything is front-loaded and easy to scan.

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 health-screening tool with no output schema but complete parameter documentation and clear read-only annotations, the description is nearly complete: it explains the screen, the returned plan, and the no-storage behavior. A little more detail on what happens when urgent warning signs are found would make it fully complete.

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 the input schema already documents each parameter's meaning and bounds. The description links parameters to outputs ('rates flare severity against usual pain', 'screens symptoms', 'trigger insights'), but does not add syntax or format details beyond the schema—the expected baseline 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Runs a quick chronic pain flare check-in') and spells out the three core actions: rating severity against usual pain, screening symptoms for urgent-care warning signs, and returning a flare plan plus trigger insights. It distinguishes itself from routine tools like log_daily_check_in by scoping to flare-ups or pain worse than usual.

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?

It gives a clear triggering condition: 'Use when the user is having a flare-up or their pain is worse than usual.' That implicitly separates it from routine daily check-ins, but it does not explicitly name alternatives or state when not to use it.

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