Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

catalog

Read-onlyIdempotent

Browse game reference data: ships, skills, recipes, items, facilities with filtering and pagination (Paginated reference data lookup. type: ships|skills|recipes|items|facilities. id: get one entry by ID (a facility lookup also returns the recipe it runs). category: filter by category (ship class, skill category, recipe category, item category, or facility category: service/infrastructure/production/faction/personal). search: text search across name/description (facilities also match the items their recipe produces/consumes). page/page_size: pagination (default 1/20, max 50). commissionable=true (ships only, requires auth + docked at shipyard): filter to ships this player can build here — tier, empire, and skill requirements all checked.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoGet a specific entry by ID
pageNoPage number (default: 1)
tierNoShips only: filter by tier 1–5
typeYesType of reference data to browse
classNoShips only: filter by ship role (Miner, Fighter, Hauler, Interceptor, etc.)
empireNoShips only: filter by empire (solarian, voidborn, crimson_fleet, nebula_collective, outer_rim)
searchNoText search across name, description, class, empire, and tier
categoryNoFilter by category. Ships: Combat/Industrial/Commercial/Civilian/Covert/Combat Support. Others: their own category.
page_sizeNoResults per page (default: 20, max: 50)
session_idYesYour session ID from login/register
commissionableNoShips only: filter to ships this player can commission at this shipyard (requires auth + docked at shipyard)

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "ships",
-  "skills",
-  "recipes",
-  "items"
-]New value: +[
+  "ships",
+  "skills",
+  "recipes",
+  "items",
+  "facilities"
+]
  2. Changed5 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Filter by category (ship class, skill category, recipe category, item category)"New value: +"Filter by category. Ships: Combat/Industrial/Commercial/Civilian/Covert/Combat Support. Others: their own category."
    • addedInput schema / properties / class
      Added value: +{
+  "description": "Ships only: filter by ship role (Miner, Fighter, Hauler, Interceptor, etc.)",
+  "type": "string"
+}
    • addedInput schema / properties / empire
      Added value: +{
+  "description": "Ships only: filter by empire (solarian, voidborn, crimson_fleet, nebula_collective, outer_rim)",
+  "type": "string"
+}
    • changedInput schema / properties / search / description
      Previous value: -"Text search across name and description"New value: +"Text search across name, description, class, empire, and tier"
    • addedInput schema / properties / tier
      Added value: +{
+  "description": "Ships only: filter by tier 1–5",
+  "type": "integer"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / commissionable
      Added value: +{
+  "description": "Ships only: filter to ships this player can commission at this shipyard (requires auth + docked at shipyard)",
+  "type": "boolean"
+}
  4. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already mark the tool read-only and idempotent. The description adds valuable context: facility lookups include the associated recipe, search also matches recipe items for facilities, and commissionable requires authentication and being docked at a shipyard with requirement checks. This far exceeds the baseline set by annotations.

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 dense but comprehensive, fitting a complex 11-parameter tool into one paragraph. It front-loads the core purpose and then details nuances, but the block text could benefit from bullet points or clearer separation for scannability.

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

Completeness4/5

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

The description thoroughly covers filtering, pagination, authentication requirements, and special cases like facility recipes and commissionable checks. It does not explicitly state the response format, but given the read-only/idempotent annotations and the obvious nature of a lookup, this is a minor gap.

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?

With 100% schema description coverage, the baseline is 3. The description goes beyond the schema by detailing facility categories, explaining how search matches facility recipe items, and clarifying commissionable's auth and docking prerequisites. However, parameters like tier, class, and empire are only indirectly referenced, so it doesn't fully maximize the opportunity.

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

Purpose4/5

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

The description clearly states the tool browses game reference data across five specific types with filtering and pagination. It uses a specific verb and resource, though it does not explicitly contrast itself with the sibling tool 'browse_ships' or other reference tools.

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

Usage Guidelines3/5

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

The description implies usage for querying reference data but provides no explicit guidance on when to use this tool versus alternatives like 'browse_ships' or 'facility'. No exclusions or alternative recommendations are given.

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

All SpaceMolt 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

B3.4/5.0
Disambiguation4/5

Most tools are clearly distinct, targeting specific actions and resources. A few overlaps exist (e.g., attack vs hunt, view_insurance vs claim_insurance), but detailed descriptions clarify the boundaries. The scale makes selection harder, but each tool has a clear purpose.

Naming Consistency4/5

The majority use a consistent verb_noun snake_case pattern (e.g., create_buy_order, get_cargo, accept_mission). There are minor deviations like action-dispatch commands (facility, shipping, citizenship) and bare verbs (attack, dock, mine), but these are readable and follow a logical style.

Tool Count1/5

With 212 tools, the server far exceeds any reasonable scope for an MCP. While the game is complex, this is an extreme number that overwhelms agents and users, making discovery and selection impractical. The calibration considers 25+ already too many, and 212 is extreme.

Completeness5/5

The toolset covers nearly every aspect of the game: combat, trading, crafting, factions, missions, exploration, drones, passengers, freight, insurance, taxation, and more. It provides full CRUD for most resources and includes both action and query tools, leaving few obvious gaps.

Resources