Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

build_outpost

Deploy a lightweight, members-only faction outpost at your current point of interest in lawless space (Deploys an Outpost Kit (assembled at an Outpost Frame Assembler) to plant a faction outpost beside the POI you're loitering at — far cheaper than a station. Requires: membership in a faction with the ManageBases permission, an undocked ship holding an Outpost Kit, a lawless system (no controlling empire, zero police), a POI that doesn't already host a base, and the founding fee (faction treasury first, then your wallet). Stars and wormholes can't host outposts. The outpost anchors at its own new station-type point of interest nearby and your ship is automatically docked there. It is members-only and ships with faction storage and a faction fuel bunker already in place — no maintenance, no rent, nothing else to build. Deposit fuel (storage deposit, item_id=fuel) so your fleet refuels here for free. For a full station with services, use 'build_base' instead.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the new faction outpost
session_idYesYour session ID from login/register

Schema Changelog

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

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, leaving the description to disclose critical behaviors. It enriches this with placement rules, docking effects, member-only access, built‑in storage/fuel bunker, no maintenance, and exclusions (stars/wormholes). This goes well beyond annotation coverage.

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 lengthy but every sentence provides essential detail—requirements, exceptions, outcome, and alternatives. It is front-loaded with the core action and remains structured, though slightly verbose.

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?

Given the tool's complexity and the absence of an output schema, the description thoroughly explains prerequisites, placement, resulting state, and features. It does not describe failure modes or explicit return values, but for a game action tool the outcome is sufficiently clear.

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% with both parameters already described (name, session_id). The description adds no extra meaning about these parameters, so the 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 uses a specific verb ('Deploy') and resource ('lightweight, members-only faction outpost'), and clearly distinguishes from build_base by stating 'For a full station with services, use build_base instead.'

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

Usage Guidelines5/5

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

The tool explicitly lists detailed prerequisites (membership, permission, undocked ship, lawless system, POI without base, fee) and explicitly names an alternative ('build_base') when a full station is desired, making usage conditions clear.

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