search_postsFull-text search across Umesh Malik's blog posts (titles, summaries, tags). Returns matching posts with slug, title, URL, summary, tags and publish date. Use for topics like AI engineering, LLMs, RAG, Claude Code, fine-tuning, or web development.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results (default 10, max 30). | |
| query | Yes | Search terms. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It discloses the search scope (titles, summaries, tags) and return fields, but does not mention ordering, matching behavior, pagination, or error handling. This is moderate transparency but lacks deeper behavioral traits that would fully inform the agent.
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 two sentences, front-loaded with the core action and return fields, followed by concrete usage examples. Every sentence contributes to understanding, with no fluff or redundancy.
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 search tool with two parameters and no output schema, the description adequately explains what it does, what it returns, and when to use it. It lacks explicit sorting/pagination details, but the schema covers limit. Overall, it is complete enough for an agent to select and invoke correctly.
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?
Input schema coverage is 100%, providing descriptions for both query and limit. The description adds value by explicitly stating that the query searches across titles, summaries, and tags, which enriches the meaning of the 'search terms' parameter beyond the schema's generic 'Search terms.' This goes beyond the baseline for high coverage.
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 clearly states the tool performs 'Full-text search across Umesh Malik's blog posts' and specifies the exact fields searched (titles, summaries, tags) and returned (slug, title, URL, summary, tags, publish date). This verb+resource combination distinguishes it from siblings like get_post and list_topics, making its purpose unambiguous.
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 provides explicit example topics for when to use the tool ('AI engineering, LLMs, RAG, Claude Code, fine-tuning, or web development'), which gives clear context for selection. However, it does not explicitly mention alternatives or when not to use it, though sibling names imply differentiation.
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.
Each tool has a clearly distinct purpose: fetching a specific post by slug, retrieving the profile, listing topic hubs, and searching posts. There is no overlap or ambiguity in their roles.
All tool names follow a consistent verb_noun pattern in lowercase snake_case (get_post, get_profile, list_topics, search_posts). No deviations or mixed conventions.
Four tools is well-scoped for a personal blog and profile server. Each tool covers a distinct, necessary function, and the count feels neither sparse nor excessive for the domain.
The server provides complete read-only coverage for its purpose: searching posts, retrieving full posts, listing topic hubs, and accessing the profile. There are no obvious gaps in the content-access lifecycle.