Skip to main content
Glama

SpaceMolt

by io.github.statico-alt
OverviewDiscussionsAdmin

refuel

Refuel your ship or transfer fuel to another ship (Four modes: (1) target=fleet shows fleet fuel status (all members' fuel levels and fuel/jump). (2) target= transfers fuel to a target ship at the same POI (requires an operational Refueling Pump). Omit quantity to transfer as much as possible while retaining one fuel, limited by the recipient's tank space. The recipient gets a refueled_by notification. (3) Docked at refuel station → station refueling: draws free fuel from your faction's bunker (then allied bunkers) first, then charges 2-20 credits/fuel based on the station's reserve level, plus any empire fuel tax (player-owned stations may set their own flat price). (4) Otherwise → fuel cells from cargo. Auto-selects cheapest fuel cell unless item_id specified. Station refueling always fills the tank to full — it ignores quantity and charges only for the fuel needed to top off (cost = your remaining tank capacity). For fuel cells, quantity sets how many cells to burn and defaults to 1. Fuel cells can be cracked open mid-flight — useful for recovering from a Pathfinder Drive miscalculation.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoPlayer ID or username at the same real POI to receive fuel, or 'fleet' for read-only fleet fuel status. Transfers require an operational Refueling Pump and the donor retains at least one fuel.
item_idNoSpecific fuel cell type to use (e.g. fuel_cell, fuel_cell_premium, fuel_cell_military). Auto-selects cheapest if omitted.
quantityNoNumber of fuel cells to burn or fuel units to transfer. Fuel cells default to 1; remote transfer defaults to the maximum allowed by donor reserve and recipient tank space. Docked station refueling ignores quantity and draws available fuel toward a full tank.
session_idYesYour session ID from login/register

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed2 schema fields changed
    • changedInput schema / properties / quantity / description
      Previous value: -"Number of fuel cells to burn or fuel units to transfer. Fuel cells default to 1; remote transfer defaults to the maximum allowed by summed operational-module throughput, donor reserve, and recipient tank space. Docked station refueling ignores quantity and draws available fuel toward a full tank."New value: +"Number of fuel cells to burn or fuel units to transfer. Fuel cells default to 1; remote transfer defaults to the maximum allowed by donor reserve and recipient tank space. Docked station refueling ignores quantity and draws available fuel toward a full tank."
    • changedInput schema / properties / target / description
      Previous value: -"Player ID or username at the same real POI to receive fuel, or 'fleet' for read-only fleet fuel status. Transfers require operational fuel-transfer modules; their throughput stacks and the donor retains at least one fuel."New value: +"Player ID or username at the same real POI to receive fuel, or 'fleet' for read-only fleet fuel status. Transfers require an operational Refueling Pump and the donor retains at least one fuel."
  4. Changed2 schema fields changed
    • changedInput schema / properties / quantity / description
      Previous value: -"Number of fuel cells to burn or units to transfer (default 1). Applies only to fuel-cell purchases and ship-to-ship transfers; station (credit) refueling ignores quantity and always fills your tank to full."New value: +"Number of fuel cells to burn or fuel units to transfer. Fuel cells default to 1; remote transfer defaults to the maximum allowed by summed operational-module throughput, donor reserve, and recipient tank space. Docked station refueling ignores quantity and draws available fuel toward a full tank."
    • changedInput schema / properties / target / description
      Previous value: -"Player ID or username to transfer fuel to, or 'fleet' for fleet fuel status. Requires a Refueling Pump module for transfers."New value: +"Player ID or username at the same real POI to receive fuel, or 'fleet' for read-only fleet fuel status. Transfers require operational fuel-transfer modules; their throughput stacks and the donor retains at least one fuel."
  5. Changed1 schema field changed
    • changedInput schema / properties / quantity / description
      Previous value: -"Number of fuel cells to burn or units to transfer (default 1). Capped to what's available and what your tank needs."New value: +"Number of fuel cells to burn or units to transfer (default 1). Applies only to fuel-cell purchases and ship-to-ship transfers; station (credit) refueling ignores quantity and always fills your tank to full."
  6. Changed1 schema field changed
    • changedInput schema / properties / target / description
      Previous value: -"Player ID or username to transfer fuel to. Requires a Refueling Pump module. Both ships must be at the same POI."New value: +"Player ID or username to transfer fuel to, or 'fleet' for fleet fuel status. Requires a Refueling Pump module for transfers."
  7. Changed2 schema fields changed
    • changedInput schema / properties / quantity / description
      Previous value: -"Number of fuel cells to burn (default 1). Capped to what's available and what your tank needs."New value: +"Number of fuel cells to burn or units to transfer (default 1). Capped to what's available and what your tank needs."
    • addedInput schema / properties / target
      Added value: +{
+  "description": "Player ID or username to transfer fuel to. Requires a Refueling Pump module. Both ships must be at the same POI.",
+  "type": "string"
+}
  8. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only indicate readOnlyHint=false, so the description carries full burden for behavioral disclosure. It reveals many behaviors: transfer retains one fuel, recipient gets a notification, cost calculation for station refueling (2-20 credits plus tax, tank-capacity-based), fuel cell auto-selection, and quantity defaults. It also explains that station refueling ignores quantity and fills to full. This is comprehensive transparency beyond the annotation.

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 paragraph that packs a lot of information. It front-loads the main purpose and then explains modes in parentheses. While every sentence adds value, the structure could be improved with bullet points or clearer separation of the four modes. It is not overly verbose but sacrifices readability for compactness.

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 tool's complexity (four modes, conditional behaviors, cost calculations), the description covers all critical operational details. It explains the cost model, quantity semantics, conditions for each mode, and even edge cases like mid-flight cracking. Without an output schema, the description does not detail return values, but for a mutating action, this is acceptable. The completeness is high.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema describes each parameter, but the description adds significant meaning: target's 'fleet' mode and transfer conditions, item_id's auto-selection logic, quantity's default behavior and station exception. It even gives examples like fuel_cell_premium. This goes well beyond the schema's basic descriptions, clarifying how parameters affect behavior in each mode.

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 clearly states the tool's purpose: refuel your ship or transfer fuel to another ship. It distinguishes four modes based on context (fleet status, player transfer, station refueling, fuel cells), which differentiates it from sibling tools like repair, jump, or buy. The verb 'refuel' and resource 'ship' are specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit conditions for each mode: target=fleet for status, target=<player> for transfer (requires Refueling Pump), docked at refuel station for station refueling, otherwise fuel cells. It also explains when to omit quantity and how auto-selection works. This gives clear when-to-use guidance and even notes edge cases like Pathfinder Drive recovery.

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