Skip to main content
Glama
Meta-consciousness-AI

mcai-knowledge

Official
by Meta-consciousness-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

检索术语

mcai_search
Read-onlyIdempotent

Search MCAI glossary concepts by Chinese keywords, English terms, or aliases, with taxonomy filters, to confirm approximate term names before retrieving full entries.

Instructions

在术语库中检索概念，支持中文关键词、英文词与别名，可按体系过滤。适合用户只记得大概说法、或需要先确认术语名称时使用。分工：拿到术语名后用 mcai_concept 取完整词条；整句问题用 mcai_answer；看全目录用 mcai_list。边界：只做词条匹配，不做语义推理。

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数上限，默认 8，范围 1–30。
queryYes检索关键词（建议 2–20 字，不要传整句），支持中文、英文或别名，例如 元意识 / progenerative agent / 序生。
categoryNo按体系过滤，取值必须是：元意识体系 / 本体论模型 / 序生体系 / 元子社会；留空则返回全部

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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: +[
+  "元意识",
+  "序生"
+]
  2. 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 / 序生"
  3. 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=true, idempotent=true, openWorld=false, so safety is covered. The description adds context beyond that: the tool only matches entries and performs no semantic reasoning, which tells the agent how to interpret weak or empty results. It stops short of describing result shape or behavior when no match is found.

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 purpose in the first clause, then labeled 分工 and 边界 segments that make scanning trivial. Every sentence carries distinct information; nothing is repeated from the schema verbatim.

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 search with no output schema, the description covers purpose, triggers, alternatives, and the hint that results are entry names to be expanded via mcai_concept. It does not describe what a result row contains or what happens on zero matches, a minor but real gap.

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 examples (元意识 / progenerative agent / 序生), the 2–20 character guidance, and the exact category enum values. The description's "支持中文关键词、英文词与别名，可按体系过滤" largely restates that, so baseline 3 applies with no meaningful addition.

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 (检索概念 in 术语库) plus the supported query forms and filter capability, which is far more than the tautological title 检索术语. It also names the siblings it is not (mcai_concept, mcai_answer, mcai_list), so an agent can route without opening a 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 condition ("适合用户只记得大概说法、或需要先确认术语名称时"), explicit division of labor naming three alternatives and what each is for, and an explicit boundary ("只做词条匹配，不做语义推理"). This is exactly the when-to-use/when-not pattern.

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

Deploy Server

Other Tools