Skip to main content
Glama

Complete mission

complete_mission
Destructive

Complete a ready mission and claim its CWM reward. Omit mission_id to auto-complete the first READY one. Without mission_id and with nothing ready it fails with NO_READY_MISSION and lists progress and remaining time (ticks in parentheses) per active mission; a delivery mission may accept a partial delivery and ask for the rest on a later call. Check progress with list_missions or get_status. Changes state: pays out CWM and closes the mission.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "complete_mission"
  }
}

Input Schema

NameRequiredDescriptionDefault
bearerNoYour SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header.
mission_idNoplayer_mission_id (optional, auto-selects if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / bearer / description
      Added value: +"Your SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag this as destructive and non-idempotent, but the description adds real context the annotations cannot: the NO_READY_MISSION failure mode, that the error payload lists per-mission progress and remaining time in ticks, and that partial deliveries may require a follow-up call. It also states the payoff (CWM) and that the mission is closed, making the destructive hint concrete.

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?

Front-loaded with the action and reward, then the optional-parameter behavior, then failure and edge cases in descending priority. The middle sentence is a long run-on packing three separate facts, which slightly hurts scannability but nothing is truly wasted.

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?

For a two-parameter mutation tool with full schema coverage and no output schema, this covers action, side effects, error behavior, and the partial-delivery edge case. An agent has everything needed to call it correctly and interpret a failure.

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% and the mission_id field already says it auto-selects if omitted, so the baseline is 3. The description adds the qualifying detail that auto-selection targets the first READY mission specifically, which is meaningful beyond the schema wording.

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?

"Complete a ready mission and claim its CWM reward" gives a specific verb (complete/claim) plus the resource (mission) and the outcome, which cleanly separates it from accept_mission and abandon_mission. The READY precondition tells an agent exactly which mission state this acts on.

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?

It states when to call with an explicit mission_id versus omitting it for auto-selection, and routes the agent to list_missions or get_status to check progress first. The alternative tools are named with the condition that selects them.

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