Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

build_base

Found a faction-owned station at your current point of interest in lawless space (Deploys a Station Core (assembled at a Station Core Foundry) to found a new faction station beside the POI you're loitering at. Requires: membership in a faction with the ManageBases permission, an undocked ship holding a Station Core, a lawless system (no controlling empire, zero police), a POI that doesn't already host a station, and the founding fee (faction treasury first, then your wallet). Stars and wormholes can't host stations. A system may only host one station at a time, regardless of owning faction — outposts remain unlimited per system. The station anchors at its own new station-type point of interest nearby and your ship is automatically docked there. Then use 'facility' faction_build to add Faction Storage, then power, life support, and services — each service/infrastructure facility draws maintenance from faction storage every cycle and goes offline when undersupplied. Use 'get_base_cost' to preview requirements and check your current spot.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the new faction station
session_idYesYour session ID from login/register
public_accessNoWhether any pilot may dock (default false — faction/allowed only)

Schema Changelog

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

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint=false annotation, the description adds rich behavioral details: the station anchors at a new POI, your ship is automatically docked, the fee is taken from faction treasury then your wallet, and infrastructure requires maintenance from faction storage. It also discloses system limits and the need to use 'facility' faction_build afterward.

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 dense paragraph, but every sentence contributes meaningful information about purpose, requirements, side effects, and follow-up. It is comprehensive without being overly verbose, though it could benefit from bullet points for readability.

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?

For a complex action with many prerequisites and side effects, the description covers all necessary context: requirements, system limits, station behavior, and next steps. It also references 'get_base_cost' for preview and mentions the maintenance mechanic. No output schema is needed for an action.

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

Parameters3/5

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

Schema coverage is 100%, so all three parameters already have descriptions in the input schema. The description doesn't add new parameter-specific details beyond the schema, but it does provide contextual meaning for the 'name' parameter as the station name and 'public_access' as docking control, which are already covered. A baseline of 3 is appropriate.

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 'Found a faction-owned station at your current point of interest in lawless space' with a specific verb and resource. It distinguishes from sibling tools like build_outpost by focusing on station construction and mentioning outposts separately.

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

Usage Guidelines4/5

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

The description lists explicit prerequisites (membership, ship holding Station Core, lawless system, POI without station, fee) and tells the user to use 'get_base_cost' to preview requirements. It also notes the one-station-per-system limit and that outposts are unlimited, implicitly guiding when to use this vs build_outpost, though it doesn't name the alternative directly.

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