Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

install_mod

Install a module on your ship (Module must be in your cargo. Requires CPU/power grid capacity. You must be docked or have a Ship Maintenance Bay fitted. CPU and power usage shown reflect your Engineering skill bonus (1% reduction per level).)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
module_idYesModule ID to install/uninstall. CPU and power usage shown reflect your Engineering skill bonus (1% reduction per level).
session_idYesYour session ID from login/register

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / module_id / description
      Previous value: -"Module ID to install/uninstall"New value: +"Module ID to install/uninstall. CPU and power usage shown reflect your Engineering skill bonus (1% reduction per level)."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations only indicate readOnlyHint=false, so the description carries the burden of behavioral context. It usefully discloses prerequisites and the Engineering skill bonus effect on CPU/power usage, but it does not describe what happens after installation, whether the module is consumed, or failure behavior. Moderate transparency.

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

Conciseness5/5

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

The description is a single dense sentence that front-loads the core action and packs the key prerequisites into a parenthetical. There is no redundancy or filler; every clause earns its place.

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 simple two-parameter install operation with no output schema, the description covers the essential operational preconditions and the skill-based stat adjustment. It does not specify return values or detailed failure messages, but an agent has enough context to decide when and how to invoke the tool.

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 description coverage is 100%, so the schema already documents both parameters. The description repeats the skill-bonus context already present in the module_id schema and adds no new parameter-level meaning beyond that, matching the baseline for full coverage.

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 and resource, 'Install a module on your ship,' making the tool's purpose immediately clear. The sibling uninstall_mod provides natural contrast, and no other sibling overlaps with this install-only operation.

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 explicit go/no-go conditions: module must be in cargo, CPU/power grid capacity is required, and the ship must be docked or have a Ship Maintenance Bay fitted. It does not name alternatives or explicitly say when not to use it, but the prerequisites strongly inform usage.

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