Skip to main content
Glama

一孔录《论语》 Yikonglu Analects

取一章的全部底子

lunyu_chapter

按章号取一章:原文、分句、白话、一孔录的读法(一孔按)、读音、朱熹注引文和它在底本的页码、原页图地址。回答时请照 credit 一行署名。

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_chapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
chapterYes章号,朱注分章,如 1.1、12.1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the complete return composition and an explicit attribution obligation ("照 credit 一行署名"), which is genuinely useful behavior beyond a bare read hint, but it says nothing about invalid chapter numbers, error responses, or output format/structure.

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?

A single dense sentence front-loads the retrieval action, then lists payload contents, then closes with the credit requirement. Every clause carries information, though the long enumeration is undifferentiated prose rather than a structured list.

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 one-parameter read tool with no output schema, the enumeration of returned fields plus the citation instruction covers what an agent needs to call it and use the result. Only failure behavior for a bad chapter number is unaddressed.

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 100% and the schema already explains the chapter format with the example "1.1、12.1". The description only restates "按章号取一章" and adds no syntax, range, or edge-case detail (e.g. whether 1.10 or trailing forms are accepted) beyond the schema.

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 ("按章号取一章") and enumerates exactly what comes back: 原文、分句、白话、一孔按、读音、朱熹注引文、底本页码、原页图地址. That is far more specific than the sibling names (search/related/today) and lets an agent tell it retrieves a single chapter's full payload.

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 phrase "按章号" implies the precondition (you must have a chapter number), but there is no explicit when-to-use/when-not guidance and no named alternative such as lunyu_search for when the agent only has a topic rather than a chapter number. Usage is inferable but not stated.

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