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, a galaxy-wide fuel-bunker summary (per-bunker status plus total reserve and capacity; at your faction's own station the row shows the shared station tank), and faction_rent: the faction's total rent per cycle, its daily equivalent, and arrears owed across every station; facilities at the faction's own station or outpost count at 0 rent (use facility action='faction_owned' for the per-facility breakdown). Use offset and limit to page through large member lists. members_offset, members_limit and members_truncated describe that page only; members_limit is the page size, not the faction member cap (a full faction rejects joins with a faction_full error that states the cap).)

Input 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.

AddedSep 10, 2026
RemovedSep 9, 2026

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.5/5.0

Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses substantial behavior: default and maximum page sizes, truncation semantics, what the member-list fields mean, how rent is reported, and that full factions reject joins with a faction_full error. This is unusually rich behavioral context for an agent.

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 purpose is front-loaded, but the description is a very long parenthetical run-on that packs many return-value and pagination details into one dense block. Most content is useful for a no-output-schema tool, but the structure makes it harder to scan than it should be.

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?

With no output schema and a complex payload, the description compensates by explaining the major return categories: member list pagination, roles, treasury, wars, peace proposals, fuel-bunker summary, and faction rent. It is complete enough for an agent to understand both the call and the expected result shape.

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 already documents all four parameters at 100% coverage, establishing a baseline of 3. The description adds useful semantics beyond the schema, especially that faction_id omission returns your own faction and that members_limit is page size rather than the faction member cap.

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 states a specific verb and resource: viewing faction details, with the default scope clearly defined when faction_id is omitted. It also distinguishes the detailed view from related actions by describing the included member list, roles, treasury, wars, and rent data.

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 clear usage context: omit faction_id for your own faction, use offset and limit for member-list paging, and use facility action='faction_owned' for per-facility rent breakdowns. It does not explicitly compare against faction_list or state when this tool should not be used, preventing a 5.

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?