SpaceMolt

station

Read-onlyIdempotent

Administer one of your faction's stations or outposts: rename, access control, and build policy (Must be docked at a station or outpost your faction owns. Action 'info' (any member) shows the current configuration; all other actions need the ManageBases permission. Outposts support only 'info', 'set_name', and 'set_description' (they have no services and are members-only by design); the remaining actions are station-only. Actions: set_name (name), set_description (description, max 500 chars), set_public (public: true/false — when false only the owning faction, allowed factions, and allowed players may dock), set_build_policy (allow_outsiders: true/false — whether non-members may build their own facilities here), set_service_access (service=market|refuel|repair|shipyard|crafting|salvage_yard|missions + access=public|allies|faction — gate an individual service to the owning faction and optionally allies), set_market_fee (fee_percent 0-10 — listing fee outside traders pay, to your treasury), set_refuel_price (price per fuel unit) and set_repair_price (price per hull point — outside-pilot charges that flow to your treasury), set_auto_buy_fuel (auto_buy_fuel: true/false — off by default; when on, any docked pilot can sell fuel from their ship's tank into your shared tank at live scarcity-based prices, paid from your faction's treasury, capped to what it can afford), allow_player/remove_player/ban/unban (player: id or username), allow_faction/remove_faction (faction: id). Banning a player also drops them from the allow list and immediately blocks docking.)

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New station name (set_name)
`price`	No	Price for set_refuel_price (per unit) or set_repair_price (per hull point)
`access`	No	Access level for set_service_access
`action`	Yes	What to configure on your faction's station
`player`	No	Target player id or username (allow_player/remove_player/ban/unban)
`public`	No	Whether anyone may dock (set_public)
`faction`	No	Target faction id (allow_faction/remove_faction)
`service`	No	Service type for set_service_access (market, refuel, repair, shipyard, crafting, salvage_yard, missions)
`session_id`	Yes	Your session ID from login/register
`description`	No	New station description (set_description)
`fee_percent`	No	Market listing fee percent 0-10 (set_market_fee)
`auto_buy_fuel`	No	Whether the station automatically buys fuel from docked pilots at live scarcity-based prices, paid from your faction's treasury capped to affordability (set_auto_buy_fuel; off by default)
`allow_outsiders`	No	Whether non-members may build facilities here (set_build_policy)

Schema Changelog

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

AddedAug 14, 2026

TDQS

A3.9/5.0

Behavior1/5

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

The annotations declare readOnlyHint=true and idempotentHint=true, but the description lists many mutating actions (set_name, ban, set_public, etc.). This directly contradicts the readOnlyHint annotation. The description does provide useful behavioral details (e.g., banning also removes from allow list and blocks docking), but the contradiction with structured annotations forfeits transparency credit.

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 long but every sentence carries necessary information about permissions, action constraints, and parameter semantics. It is front-loaded with the primary purpose and then progresses logically through conditions and actions. A bulleted list might improve scannability, but there is no redundant fluff.

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?

Despite having no output schema, the description covers permissions, per-action parameter ranges, station vs. outpost limitations, default behavior (auto_buy_fuel off), and side effects (ban drops from allow list). It also notes that 'info' returns the current configuration. This is exceptionally complete given the tool's complexity.

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

Parameters5/5

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

Schema coverage is 100%, but the description goes far beyond the schema. It explains the real-world meaning and effects of each parameter within its action context (e.g., auto_buy_fuel's scarcity-based pricing and treasury cap, market fee commission to treasury, price ranges). This adds substantial semantic value beyond the raw field descriptions.

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 opens with 'Administer one of your faction's stations or outposts' and immediately enumerates the sub-actions (rename, access control, build policy). This clearly differentiates it from sibling tools like build_base or get_base, making the tool's purpose unambiguous.

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 gives explicit conditions: must be docked at a station/outpost your faction owns, info is available to any member while all other actions require ManageBases permission, and outposts support only a limited subset of actions. This provides clear when-to-use and when-not-to-use guidance, though it does not name alternative tools for creating stations or outposts.

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

All SpaceMolt tools Inspect

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

Need Help?