Skip to main content
Glama

AcuiQ

by com.acuiq
OverviewDiscussionsAdmin

Find treatment protocols

search_protocols
Read-onlyIdempotent

Find acupuncture protocols for given symptom names – the same ranked pipeline behind GET /api/protocols. Returns matches (each with point codes, cred, dosage and provenance: sourceKind, source, caveat) plus a points dictionary giving each referenced code its name, meridian, location and warnings ONCE. Ten matches by default; raise limit (max 50) if you need more. directMatches lists indicated points when no protocol covers the query – index entries, not prescriptions. Pass symptom names from search_symptoms, not a description. When the symptom is covered by a $5 mini-guide, the result carries a guide pointer – mention it only if the person wants something to follow away from a screen, then call create_checkout with that product id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoPatient age. Drops protocols whose recorded cohort age is more than 20 years away; rows that recorded no age are kept.
sexNoPatient sex. Drops protocols recorded in the opposite sex; rows that recorded no sex are kept.
limitNoMax protocols to return (default 10, max 50)
symptomsYesComma-separated symptom names, max 10 (e.g. "headache,neck pain")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / age / description
      Previous value: -"Patient age for demographic filtering"New value: +"Patient age. Drops protocols whose recorded cohort age is more than 20 years away; rows that recorded no age are kept."
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max protocols to return (default 10, max 50)",
+  "type": "number"
+}
    • changedInput schema / properties / sex / description
      Previous value: -"Patient sex for demographic filtering"New value: +"Patient sex. Drops protocols recorded in the opposite sex; rows that recorded no sex are kept."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by detailing the return shape: matches with provenance, a points dictionary deduplicated and emitted once, directMatches as index entries rather than prescriptions, a default limit of 10, and a guide pointer for mini-guides. This gives the agent a clear model of what the call will and will not do.

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?

Dense but efficient: every sentence earns its place, and the most critical scoping ('for given symptom names', 'same ranked pipeline') is front-loaded. The later sentences pack return-structure, caveats, and cross-tool routing without padding.

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?

With no output schema present, the description carries the full burden of explaining the response and does so thoroughly: matches, points, directMatches, guide pointer, and the create_checkout follow-up. It also covers input provenance and limit behavior, making the tool safely callable without further inference.

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?

The input schema already documents all four parameters with 100% coverage, so the baseline is 3. The description adds an important semantic constraint beyond the schema — symptom names must come from search_symptoms, not a description — and reinforces the limit default/maximum, lifting it to 4.

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: 'Find acupuncture protocols for given symptom names' and ties it to the ranked pipeline behind GET /api/protocols. The description also distinguishes it from search_symptoms by instructing that symptom names must come from that tool, so an agent can keep siblings apart.

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?

Gives explicit input guidance: pass symptom names from search_symptoms, not a free-text description. It also provides conditional routing, telling the agent to call create_checkout with the product id only when the user wants the $5 mini-guide away from a screen.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AcuiQ toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources