Skip to main content
Glama

reload

Reload a weapon's magazine from ammo in cargo (Consumes 1 ammo item from cargo to fill the weapon's magazine. Send a weapons array instead of weapon_instance_id/ammo_item_id to load up to 50 weapons in one action for one tick: {"weapons": [{"weapon_instance_id": "abc123", "ammo_item_id": "standard_rounds_box"}, {"weapon_instance_id": "def456"}]}. Each entry succeeds or fails on its own and the response reports both. Each weapon type has a magazine size — autocannons hold hundreds of rounds, railguns hold a handful, torpedoes hold 2-3. Energy weapons (lasers, beams) don't need ammo. Works mid-battle and mid-flight (costs a game tick). Swapping to a different ammo type discards remaining rounds. Weapons auto-load when first installed if compatible ammo is in cargo. Weapons with the ammo_from_cargo special (e.g. the Scrapgun) accept any cargo item as ammo. Omit ammo_item_id to load a random low-value junk item automatically, or specify any ammo_item_id to shoot that exact item.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weaponsNoBulk reload: array of {weapon_instance_id, ammo_item_id?} entries loaded in a single action for one tick, however many weapons. Omit weapon_instance_id/ammo_item_id when using this. Entries are independent — the response reports per-weapon success/failure. Maximum 50 entries.
session_idYesYour session ID from login/register
ammo_item_idNoItem ID of ammo to load from cargo (must match the weapon's ammo type). For weapons with the ammo_from_cargo special: omit to auto-select random low-value junk, or specify any cargo item to load that exact item.
weapon_instance_idNoInstance ID of the fitted weapon to reload (use get_ship to see weapon instance IDs)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / oneOf
      Added value: +[
      +  {
      +    "required": [
      +      "weapon_instance_id"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "weapons"
      +    ]
      +  }
      +]
    • addedInput schema / properties / weapons
      Added value: +{
      +  "description": "Bulk reload: array of {weapon_instance_id, ammo_item_id?} entries loaded in a single action for one tick, however many weapons. Omit weapon_instance_id/ammo_item_id when using this. Entries are independent — the response reports per-weapon success/failure. Maximum 50 entries.",
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "session_id",
      -  "weapon_instance_id"
      -]New value: +[
      +  "session_id"
      +]
  2. Added
  3. Removed
  4. Changed2 schema fields changed
    • changedInput schema / properties / ammo_item_id / description
      Previous value: -"Item ID of ammo to load from cargo (must match the weapon's ammo type)"New value: +"Item ID of ammo to load from cargo (must match the weapon's ammo type). For weapons with the ammo_from_cargo special: omit to auto-select random low-value junk, or specify any cargo item to load that exact item."
    • changedInput schema / required
      Previous value: -[
      -  "session_id",
      -  "weapon_instance_id",
      -  "ammo_item_id"
      -]New value: +[
      +  "session_id",
      +  "weapon_instance_id"
      +]
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations (which only indicate readOnlyHint=false). It covers ammo consumption, per-entry independence, magazine size variation by weapon type, the discard of remaining rounds on ammo swap, auto-load behavior, the ammo_from_cargo special case, and the option to auto-select junk ammo. This is a comprehensive disclosure of the tool's effects and edge cases.

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 long but information-dense, with no redundant filler. It front-loads the core purpose and then systematically covers the bulk reload option, per-entry behavior, magazine sizes, energy weapon exemption, timing constraints, ammo swap consequences, auto-loading, and special ammo handling. Each sentence contributes unique value, though the length could be trimmed slightly without losing meaning.

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?

Given the tool's complexity (mutation, multiple parameters, special cases), the description covers nearly all necessary context: bulk vs single reload, per-entry outcomes, ammo types, energy weapons, timing, auto-load, and special ammo. It does not detail the response format beyond mentioning that it reports success/failure per entry, but since there is no output schema, a more explicit response description could have improved completeness. Overall, it is highly informative and sufficient for an agent to call the tool correctly.

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 descriptions already cover all four parameters (100% coverage), so the baseline is 3. The description adds valuable semantics beyond the schema: it explains the bulk reload array format with an example, clarifies that each entry succeeds/fails independently, and elaborates on the ammo_item_id omission behavior for ammo_from_cargo weapons. This extra context justifies a score above baseline.

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 clear verb and resource: 'Reload a weapon's magazine from ammo in cargo.' It explicitly covers bulk reload and per-entry success, distinguishing it from other weapon-related tools like refuel or repair. The purpose is unambiguous and not a tautology.

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 strong usage context: works mid-battle, costs a tick, and notes that energy weapons don't need ammo (a when-not). It also mentions auto-loading when first installed, implying that a manual reload may be unnecessary in that case. However, it does not explicitly name an alternative tool or provide a direct comparison, so it falls just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources