get_blogsFetch the latest spaceflight blog posts sorted by publication date. Returns title, summary, URL, image, and source.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of blog posts to return (default 10, max 100) |
| Name | Required | Description | Default |
|---|---|---|---|
| blogs | Yes | ||
| total | Yes | Total number of blog posts available | |
| returned | Yes | Number of blog posts returned in this response |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds useful behavioral context: sorting by publication date and the exact return fields (title, summary, URL, image, source). This 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?
The description is two concise sentences, front-loaded with the action and resource, and every word adds value. It avoids redundancy and is appropriately sized 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?
Given the tool's simplicity (one optional parameter, strong annotations, and an output schema), the description is complete. It covers all essential aspects: what is fetched, sorting, and return fields, without missing critical information.
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 input schema fully describes the single optional 'limit' parameter with default and max values. The description does not add additional parameter-level semantics, relying on the schema's 100% coverage, so a baseline score 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 clearly states the specific action ('Fetch') and resource ('latest spaceflight blog posts'), and distinguishes it from siblings like get_articles by specifying the 'spaceflight' domain. It also mentions the sorting criterion, making the 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 implies when to use this tool: when the latest spaceflight blog posts are needed. It provides clear context but does not explicitly mention alternatives or exclusions, such as when to use search_articles instead for more specific queries.
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.
Several tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research. While each has distinct nuances, they could be confused by an agent.
Most tools use snake_case, but the naming pattern is inconsistent (e.g., bet_research vs. polymarket_arbitrage vs. ai_visibility_check). There is no strong verb_noun pattern across the set.
34 tools is high given the server's stated purpose ('spacenews'). Only a few tools directly relate to space news; the bulk are general-purpose Pipeworx utilities, making the scope too broad.
For a space news server, the tool surface is incomplete: only get_articles, get_blogs, and search_articles are relevant. Missing tools for article details, source filtering, or categories. The extensive general tools don't make up for this gap.