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, modality and course where the source states them, 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.8/5.0
Behavior5/5

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

With no output schema, the description carries the return-shape burden and does so: `matches`, per-match provenance (sourceKind/source/caveat), a deduplicated `points` dictionary, `directMatches` semantics as index entries rather than prescriptions, and the conditional `guide` pointer. It also discloses default (10) and cap (50) result counts, which goes beyond the annotations' safety profile.

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-loaded with purpose and return shape, and nearly every clause carries new information. It is one dense block, though, and the final sentence about the guide pointer is long enough that a reader must parse it carefully – efficient but slightly overloaded.

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 read-only, non-open-world tool with no output schema, the description covers invocation (required symptom names), result volume controls, the full returned structure, and the cross-tool handoff to create_checkout. Nothing an agent needs to call or interpret it correctly is missing.

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%, so the baseline is 3; the description still adds meaning by specifying that `symptoms` must be symptom names sourced from search_symptoms and by restating the limit default/max in context. It does not add anything for `age`/`sex` beyond the schema's own cohort-filter descriptions.

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+resource+scope ('Find acupuncture protocols for given symptom names') and even names the underlying pipeline (GET /api/protocols). It differentiates itself from search_symptoms by insisting on symptom names rather than a free-text description, so an agent can route correctly without opening schemas.

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?

Explicit routing: use search_symptoms to obtain the symptom names to pass here, not a natural-language description. It also names the downstream alternative (create_checkout) and the exact condition that should trigger it (only when the person wants something to follow 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