Skip to main content
Glama
Sign In

AcuiQ

by com.acuiq
OverviewDiscussionsAdmin

Search the wiki

search_wiki
Read-onlyIdempotent

Keyword search across the AcuiQ reference wiki: the first call when you know what you are looking for but not where it lives. Matches titles and body prose, ranked in four tiers: titles starting with the term, titles containing it, literal body hits, then English full-text hits by relevance, which stem words and drop stopwords. Not semantic: one distinctive word beats a sentence. Each row carries a path, its size in chars and a snippet windowed on the match. Feed the paths to get_pages in one call rather than looping get_page. Narrow with tagPath when a term is common. Defaults: page 1, pageSize 20 (max 50); keep paging while hasMore is true.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number (default 1)
queryYesSearch term, matched against page titles and body text
tagPathNoOnly pages at this tag path, e.g. a path from get_categories
pageSizeNoResults per page (default 20, max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / page / maximum
      Removed value: -1000
    • changedInput schema / properties / pageSize / description
      Previous value: -"Results per page (default 10, max 50)"New value: +"Results per page (default 20, max 50)"
    • changedInput schema / properties / query / description
      Previous value: -"A keyword, phrase or question (e.g. \"cupping\", \"is acupuncture safe in pregnancy\")"New value: +"Search term, matched against page titles and body text"
    • addedInput schema / properties / tagPath
      Added value: +{
+  "description": "Only pages at this tag path, e.g. a path from get_categories",
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / page / maximum
      Added value: +1000
    • addedInput schema / properties / page / minimum
      Added value: +1
    • addedInput schema / properties / pageSize / maximum
      Added value: +50
    • addedInput schema / properties / pageSize / minimum
      Added value: +1
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent, but the description adds substantial context beyond them: the exact four-tier ranking order, stemming and stopword handling, and the shape of each result row (path, chars, snippet windowed on the match). Paging behavior (defaults, pageSize max, keep paging while hasMore) is disclosed.

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?

Front-loaded with the purpose, then ranking rules, then result shape, then follow-up and parameters. Dense but every sentence carries actionable information; no rhetorical filler.

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?

No output schema exists, but the description describes the result row fields and the paging signal (hasMore). Combined with annotations covering safety and a fully documented schema, an agent has everything needed to invoke, page, and hand off to get_pages.

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 goes beyond it by explaining the practical role of tagPath (narrowing a common term) and by restating the paging defaults and the hasMore continuation rule in context.

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 ('keyword search across the AcuiQ reference wiki') and immediately scopes the match behavior (titles and body prose), distinguishing it from get_page/get_pages and the search_protocols/search_symptoms siblings.

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?

Explicitly names when to use it ('first call when you know what you are looking for but not where it lives'), when to narrow ('use tagPath when a term is common'), and the follow-up workflow ('feed the paths to get_pages in one call rather than looping get_page'). It also gives a negative guideline: not semantic, so one distinctive word beats a sentence.

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