Skip to main content
Glama

List all terms

mcai_list
Read-onlyIdempotent

List knowledge base terms, optionally filtered by category, to show coverage or let users choose from a catalog; returns term names and categories only, not full definitions.

Instructions

List all terms in the knowledge base, optionally filtered by category, to show coverage or let the user choose from a catalog. Use when the user asks "What concepts does this theory have?" or "What do you cover?". Routing: keyword lookup -> mcai_search; full entry -> mcai_concept. Boundary: returns term names and categories only, not full definitions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mcai_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoFilter by category; must be one of: 元意识体系 / 本体论模型 / 序生体系 / 元子社会; leave empty for all categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • changedInput schema / properties / category / description
      Previous value: -"按体系过滤,取值必须是:元意识体系 / 本体论模型 / 序生体系 / 元子社会;留空则返回全部"New value: +"Filter by category; must be one of: 元意识体系 / 本体论模型 / 序生体系 / 元子社会; leave empty for all categories."
  2. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / category / description
      Previous value: -"按体系过滤:元意识体系 / 本体论模型 / 序生体系 / 元子社会;留空则返回全部"New value: +"按体系过滤,取值必须是:元意识体系 / 本体论模型 / 序生体系 / 元子社会;留空则返回全部"
  3. Changed2 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / category / description
      Added value: +"按体系过滤:元意识体系 / 本体论模型 / 序生体系 / 元子社会;留空则返回全部"
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so safety is covered by structured data. The description adds the one thing annotations cannot: the payload boundary that only term names and categories come back, not definitions. It stops short of describing ordering, total counts, or pagination, which keeps it at 4.

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?

Three sentences, front-loaded with the action and scope, then trigger examples, then routing and boundary. Every clause carries distinct information and nothing is repeated between the title and body.

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 single optional-parameter list tool with no output schema, the description supplies purpose, triggers, alternatives, and the return granularity. There is no gap an agent would need to guess at in order to call it correctly.

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 category parameter already enumerates its four allowed values. The description only restates that filtering is optional and by category, adding no format or behavior detail beyond the schema. 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 ("List all terms in the knowledge base") plus the optional category scope and the intended outcome (coverage view or catalog selection). It draws the line against mcai_search and mcai_concept explicitly, so an agent can route without inspecting either 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?

Gives both a positive trigger (user asks "What concepts does this theory have?" or "What do you cover?") and a routing table: keyword lookup -> mcai_search, full entry -> mcai_concept. It also states a boundary case (names and categories only, not full definitions), so when-not-to-use is covered.

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