Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

view_faction_storage

Read-onlyIdempotent

View your faction's shared storage at a station (Shows the faction's global treasury balance, items at the station, and recent activity. Must be in a faction. Provide station_id as either the station's Base ID or station POI ID to view without being docked; omit to use your current docked station (must have storage service).)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYesYour session ID from login/register
station_idNoOptional: station Base ID or station POI ID to view your faction's storage at without being docked. If omitted, must be docked and uses the current station.

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / station_id / description
      Previous value: -"Optional: station ID to view your faction's storage at without being docked. If omitted, must be docked and uses the current station."New value: +"Optional: station Base ID or station POI ID to view your faction's storage at without being docked. If omitted, must be docked and uses the current station."
  2. Changed1 schema field changed
    • addedInput schema / properties / station_id
      Added value: +{
+  "description": "Optional: station ID to view your faction's storage at without being docked. If omitted, must be docked and uses the current station.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only and idempotent behavior, and the description adds context about data scope and the docking requirement. It explains the difference in behavior when station_id is supplied versus omitted. This goes beyond what annotations state, though it does not detail response format or any auth nuance beyond faction membership.

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, information-dense sentence that front-loads the core purpose and then supplies necessary usage details. It is not bloated, though the parenthetical structure makes it slightly dense.

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?

Given the annotations, full schema coverage, and the description's explicit statements about prerequisites, data returned, and station resolution behavior, the definition is complete enough for an agent to know when and how to invoke this tool.

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 important semantics by specifying that station_id can be either a Base ID or POI ID, and that omission means 'current docked station.' This adds value beyond the schema's brief parameter descriptions.

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: 'View your faction's shared storage at a station.' It also enumerates what is shown (global treasury balance, items, recent activity), which clearly distinguishes it from sibling tools like view_storage (personal storage) and faction_info.

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 explicit usage context: must be in a faction, station_id can be provided to view without docking, and omitting it uses the currently docked station when storage service is available. It does not explicitly name alternatives such as view_storage, so it falls just short of full routing guidance.

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