Skip to main content
Glama

Search terms

mcai_search
Read-onlyIdempotent

Search concepts in a term base by Chinese keywords, English terms, or aliases, and filter results by category to find approximate names or confirm terminology.

Instructions

Search concepts in the term base. Supports Chinese keywords, English terms, and aliases; results can be filtered by category. Use when the user remembers only an approximate name or needs to confirm a term. Routing: with a term in hand use mcai_concept for the full entry; for full-sentence questions use mcai_answer; for the whole catalog use mcai_list. Boundary: term matching only, no semantic reasoning.

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": {
      "query": "<query>"
    },
    "name": "mcai_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results, default 8, range 1–30.
queryYesSearch keywords (2–20 characters recommended; do not pass a full sentence). Supports Chinese, English, or aliases, e.g. 元意识 / progenerative agent / 序生.
categoryNoFilter by category; must be one of: 元意识体系 / 本体论模型 / 序生体系 / 元子社会; leave empty for all categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.5
    • changedInput schema / properties / category / description
      Previous value: -"按体系过滤,取值必须是:元意识体系 / 本体论模型 / 序生体系 / 元子社会;留空则返回全部"New value: +"Filter by category; must be one of: 元意识体系 / 本体论模型 / 序生体系 / 元子社会; leave empty for all categories."
    • changedInput schema / properties / limit / description
      Previous value: -"返回条数上限,默认 8,范围 1–30。"New value: +"Maximum number of results, default 8, range 1–30."
    • changedInput schema / properties / query / description
      Previous value: -"检索关键词(建议 2–20 字,不要传整句),支持中文、英文或别名,例如 元意识 / progenerative agent / 序生。"New value: +"Search keywords (2–20 characters recommended; do not pass a full sentence). Supports Chinese, English, or aliases, e.g. 元意识 / progenerative agent / 序生."
  2. Changed4 schema fields changedv0.1.2
    • changedInput schema / properties / category / description
      Previous value: -"按体系过滤:元意识体系 / 本体论模型 / 序生体系 / 元子社会;留空则返回全部"New value: +"按体系过滤,取值必须是:元意识体系 / 本体论模型 / 序生体系 / 元子社会;留空则返回全部"
    • changedInput schema / properties / limit / description
      Previous value: -"返回条数上限,默认 8,范围 1–30"New value: +"返回条数上限,默认 8,范围 1–30。"
    • changedInput schema / properties / query / description
      Previous value: -"检索关键词,支持中文、英文或别名,例如 元意识 / progenerative agent / 序生"New value: +"检索关键词(建议 2–20 字,不要传整句),支持中文、英文或别名,例如 元意识 / progenerative agent / 序生。"
    • addedInput schema / properties / query / examples
      Added value: +[
      +  "元意识",
      +  "序生"
      +]
  3. Changed4 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / category / description
      Previous value: -"可选:元意识体系 / 本体论模型 / 序生体系 / 元子社会"New value: +"按体系过滤:元意识体系 / 本体论模型 / 序生体系 / 元子社会;留空则返回全部"
    • addedInput schema / properties / limit / description
      Added value: +"返回条数上限,默认 8,范围 1–30"
    • addedInput schema / properties / query / description
      Added value: +"检索关键词,支持中文、英文或别名,例如 元意识 / progenerative agent / 序生"
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context that annotations cannot express: what matching strategy is used and that no semantic reasoning occurs. It stops short of describing result shape or what a zero-hit response looks like.

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?

Four compact sentences, front-loaded with the core action, then usage trigger, then routing, then boundary. Each sentence carries distinct information with no redundancy or filler.

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

Completeness4/5

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

For a three-parameter read-only search with full schema coverage and rich annotations, the description covers purpose, triggers, alternatives, and matching scope. The only gap is the absence of any hint about result shape or behavior on no matches, which matters slightly since there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents query formats, category enum values, and the limit range with defaults. The description's mention of Chinese keywords, English terms, aliases, and category filtering largely restates what the schema says, adding little beyond it. Baseline 3 applies when the schema does the heavy lifting.

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 ("Search concepts in the term base") plus the supported input forms and the category filter. The routing sentence makes it clearly distinguishable from mcai_concept, mcai_answer, and mcai_list 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?

Explicit trigger conditions are given ("when the user remembers only an approximate name or needs to confirm a term") along with per-sibling routing rules for the three alternatives. The boundary sentence ("term matching only, no semantic reasoning") further excludes misuse for full-sentence questions.

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