Receive a grounded reflection prompt connected to Tao Te Ching chapters or a chosen topic, inviting personal agency while avoiding diagnosis or professional care.
Return a grounded reflection prompt connected to one or more chapters. The prompt invites agency and does not diagnose or replace professional care.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | No | Optional topic such as letting-go, leadership, or relationships | |
| chapter | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It adds a useful boundary that the prompt does not diagnose or replace professional care, but it does not explain how chapters are matched, what 'grounded' means, or whether output is deterministic.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two efficiently written sentences with no wasted words. The core action is front-loaded)Skip, and the safety caveat earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Reasonable for a simple tool with two optional parameters, but ambiguity remains about how a single chapter parameter maps to 'one or more chapters,' and with no output schema the return value is only broadly described.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 50%; the description mentions 'one or more chapters' but the schema only provides a single integer chapter parameter. It does not explain how topic and chapter interact or what each contributes, adding minimal meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Return') and resource ('grounded reflection prompt') connected to chaptersinates it from siblings like get_chapter or search_chapters by focusing on reflection prompts, though it does not explicitly name any sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for generating reflection prompts tied to chapters, but gives no explicit when-to-use, when-not-to-use, or alternatives. The context is clear, but no exclusion criteria or selection guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.