Skip to main content
Glama

Get a concept entry

mcai_concept
Read-onlyIdempotent

Fetches the detailed knowledge-base entry for an exact concept term, alias, or slug, including definition, aliases, sources, quotations, and relations; returns an explicit error when no match exists.

Instructions

Get the complete entry for a single concept by term, alias, or slug: definition, aliases, sources, source quotations, and relations. Use when the exact term is known and full detail is needed. Routing: if the spelling is uncertain use mcai_search first; for full-sentence questions use mcai_answer; for relations only use mcai_related. Boundary: returns only entries in this knowledge base, with an explicit error when not found.

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": {
      "term": "<term>"
    },
    "name": "mcai_concept"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesExact term, alias, or slug, e.g. 元意识 / MCAI / meta-consciousness; use mcai_search first if unsure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.5
    • changedInput schema / properties / term / description
      Previous value: -"精确的术语名、别名或 slug,例如 元意识 / MCAI / meta-consciousness;不确定写法时先用 mcai_search。"New value: +"Exact term, alias, or slug, e.g. 元意识 / MCAI / meta-consciousness; use mcai_search first if unsure."
  2. Changed2 schema fields changedv0.1.2
    • changedInput schema / properties / term / description
      Previous value: -"术语名、别名或 slug,例如 元意识 / MCAI / meta-consciousness"New value: +"精确的术语名、别名或 slug,例如 元意识 / MCAI / meta-consciousness;不确定写法时先用 mcai_search。"
    • addedInput schema / properties / term / examples
      Added value: +[
      +  "元意识",
      +  "meta-consciousness"
      +]
  3. Changed2 schema fields changedv0.1.1
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / term / description
      Previous value: -"术语、别名或 slug,如 元意识 / MCAI / meta-consciousness"New value: +"术语名、别名或 slug,例如 元意识 / MCAI / meta-consciousness"
  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 establish read-only, idempotent, closed-world behavior, so the bar is lower; the description still adds useful context about the lookup boundary and the explicit not-found error. It does not discuss lookup fuzzy-matching limits, but nothing contradicts the annotations.

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 tight sentences, front-loaded with the outcome, then the usage condition, then routing and boundary. Every clause carries routing or scope information; no 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?

With no output schema, the description compensates by listing the returned fields and the not-found failure mode, which is enough to call the tool confidently. Slightly thinner on formatting of the quotations/relations payload, but no material 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 `term` as exact term, alias, or slug with examples, so the description's "by term, alias, or slug" is largely a restatement. Baseline 3 applies since the schema carries the parameter detail.

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 ("Get the complete entry for a single concept") and enumerates the payload (definition, aliases, sources, quotations, relations), which makes it immediately distinguishable from mcai_search and mcai_related.

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 an explicit use condition ("when the exact term is known and full detail is needed") plus concrete routing: mcai_search for uncertain spelling, mcai_answer for full-sentence questions, mcai_related for relations only. It also declares a boundary (only this knowledge base, explicit not-found error).

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