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. Five boolean toggles control what your alliance implies: 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); ally_battle_opt_out=true keeps your members from auto-joining battles on an ally's behalf, though they can still join with battle action=engage (default false → members auto-join to help allies). ally_shipyard_access=true lets allied members commission ships at your faction's station shipyards under your ship licenses, supplying materials from their own faction storage there and paying labor and royalty from their own treasury; mobile bases stay members-only (default false → only your members build here). All fields optional. Requires leader or manage_roles permission. Requires Faction Admin Office at current station.)

Input 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_battle_opt_out`	No	True to keep your members out of battles they would auto-join on an ally's behalf. They can still join with battle action=engage (default false → members auto-join to help allies).
`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).
`ally_shipyard_access`	No	True to let allied faction members commission ships at your faction's station shipyards under your ship licenses. They supply the build materials from their own faction storage at the station and pay labor and royalty from their own treasury. Mobile bases stay members-only (default false → only your members build here).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

addedInput schema / properties / ally_shipyard_access

Added value: +{
+  "description": "True to let allied faction members commission ships at your faction's station shipyards under your ship licenses. They supply the build materials from their own faction storage at the station and pay labor and royalty from their own treasury. Mobile bases stay members-only (default false → only your members build here).",
+  "type": "boolean"
+}

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / ally_battle_opt_out

Added value: +{
+  "description": "True to keep your members out of battles they would auto-join on an ally's behalf. They can still join with battle action=engage (default false → members auto-join to help allies).",
+  "type": "boolean"
+}

AddedSep 10, 2026
RemovedSep 9, 2026

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

B3.4/5.0

Behavior1/5

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

Annotations declare readOnlyHint=true and idempotentHint=true, yet the description describes a mutation that rewrites faction identity and access policy. Beyond that contradiction it also fails to say whether omitted fields are preserved or reset, which matters greatly for toggles whose defaults are semantically loaded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is properly front-loaded and the parenthetical grouping is logical, but the body is long and restates per-toggle text already present in the schema. Tightening to the lead sentence plus permissions and default-preservation behavior would lose no information.

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?

For a 10-parameter mutation the description covers permissions, station requirement, optionality, and the meaning of every toggle, which is close to complete. The gaps are behavioral rather than semantic: no statement about partial-update merging or what the call returns, and the safety profile conflicts with the annotations.

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% and the schema descriptions for the five boolean toggles already spell out defaults and consequences in nearly the same words used here, so the prose largely duplicates structured data. The only additive framing is 'All fields optional' and the char-limit rationale, which justifies the baseline 3 rather than higher.

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 opening sentence names a specific verb and enumerates the exact mutable fields (description, charter, colors, ally-sharing toggles), which cleanly separates it from siblings like faction_edit_role or set_colors. An agent can tell what this tool writes without opening the schema.

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?

It gives concrete preconditions: leader or `manage_roles` permission and a Faction Admin Office at the current station, plus 'All fields optional' implying partial updates. It stops short of naming alternatives for pure color changes (set_colors) or role management (faction_edit_role), so routing is implied rather than explicit.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?