get_assignmentsFetch the currently active assignments (Major Orders) issued by Super Earth high command. Returns each assignment with title, briefing, task description, decoded task list (type and value information including races, difficulties, and target planet names), current progress numbers, reward (type and amount), and expiration (seconds until expiry).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 provided, the description carries the full transparency burden. It clearly indicates a read-only 'Fetch' operation and thoroughly enumerates all returned data fields, including task list details and expiration. It lacks only explicit statements about error cases or empty results, but is otherwise transparent.
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: the first states the action and object, the second lists all return components. Every word adds value, with no filler 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?
Despite having no output schema and no annotations, the description covers essential output semantics, including task list decoded details, progress, rewards, and expiry. For a zero-input tool, this is a comprehensive and self-contained description.
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 tool has zero parameters and an empty schema, so baseline is 4. The description adds no parameter information, which is acceptable since there are no inputs to document; it implicitly communicates that no arguments are needed.
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?
Description starts with 'Fetch' and clearly identifies the resource as 'currently active assignments (Major Orders)', which is a specific verb+resource pairing. It also lists all key return fields, effectively distinguishing this tool from sibling tools focused on planets, dispatches, etc.
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 states it fetches 'currently active' assignments, implying it is not for historical data. While it does not explicitly name alternatives, the sibling tool list shows no overlapping assignment-related tool, so the usage context is clear without needing explicit exclusions.
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.