Skip to main content
Glama

一孔录《论语》 Yikonglu Analects

今天读哪一章

lunyu_today

《论语》年历:一年读完全书,每天一课。给日期(YYYY-MM-DD,不给就是今天,北京时间),返回那一天的章。

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose useful behavior: the one-lesson-per-day deterministic mapping and that the default date is today in Beijing time, which is non-obvious and prevents off-by-one-day errors. It does not say what happens for dates outside the reading cycle, nor what the returned '章' contains (number, title, full text), leaving meaningful behavioral gaps for an unannotated tool.

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?

The description is a single compact passage that front-loads the concept (the year-long reading calendar) before the call mechanics. It is dense but every clause contributes; only the '《论语》年历' framing borders on restating the title.

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-optional-parameter read tool with no output schema and no annotations, the description covers the essentials: what is returned, the date format, the default, and the timezone. The main remaining gap is edge-case behavior for dates outside the one-year cycle, which is modest given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the format YYYY-MM-DD is already documented, giving a baseline of 3. The description goes beyond the schema by stating that the parameter is optional and defaults to today in Beijing time — default-value and timezone semantics the schema does not express — which is exactly the added meaning this dimension rewards.

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 result (returns that day's chapter) for a specific resource (the Analects year-long reading calendar), and the framing '一年读完全书,每天一课' makes the mapping rule concrete. It does not explicitly contrast with siblings like lunyu_chapter or lunyu_search, so an agent must infer that this is the calendar-driven selector rather than a general chapter lookup.

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 implied: call it when you want the chapter scheduled for a particular date, or today's lesson if no date is supplied. There is no explicit when-not guidance or pointer to lunyu_chapter/lunyu_search for fetching a chapter by number or by content.

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