get_commandsReturn just the runnable commands and code blocks from the best-matching article or cheatsheet — no prose. Use when the user wants the command, not the explanation.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max code blocks to return (default 6, max 12). | |
| topic | Yes | Topic or tool, e.g. docker, kubectl, terraform, psql. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare safe, idempotent read-only behavior. The description adds meaningful behavioral context: it returns only runnable commands and code blocks, excludes prose, and selects from a best-matching article or cheatsheet. It goes beyond the annotations without contradicting them.
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 short, front-loaded sentences carry all the key information: what is returned, what is excluded, and when to use the tool. There is no filler or redundant restating of the title.
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?
For a simple tool with only two parameters, a complete schema, and sufficient annotations, the description is largely complete. It could mention what happens if no matching article is found or clarify 'best-matching', but these are minor omissions given the low complexity.
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 description coverage is 100%, so the schema already fully documents 'topic' and 'limit' including default and maximum. The description adds no additional parameter-level meaning, so the baseline of 3 is appropriate.
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?
The description uses a specific verb ('Return') with a precise resource ('runnable commands and code blocks from the best-matching article or cheatsheet') and explicitly contrasts itself with prose. This clearly distinguishes it from siblings like read_post and get_cheatsheet.
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?
It gives an explicit usage condition: 'Use when the user wants the command, not the explanation.' This provides clear context, though it does not name an alternative tool to use when the user does want the explanation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clear, distinct purposes: search, browse by tag, read, cheatsheets, related posts, and quiz. The only mild overlap is between browse_by_tag and search_posts, but their descriptions make the distinction clear. get_commands also overlaps slightly with get_cheatsheet and read_post, but it explicitly limits output to commands only.
Tool names follow a consistent verb_noun pattern throughout: list_*, get_*, search_posts, read_post, related_posts, random_post, quiz_me. The naming convention is uniform and predictable, making the tool set easy to navigate for an agent.
11 tools is well-scoped for a blog-focused server. Each tool serves a distinct content-access or discovery need without feeling bloated or redundant. The count feels appropriate for the domain.
The server covers the core blog workflow well: discovering topics, searching posts, browsing tags, reading full content, extracting commands, and finding related content. A minor gap is the lack of a simple 'list all posts' endpoint, but list_recent, browse_by_tag, and search_posts provide sufficient alternatives.