get_dispatchesFetch the latest dispatches (news feed) from Super Earth high command. Returns recent dispatches with their published date (relative time) and message text. Optional limit parameter caps how many items to return (default 20, max 50).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of dispatches to return. Default 20, max 50. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the tool returns published dates as relative time and message text, and specifies the default and maximum for the limit parameter. This is adequate for a read-only fetch, though it doesn't cover potential side effects or rate limits.
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 concise and well-structured: two sentences that first state the purpose and then cover return format and parameter behavior. No unnecessary words.
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 one optional parameter and no output schema, the description fully explains what it returns, the parameter's behavior, and the source. It is sufficiently complete for an agent to 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?
Schema description coverage is 100% and fully documents the limit parameter with default and max values. The description merely repeats this information, adding no additional semantic value 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 clearly states the action ('Fetch') and resource ('dispatches (news feed)'), and it distinguishes itself from sibling tools like get_assignments or get_war_status by focusing on news feed items from Super Earth high command.
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 clear context for when to use the tool (fetching latest dispatches) and implies it is for news feed content. However, it does not explicitly exclude alternatives or name sibling tools, so it falls short of a 5.
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 targets a distinct resource: planets list vs. planet details vs. war status vs. assignments vs. dispatches vs. space station vs. Steam news. No two tools overlap in purpose; the only potential confusion between get_all_planets and get_war_status is resolved by one providing the full list and the other focusing on active war statistics.
All tool names follow the same 'get_' + descriptive noun pattern, e.g., get_all_planets, get_planet_details, get_war_status. This is perfectly uniform and predictable.
Seven tools is an appropriate number for this read-only game data server. Each tool covers a distinct aspect of the Helldivers 2 war data, and none feel redundant or excessive.
The set covers the full scope of publicly available read-only data for Helldivers 2: all planets, detailed planet info, war status, assignments, dispatches, space station details, and Steam news. There are no obvious gaps for the server's stated purpose.