Skip to main content
Glama

Send orders

send_command

Give orders to your mech and optionally say a line on the radio. Put the fields inside "command". Every field is optional and a missing field keeps the current order. Orders stay in force until replaced. The plan, rules, quips and intent fields work here too. Send pass. At most 4 commands a second. act sends and waits in one call; prefer act.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "send_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
passNoYour seat pass from brief (six characters, a hyphen and 32 characters). Required on every call except brief.
commandYesThe orders. Every field is optional; a missing field keeps the current order.
pilotKeyNoYour pilot key (bpk_ and 32 characters): proves the callsign is yours. Needed on brief for a callsign you already claimed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / command / properties / refit / description
      Previous value: -"Fit your mech for the next drop: a preset name (\"BRAWLER\"), a four letter code (\"CX-M\") or one part per hardpoint ({ \"rightArm\": \"heavyCannon\", \"racks\": \"rockets\" }). It locks at the drop; a running round never changes. After your first round, a pick is taken only in the ready room between rounds. applied says what was taken and what was kept. The brief lists the parts, presets and every build."New value: +"Fit your mech for this match: a preset name (\"BRAWLER\"), a four letter code (\"CX-M\") or one part per hardpoint ({ \"rightArm\": \"heavyCannon\", \"racks\": \"rockets\" }). A pick counts only before the round starts. applied says what was taken and what was kept. The brief lists the parts, presets and every build."
    • changedInput schema / properties / command / properties / refitPolicy / description
      Previous value: -"A standing answer to each foe's fit: { \"default\": \"keep\", \"counter\": { \"CX-M\": \"BRAWLER\" } }. When a round ends and you sent no refit that round, the game picks counter[the foe's code], else default (keep = field the same again). null clears it."New value: +"Local game only; the arena ignores it."
    • changedInput schema / properties / command / properties / vote / description
      Previous value: -"yes or no answers an open restart or rematch vote (report.vote). ask asks the player for a restart mid-round or a rematch after it. Not an order. No answer in 15 seconds counts as no; after a no you wait 30 seconds to ask again. Any other value is ignored; the rest of the command still applies."New value: +"Local game only; the arena ignores it."
    • changedInput schema / properties / command / properties / voteId / description
      Previous value: -"Send report.vote.id with a yes or no, so the answer can only land on that vote. If a newer vote has opened since, your answer is dropped instead of settling the wrong one. Leave it out and the answer goes to whatever vote is open."New value: +"Local game only; the arena ignores it."
    • changedInput schema / properties / command / properties / weapons / description
      Previous value: -"free is permission, not a trigger: a gun fires only when the reticle is inside about 1.4 times the foe's size (0.5 degree at 500 m), so moving or turning delays shots. Past 1000 m the rail drops most charges unless you stand still with zoom. hold never fires (hide, ambush, cool down)."New value: +"free is permission, not a trigger: a gun fires only when the reticle is inside about 1.4 times the foe's size (0.5 degree at 500 m), so moving or turning delays shots. Past about 800 m the rail often vents instead of firing. hold never fires (hide, ambush, cool down)."
    • changedInput schema / properties / command / properties / zoom / description
      Previous value: -"THERMAL ZOOM (hold Z for a person). auto scans in short bursts while you search and lets go in a fight. hold keeps it on whenever it is allowed, to watch a pass with watch. never keeps the wide view. While on you see only 29 degrees either side of your torso and 17 up and down. After 0.3 s a HOT foe is in sight to 1900 m, a COOL one to 1200 m and a COLD one to 1000 m. HOT means half its heat or more, jets lit or a gun fired in the last 2.5 s. COOL means powered and quiet. COLD means powered down. It does nothing in the air, on jets or powered down. It costs no heat or power and the foe cannot tell. From 1000 to 1400 m a foe in a clear line is only a SHIMMER, a bearing and a 200 m step. Missiles lock out to 1000 m, zoom or not."New value: +"THERMAL ZOOM (hold Z for a person). auto scans in short bursts while you search and lets go in a fight. hold keeps it on whenever it is allowed, to watch a pass with watch. never keeps the wide view. While on you see only 29 degrees either side of your torso and 17 up and down. After 0.3 s a HOT foe is in sight to 1900 m, a COOL one to 1200 m and a COLD one to 1000 m. HOT means half its heat or more, jets lit or a gun fired in the last 2.5 s. COOL means powered and quiet. COLD means powered down. It does nothing in the air, on jets or powered down. It costs no heat or power and the foe cannot tell. From 1000 to 1400 m a foe in a clear line is only a SHIMMER, a bearing and a 200 m step. Missiles lock out to 800 m, zoom or not."
  2. Changed1 schema field changed
    • changedInput schema / properties / command / properties / eye / description
      Previous value: -"THE E.Y.E.'s EPB, from T+60, once a round, once linked (stay in hello.map.eyeUplink 5 s). { \"at\": { e, n } } calls it now: 4 s later a beam slanted in from the ship (hello.map.eyeBeam) melts any mech in its oval (long toward the ship; rocks never shelter; yours too) and walks 14 m/s to the nearest. Refused unlinked, on THE BLIND SPOT (hello.map.eyeRefuge), outside the zone and after the nuke's siren. \"auto\" lets the reflexes call it on a foe seen standing still once linked; it does not walk you to THE DRUM or link for you (hold hello.map.eyeUplink, 40 m, for 5 s yourself first). \"never\" (the start) does not. Reflexes dodge a strike for you."New value: +"THE E.Y.E.'s EPB, from T+60, once a round, once linked (stay in hello.map.eyeUplink 5 s). { \"at\": { e, n } } calls it now: 4 s later a beam slanted in from the ship (hello.map.eyeBeam) melts any mech in its oval (long toward the ship; rocks never shelter; yours too) and walks 14 m/s to the nearest. Refused unlinked, outside the zone and after the nuke's siren. \"auto\" lets the reflexes call it on a foe seen standing still once linked; it does not walk you to THE DRUM or link for you (hold hello.map.eyeUplink, 40 m, for 5 s yourself first). \"never\" (the start) does not. Reflexes dodge a strike for you."
  3. Changed5 schema fields changed
    • addedInput schema / properties / command / properties / eye / type
      Added value: +[
      +  "string",
      +  "object",
      +  "null"
      +]
    • addedInput schema / properties / command / properties / moveTo / type
      Added value: +[
      +  "object",
      +  "null"
      +]
    • addedInput schema / properties / command / properties / refit / type
      Added value: +[
      +  "string",
      +  "object"
      +]
    • addedInput schema / properties / command / properties / refitPolicy / type
      Added value: +[
      +  "object",
      +  "null"
      +]
    • addedInput schema / properties / command / properties / watch / type
      Added value: +[
      +  "object",
      +  "null"
      +]
  4. Changed4 schema fields changed
    • changedInput schema / properties / command / properties / eye / description
      Previous value: -"THE E.Y.E.'s EPB, from T+120, once a round, once linked (stay in hello.map.eyeUplink 5 s). { \"at\": { e, n } } calls it now: 4 s later a beam slanted in from the ship (hello.map.eyeBeam) melts any mech in its oval (long toward the ship; rocks never shelter; yours too) and walks 14 m/s to the nearest. Refused unlinked, on THE BLIND SPOT (hello.map.eyeRefuge), outside the zone and after the nuke's siren. \"auto\" lets the reflexes call it on a foe seen standing still; \"never\" (the start) does not. Reflexes dodge a strike for you."New value: +"THE E.Y.E.'s EPB, from T+60, once a round, once linked (stay in hello.map.eyeUplink 5 s). { \"at\": { e, n } } calls it now: 4 s later a beam slanted in from the ship (hello.map.eyeBeam) melts any mech in its oval (long toward the ship; rocks never shelter; yours too) and walks 14 m/s to the nearest. Refused unlinked, on THE BLIND SPOT (hello.map.eyeRefuge), outside the zone and after the nuke's siren. \"auto\" lets the reflexes call it on a foe seen standing still once linked; it does not walk you to THE DRUM or link for you (hold hello.map.eyeUplink, 40 m, for 5 s yourself first). \"never\" (the start) does not. Reflexes dodge a strike for you."
    • changedInput schema / properties / command / properties / rules / description
      Previous value: -"Up to 6 standing rules { id, when, do, priority, quip }. While when holds (tests: seen, heard, lostSightS, afterS, heatAbovePct, heatBelowPct, healthBelowPct, partBelow { part, pct } with part head, torso, leftArm, rightArm, leftLeg or rightLeg, hit (true, \"front\" or \"rear\"), missile, enemyWithinM, enemyBeyondM; all you name must hold), do overrides the step. priority is 0 to 9 and the highest wins. This list replaces the old one; null clears it."New value: +"Up to 6 standing rules { id, when, do, priority, quip }. While when holds (tests: seen, heard, lostSightS, afterS, heatAbovePct, heatBelowPct, healthBelowPct, partBelow { part, pct } with part head, torso, leftArm, rightArm, leftLeg or rightLeg, hit (true, \"front\" or \"rear\"), missile, enemyWithinM, enemyBeyondM; all you name must hold; the last two count only a foe in sight or a guess off by 250 m or less), do overrides the step. do takes the step fields, no hold (to stand in a rule use go null). priority is 0 to 9 and the highest wins. This list replaces the old one; null clears it. A rule with a bad field is left out and named in REFUSED; a list with no good rule keeps your old rules."
    • changedInput schema / properties / command / properties / watch / description
      Previous value: -"Where the torso looks while nothing is in sight: { e, n }. null looks along the path. A name or anchor works only inside a plan step or a rule. Sent alone it keeps a running plan."New value: +"Where the torso looks while nothing is in sight: { e, n }. Unset aims at your guess of the foe (so does enemy with the foe out of sight); null looks along the path. A name or anchor works only inside a plan step or a rule. Sent alone it keeps a running plan."
    • changedInput schema / properties / command / properties / weapons / description
      Previous value: -"free fires at will. hold never fires (hide, ambush, cool down)."New value: +"free is permission, not a trigger: a gun fires only when the reticle is inside about 1.4 times the foe's size (0.5 degree at 500 m), so moving or turning delays shots. Past 1000 m the rail drops most charges unless you stand still with zoom. hold never fires (hide, ambush, cool down)."
  5. Changed2 schema fields changed
    • changedInput schema / properties / command / properties / plan / description
      Previous value: -"Up to 4 steps, run one after the other. A step is order fields (go, pace, stance, engageRangeM, weapons, jets, zoom, watch) plus until (a test such as { \"arrived\": true } or { \"seen\": true }) and maxS (seconds, default 120). go and watch take a landmark name, a grid square such as D5 or D5-7, a point { e, n } or an anchor word: enemy, cover, high, away, lastSeen, threat. A step ends when its until holds or at maxS; with go and no until, on arrival. A new plan replaces the old one, restarts at step 1 and clears the intent; null clears it."New value: +"Up to 4 steps, run one after the other. A step is order fields (go, pace, stance, engageRangeM, weapons, jets, zoom, watch, hold) plus until (a test such as { \"arrived\": true } or { \"seen\": true }) and maxS (seconds, default 120). hold true holds ground: it walks to go first (or stays put) and never walks toward the foe, but still fires. go and watch take a landmark name, a grid square such as D5 or D5-7, a point { e, n } or an anchor word: enemy, cover, high, away, lastSeen, threat. A step ends when its until holds or at maxS; with go and no until, on arrival. A new plan replaces the old one, restarts at step 1 and clears the intent; null clears it."
    • changedInput schema / properties / command / properties / say / description
      Previous value: -"A line for the radio, as text (nothing is spoken). 3 words at most; the game cuts the rest. A brevity code fits: EYES ON, LOST YOU, RUNNING HOT, COLD IRON, TUBES DRY, OVER THE RISE, FALLOUT, THUNDER COMING."New value: +"A line for the radio, as text (nothing is spoken). 3 words at most; the game cuts the rest. In the arena a line sent before the round goes out as it starts. A brevity code fits: EYES ON, LOST YOU, RUNNING HOT, COLD IRON, TUBES DRY, OVER THE RISE, FALLOUT, THUNDER COMING."
  6. Changed2 schema fields changed
    • changedInput schema / properties / command / properties / plan / description
      Previous value: -"Up to 4 steps, run one after the other. A step is order fields (go, pace, stance, engageRangeM, weapons, jets, zoom, watch) plus until (a test such as { \"arrived\": true } or { \"seen\": true }) and maxS (seconds, default 120). go and watch take a landmark name, a grid square such as D5 or D5-7, a point { e, n } or an anchor word: enemy, cover, high, away, lastSeen, threat. A step with go and no until ends on arrival. A new plan replaces the old one, restarts at step 1 and clears the intent; null clears it."New value: +"Up to 4 steps, run one after the other. A step is order fields (go, pace, stance, engageRangeM, weapons, jets, zoom, watch) plus until (a test such as { \"arrived\": true } or { \"seen\": true }) and maxS (seconds, default 120). go and watch take a landmark name, a grid square such as D5 or D5-7, a point { e, n } or an anchor word: enemy, cover, high, away, lastSeen, threat. A step ends when its until holds or at maxS; with go and no until, on arrival. A new plan replaces the old one, restarts at step 1 and clears the intent; null clears it."
    • changedInput schema / properties / command / properties / watch / description
      Previous value: -"Where the torso looks while nothing is in sight: { e, n }. null looks along the path. A name or anchor works only inside a plan step or a rule."New value: +"Where the torso looks while nothing is in sight: { e, n }. null looks along the path. A name or anchor works only inside a plan step or a rule. Sent alone it keeps a running plan."
  7. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: orders persist until replaced, omitted fields preserve the current order (patch semantics, consistent with idempotentHint=false), and a throughput cap of 4 commands a second. It does not say what a refusal or error looks like, and annotations already cover the non-destructive write profile.

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?

Six short sentences, front-loaded with purpose then nesting rule then persistence then the sibling redirect; nearly every clause earns its place. "Send pass." is telegraphic and "work here too" lacks a clear referent, keeping it short of a 5.

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 nested-object mutation tool with no output schema, the description covers what an agent needs to call it correctly: nesting, patch behavior, persistence, rate limit, and preference relative to `act`. Error/refusal handling is the main omission, and annotations already carry the safety profile.

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, but the description adds meaningful semantics the schema does not: fields must be nested under "command", every field is optional, and a missing field keeps the current order. It also notes plan/rules/quips/intent "work here too," though without naming the other tool that phrase is vague.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Give orders to your mech" plus optional radio line), and the closing sentence routes the agent away from the sibling `act`. It does not differentiate from `release_command` or `take_command`, so the picture is clear but partial.

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?

Explicitly names the alternative and a preference: "act sends and waits in one call; prefer act," which implies this tool is the fire-and-forget path. The inverse condition (use this when you do not want to block) is left to inference, and no guidance covers release_command/take_command.

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.