beook_list_booksLists beook courses with their chapters and completed exercise counts, helping users review progress and navigate available books.
List the books (courses) in beook with their chapters and how many exercises are done.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true already covers the safety profile, so the description's added value is in disclosing the return payload: chapters plus completed-exercise counts. That is meaningful behavioral context an agent cannot get from the annotations or the empty schema. Minor gap is no note on ordering or volume of results.
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?
One sentence, front-loaded with the primary action and followed immediately by the shape of the result. No filler or restatement of the tool name alone.
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?
With no output schema and no parameters, the description carries the burden of describing the return value, and it does so (chapters, completed exercise counts). It is nearly complete; only ordering, pagination, and error/auth conditions are unaddressed.
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?
The tool takes zero parameters, so there is nothing for the description to explain beyond call semantics; baseline of 4 applies. The description correctly implies no filtering inputs are needed.
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 (List) and resource (books/courses) and even clarifies the domain synonym 'courses', which disambiguates terminology. It does not explicitly contrast itself with beook_list_exercises, but the resource named is distinct enough that an agent can tell them apart.
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?
Usage is only implied: this is the natural entry point to survey available books and progress. There is no explicit statement of when to prefer it over beook_list_exercises or beook_status, and no prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.