get_blog_postGet the full Markdown body of one published blog post by its slug. Free; does not consume API quota. Content is an original AI synthesis with no verbatim community quotes.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Article slug, taken from list_blog_posts results. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnly, idempotent, and non-destructive safety. The description adds meaningful traits: 'Free; does not consume API quota' (cost/rate-limit behavior) and 'Content is an original AI synthesis with no verbatim community quotes' (content provenance). These go beyond annotations.
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?
Three short sentences, each adding a distinct fact (what is returned, cost, content nature). No fluff or repetition; the size is appropriate for the tool's simplicity.
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?
The tool is simple with one parameter, and the annotations plus output schema carry substantial structured info. The description covers the return format (Markdown body), cost, and content nature, making it complete for an agent.
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 schema fully documents 'slug' as coming from list_blog_posts. The description adds the constraint 'published', clarifying that only published posts are retrievable, which is extra semantic information 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?
The description specifies the action ('Get'), the resource ('blog post'), and the exact scope ('full Markdown body by slug'), clearly distinguishing it from sibling tools like list_blog_posts. It is a specific verb+resource with no ambiguity.
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 context is clear: use this when you have a specific slug and need the full Markdown body. The schema note about slug coming from list_blog_posts implies a follow-up workflow, but the description does not explicitly mention alternatives or when-not-to-use conditions.
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 distinct purpose: get_overview provides a landscape map, get_theme dives into a specific theme, list_trending_themes shows hot themes, get_opportunity gives full detail on an opportunity, and query_opportunities enables filtered search. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (get_overview, get_theme, list_trending_themes, get_opportunity, query_opportunities), making them predictable and easy to understand.
With 5 tools, the server is well-scoped for its domain of market signal analysis. Each tool serves a clear function without redundancy or unnecessary complexity.
The tool set covers the full workflow: overview, theme exploration, trending themes, detailed opportunity views, and searchable filtering. All key operations for the domain are present with no obvious gaps.