read_postRead a post's full text by URL, paginated. Returns a window of characters; call again with the returned next offset to continue.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Post URL or path, e.g. /posts/aurora-postgresql-setup-guide/. | |
| offset | No | Character offset to start from (default 0). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context beyond annotations by explaining the paginated chunking mechanism and the need to use the returned next offset to continue reading. It does not cover edge cases like end-of-post handling, but the added pagination detail earns above-average credit.
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?
The description is a single, tightly written sentence that front-loads the primary action, states the resource, and includes the pagination behavior. Every clause earns its place, with no filler or redundant phrasing.
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 read-only tool with two simple parameters and no nested objects, the description covers the essential calling pattern: provide a URL, optionally use offset, and iterate with the returned next offset. It does not mention how to detect the end of the post or the exact format of the returned window, but given the lack of an output schema and the tool's simplicity, the description is reasonably complete.
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 documents url and offset. The description adds value beyond the schema by explaining the semantics of offset in the context of pagination ('Returns a window of characters; call again with the returned next offset to continue'), which clarifies how the offset parameter is meant to be used in practice.
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 states a specific verb ('Read'), a specific resource ('a post's full text by URL'), and a key behavioral trait (pagination). It clearly distinguishes itself from sibling tools like search_posts, random_post, and related_posts by requiring a URL and focusing on full-text retrieval rather than discovery or listing.
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?
The description implies usage: when you have a post URL and want to read its content. It also gives a pagination usage note ('call again with the returned next offset'), but it does not explicitly state when to prefer this tool over alternatives such as search_posts or related_posts, nor does it mention exclusions or prerequisites beyond having a URL.
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.