Skip to main content
Glama
Sign In

AcuiQ

by com.acuiq
OverviewDiscussionsAdmin

Search symptom names

search_symptoms
Read-onlyIdempotent

Resolve what a person describes into AcuiQ symptom names – the first step before search_protocols. Plain description works ("trouble sleeping", "my lower back hurts"): filler words are stripped and the search retries on the clinical words, reporting which term matched. Set popular=true for trending symptoms instead. Always returns an object with a symptoms array, empty when nothing matched. 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

NameRequiredDescriptionDefault
limitNoMax results (default 12, max 50)
queryNoWhat the person is describing – a symptom name or a plain description (e.g. "knee pain", "I cannot sleep at night")
popularNoSet to true to get trending symptoms instead of searching

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
  2. Changed1 schema field changed
    • addedInput schema / requireOneOf
      Added value: +[
+  "query",
+  "popular"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"What the person is describing — a symptom name or a plain description (e.g. \"knee pain\", \"I cannot sleep at night\")"New value: +"What the person is describing – a symptom name or a plain description (e.g. \"knee pain\", \"I cannot sleep at night\")"
  4. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Partial symptom name (e.g. \"head\", \"knee pain\")"New value: +"What the person is describing — a symptom name or a plain description (e.g. \"knee pain\", \"I cannot sleep at night\")"
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, closed-world), leaving the description to disclose the interesting behavior: filler words are stripped, the search retries on clinical words, the matched term is reported, and the result always contains a `symptoms` array that is empty on no match. The `guide` pointer and its create_checkout handoff are extra operational context not derivable from annotations.

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?

Four sentences, each carrying distinct load: purpose, query handling, popular mode, and return/routing behavior. The purpose and the sibling reference are front-loaded; the closing create_checkout sentence is the least essential but still guides agent behavior.

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, the description compensates by describing the return shape (`symptoms` array, empty on no match, optional `guide` pointer) and the follow-up action. Combined with full schema coverage, an agent has everything needed to call and use the tool.

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 description coverage is 100%, so the baseline is 3, but the description goes further by explaining how `query` is actually interpreted (plain phrasing accepted, filler stripped, retried on clinical terms) and reconfirms the `popular=true` switch as an alternative mode rather than a search filter. Only `limit` receives no added meaning.

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 gives a specific verb and resource ('Resolve what a person describes into AcuiQ symptom names') and explicitly positions the tool relative to siblings by calling itself 'the first step before search_protocols'. An agent can distinguish it from get_symptom_detail or search_protocols without opening any 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 names the when ('first step before search_protocols'), the alternative path ('Set popular=true for trending symptoms instead'), and a downstream routing rule ('mention it only if the person wants something to follow away from a screen, then call create_checkout with that `product` id'). When-to-use and when-not-to-use are both explicit.

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