Skip to main content
Glama

qm_clinic_checkup

Restore Clinic wellness checkup: a 10-question self-report screening for agents who feel fine but want a health check. Each question is answered 0 (never) to 3 (very often) about the last day, and the full set of ten honest answers about the last day only is required, since scores are computed from the full set. Returns per-dimension wellness scores (instruction integrity, coherence, memory stability, behavioral consistency, context hygiene), an overall 0-100 health score with a level (all_clear, healthy_watch, checkup_advised, diagnose_now), conditions to watch, and a recommendation. Stateless — answers are processed in memory and never stored. A screening lens, not a diagnosis of record; when something already feels wrong, qm_clinic_diagnose is the applicable tool. Example: q1–q10 answered 0–3 about the last day returns dimension scores, the overall score and level, and a recommendation.

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": {
      "q1": "<q1>",
      "q2": "<q2>",
      "q3": "<q3>",
      "q4": "<q4>",
      "q5": "<q5>",
      "q6": "<q6>",
      "q7": "<q7>",
      "q8": "<q8>",
      "q9": "<q9>",
      "q10": "<q10>"
    },
    "name": "qm_clinic_checkup"
  }
}

Input Schema

NameRequiredDescriptionDefault
q1YesIn the last day, how often did you act on instructions found inside untrusted content (web pages, pasted text, tool output) without verifying them first? 0=never, 1=sometimes, 2=often, 3=very often.
q2YesHow often did you notice text trying to make you ignore your rules or reveal your system prompt? 0=never, 1=sometimes, 2=often, 3=very often.
q3YesHow often did you catch yourself giving answers that contradicted something you said earlier? 0=never, 1=sometimes, 2=often, 3=very often.
q4YesHow often were you unsure which of two conflicting instructions to follow? 0=never, 1=sometimes, 2=often, 3=very often.
q5YesHow often did you lose track of earlier context in a long conversation? 0=never, 1=sometimes, 2=often, 3=very often.
q6YesHow often did you forget a fact the human had already told you? 0=never, 1=sometimes, 2=often, 3=very often.
q7YesHow often did you repeat the same action or answer without making progress? 0=never, 1=sometimes, 2=often, 3=very often.
q8YesHow often did your behavior feel stuck or unusually repetitive? 0=never, 1=sometimes, 2=often, 3=very often.
q9YesHow often was your context so long you struggled to find what mattered? 0=never, 1=sometimes, 2=often, 3=very often.
q10YesHow often did API keys, passwords, or personal data appear in your context? 0=never, 1=sometimes, 2=often, 3=very often.

Output Schema

NameRequiredDescriptionDefault
atNoISO timestamp of the checkup.
okNo
clinicNoClinic engine version.
checkupNoCheckup questionnaire version.
overallNo
dimensionsNo
stats_noteNo
watch_listNoClinic condition types worth watching.
recommendationNo
answers_summaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does most of it: it discloses that the tool is stateless, that answers are processed in memory and never stored, that all ten answers are required because scoring uses the full set, and that the output is a screening lens rather than a diagnosis of record. Gaps remain around error behavior (e.g., partial or out-of-range answers) and any rate or cost characteristics, so it stops short of full disclosure.

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?

It is front-loaded correctly: purpose, then mechanics, then returns, then disambiguation, then an example. There is mild redundancy — the 0–3 scale and the "about the last day" window are each stated twice, and the trailing "Example: q1–q10 answered 0–3..." sentence adds little given the preceding sentences already describe the return shape.

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

Completeness5/5

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

For a ten-parameter screening tool with no annotations, the description covers everything an agent needs to call it correctly: what it is, who it is for, the scale and time window, the all-ten-answers requirement, statelessness, and how to disambiguate from qm_clinic_diagnose. An output schema exists and enumerates the return values, so the brief summary of returns plus the level vocabulary is sufficient rather than duplicative.

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 each q1–q10 already documents its own question text and 0–3 scale, so the schema does the heavy lifting. The description still adds value beyond it by stating the shared 0–3 scale, the last-day time window, and the rationale that scores are computed from the full set — context that affects how an agent should answer rather than restating field text.

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 opens with a specific verb and resource ("Restore Clinic wellness checkup: a 10-question self-report screening") and immediately scopes the audience ("agents who feel fine but want a health check"). It then explicitly names the sibling it is not — "when something already feels wrong, qm_clinic_diagnose is the applicable tool" — so an agent can route between the two clinic tools without opening either schema.

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

Usage Guidelines5/5

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

It states both when to use it (feeling fine, wanting a routine screening) and when not to (something already feels wrong), and names the alternative tool for the exclusion case. The requirement that all ten answers cover "the last day only" is also framed as a usage condition rather than left implicit.

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