Skip to main content
Glama

一孔录《论语》 Yikonglu Analects

按字句查《论语》

lunyu_search

按章号、原文里的字句或白话里的词,查《论语》的章。返回章号、标题、原文和网址。底本是朱熹《论语集注》(《四部备要》本),全书 498 章。

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": "lunyu_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes章号(如 1.1)或几个字(如 学而时习之)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It does disclose the corpus size (498 chapters) and the base edition (朱熹《论语集注》/《四部备要》本), which helps the agent judge recall and citation fidelity, but it omits matching semantics (substring vs. fuzzy), result ordering, and no-match behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the main capability and followed by return fields and corpus provenance; little waste. The edition and chapter-count sentences are secondary but do earn their place as context.

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

Completeness3/5

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

With no output schema and no annotations, the description does well to enumerate returned fields (章号、标题、原文、网址). Gaps remain around the undocumented limit parameter and result/matching behavior, which matter for a search tool.

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 50%. The description usefully extends the query parameter beyond the schema by adding vernacular-word matching, which the schema does not mention. The limit parameter, however, is undocumented in both the schema and the description, so coverage is not fully compensated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource (查《论语》的章 = look up chapters of the Analects) and enumerates the three query modes: chapter number, original-text wording, and vernacular wording. It does not distinguish the tool from its sibling lunyu_chapter, which appears to be the by-chapter-number lookup, so the agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The three query modes imply when to use this tool (lookup by number, original text, and vernacular translation), which usefully signals the vernacular reverse-lookup capability. However, the description never states when to prefer this tool over lunyu_chapter, nor what to do when no match exists.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources