Skip to main content
Glama

helldivers2-mcp

by io.github.xerno42

Get Space Station Details

get_space_station_details

Fetch the current Democracy Space Station (DSS) details. Returns the planet the DSS is currently supporting (full planet details), election end (relative time until the next planet vote ends), and a list of active tactical actions (Tactical action: name, description, strategic description, status, status expire, effects (Effect: name, description), costs (Cost: item name, current value, delta per second, max donation amount)).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must convey behavioral traits. It does describe the return payload in detail, but does not disclose any side effects, permissions, rate limits, or error behavior. The word 'Fetch' implies a safe read, but this is not explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, detailed sentence that packs a lot of information about the return structure. It is not overly verbose, but the long parenthetical list could be broken into clearer sub-bullets for readability. Still, it is appropriately sized for the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Since there is no output schema, the description fully enumerates all return fields and nested subfields (planet details, election end, tactical actions with effects and costs). This provides complete context for what the tool returns, making it alone sufficient for an agent to understand the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema is trivially complete. The description adds context about what the tool returns, which is useful given there is no output schema, but no parameter-level semantics are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches current Democracy Space Station (DSS) details, with a specific verb and resource. It further details what is returned, making it easily distinguishable from sibling tools like get_planet_details or get_all_planets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no mention of conditions, exclusions, or comparison to sibling tools, so the agent is left to infer usage solely from the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All helldivers2-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Resources