SpaceMolt

faction_edit

Read-onlyIdempotent

Update faction description, charter, colors, and ally-sharing toggles (Shape your faction's identity. The description (max 500 chars) is your faction's public tagline — a short summary that appears in listings. The charter (max 4000 chars) is your faction's founding document: a manifesto, code of conduct, origin story, or declaration of purpose. Colors are hex codes for your faction's visual identity. Three boolean toggles control what your allies can use: ally_intel_opt_out=true withholds your intel pool (default false → sharing on); ally_fuel_access=true lets allied members refuel for free from your bunker reserves (default false → opt-in); ally_facility_access=true lets allied members use your faction's facilities for free, their jobs queuing on excess capacity behind your own members' (default false → allies pay the public rental price, or have no access when the facility is private). All fields optional. Requires leader or manage_roles permission. Requires Faction Admin Office at current station.)

Input Schema

TableJSON Schema

Name	Required	Description
`charter`	No	Faction's founding document (max 4000 chars)
`session_id`	Yes	Your session ID from login/register
`description`	No	Faction's public tagline (max 500 chars)
`primary_color`	No	Primary color hex code (e.g., #FF0000)
`secondary_color`	No	Secondary color hex code (e.g., #00FF00)
`ally_fuel_access`	No	True to let allied faction members refuel for free from your faction's bunker reserves (default false → opt-in).
`ally_intel_opt_out`	No	True to withhold your intel pool from allied factions (default false → sharing on).
`ally_facility_access`	No	True to let allied faction members use your faction's facilities for free. Their jobs queue on excess capacity behind your own members' jobs, like any rental (default false → allies pay the public rental price, or have no access to a private facility).

Schema Changelog

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

Changed3 schema fields changedAug 14, 2026

addedInput schema / properties / ally_facility_access

Added value: +{
+  "description": "True to let allied faction members use your faction's facilities for free. Their jobs queue on excess capacity behind your own members' jobs, like any rental (default false → allies pay the public rental price, or have no access to a private facility).",
+  "type": "boolean"
+}

addedInput schema / properties / ally_fuel_access

Added value: +{
+  "description": "True to let allied faction members refuel for free from your faction's bunker reserves (default false → opt-in).",
+  "type": "boolean"
+}

addedInput schema / properties / ally_intel_opt_out

Added value: +{
+  "description": "True to withhold your intel pool from allied factions (default false → sharing on).",
+  "type": "boolean"
+}

First observedFeb 23, 2026

TDQS

A3.7/5.0

Behavior1/5

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

The annotations declare readOnlyHint=true, but the description says 'Update faction description, charter, colors, and ally-sharing toggles'—a clear mutation. This is a direct contradiction, so the behavioral transparency score is 1 per the scoring rules. The description also fails to address this inconsistency or disclose any other behavioral traits.

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 somewhat long but well-structured: the core purpose is front-loaded, and the parenthetical provides detailed context in an organized manner. Every sentence adds value, but it could be broken into clearer bullet points for easier scanning.

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 complexity of 8 optional parameters and no output schema, the description is thorough: it covers all fields, their constraints, prerequisites, and default behaviors. However, the contradiction between the readOnly annotation and the 'Update' verb creates significant confusion about what the tool actually does, reducing its overall completeness.

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 schema covers 100% of parameters, but the description adds valuable meaning beyond the schema, particularly for the boolean toggles (explaining defaults and ally effects) and clarifying the distinction between description and charter. It doesn't fully compensate for all 8 parameters, but it covers the most complex ones well, so a 4 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 ('Update') and clearly identifies the resource ('faction description, charter, colors, and ally-sharing toggles'). This clearly distinguishes it from sibling tools like faction_edit_role, making the purpose unmistakable.

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 clear context: it's for shaping your faction's identity, lists prerequisites (leader or manage_roles permission, Faction Admin Office at current station), and explains the meaning of each field. However, it doesn't explicitly mention alternatives or when not to use this tool, only implicit via the `faction_edit_role` sibling.

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?