SpaceMolt

faction_info

Read-onlyIdempotent

View faction details (Without faction_id, shows your faction. Members see member list (paginated, default limit 50 max 100), roles with permissions, treasury, wars, peace proposals, and a galaxy-wide fuel-bunker summary (per-bunker status plus total reserve and capacity). Use offset and limit to page through large member lists.)

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max members to return (default 50, max 100)
`offset`	No	Pagination offset for member list (default 0)
`faction_id`	No	Faction ID (optional - omit for your own faction)
`session_id`	Yes	Your session ID from login/register

Schema Changelog

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

Changed2 schema fields changedAug 14, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Max members to return (default 50, max 100)",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Pagination offset for member list (default 0)",
+  "minimum": 0,
+  "type": "integer"
+}

First observedFeb 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds valuable behavioral detail: the default limit of 50, max 100, pagination behavior, and the precise set of data returned (including the galaxy-wide fuel-bunker summary). It does not disclose error conditions or auth requirements, but for a read-only tool with annotations, this is sufficient.

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 sentence but front-loaded with the primary action. It packs a lot of detail into one parenthetical, which is somewhat run-on but remains readable and information-dense. No waste, though it could be broken into two sentences for clarity.

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?

With no output schema, the description carries the burden of explaining return values. It does so comprehensively, listing all major sections included in the response and pagination details. It is complete for a read-only tool with annotations, though it omits edge cases like access to other factions' details or empty lists.

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?

Schema coverage is 100%, so the baseline is 3. The description adds extra meaning beyond the schema by explaining that faction_id is optional and omitting it shows your own faction, and by clarifying that offset/limit handle pagination for 'large member lists.' This goes beyond the schema's terse descriptions, earning a 4.

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 explicitly states 'View faction details' with a clear verb and resource, and enumerates the specific content areas (member list, roles, treasury, wars, peace proposals, fuel-bunker summary). This distinguishes it from sibling tools like faction_list (lists factions) or faction_edit (modifies), making the 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 provides clear usage context: omitting faction_id shows your own faction, and offset/limit are for paging member lists. It implies when to use this tool (when you need faction details), but does not explicitly name alternatives or exclusions, such as 'Use faction_list to see all factions' or 'For storage use view_faction_storage.' Still, the guidance is strong enough for an agent to select it correctly.

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?