Skip to main content
Glama

一孔录《论语》 Yikonglu Analects

这一章连着哪里

lunyu_related

按章号取这一章在全书关系表里的连线:本书互见、同问异答、人物、场合、别的书(三字经、道德经等)、异文、读法之争。

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": {
      "chapter": "<chapter>"
    },
    "name": "lunyu_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
chapterYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does convey meaningful behavior: the tool reads from a pre-built relationship table and returns categorized links rather than full text. But it is silent on whether the operation is read-only, what happens for a chapter with no connections or an invalid chapter number, and what the returned structure 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.

Conciseness4/5

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

One sentence, front-loaded with the action and parameter, followed by a compact enumeration of return categories. No filler. The list of content types is long but each item carries information, so the length is justified.

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?

The tool is simple (one required parameter, no nested objects) and has no output schema or annotations, so the description should stand in for both. It captures the return categories well, which is its main contribution, but leaves gaps around chapter-number format, empty/error cases, and return shape for a tool whose output is entirely undocumented elsewhere.

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 description coverage is 0% and the single parameter is a bare untyped string, so the description must compensate. "按章号" establishes that the parameter is a chapter number rather than a title or index, which is genuine added meaning. However, the expected format (e.g. 1.1, 学而第一) and validity rules are still unstated.

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 (取 / fetch by chapter number) and resource (this chapter's connection lines in the whole-book relationship table), then enumerates exactly what those connections are: intra-book cross-references, same-question-different-answers, persons, occasions, other books, textual variants, and reading disputes. That is enough to distinguish it in practice from lunyu_chapter (text) and lunyu_search (lookup), though no sibling is named explicitly.

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?

Usage is only implied: the enumerated content types suggest you call this when you want cross-references rather than the chapter text. There is no explicit when-to-use statement, no when-not-to-use, and no mention of alternatives such as lunyu_chapter for the raw passage.

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