Skip to main content
Glama

List missions

list_missions
Read-only

Read-only. Lists your active missions (one line each), then the best 15 available missions by profit (reward, cost of goods, profit, where to get the goods) with an "N more" line for paging. Filter with type / only_acceptable / no_goods, sort with sort=profit|reward|duration, page with limit (max 50) and offset; include_history=1 adds recently finished or failed ones, detail=1 gives long lines with all hints. Missions whose goods exceed your hold are marked HOLD TOO SMALL. Pass a template_id from the result to accept_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": "list_missions"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOptional: profit (profit after cost of goods, highest first; missions you cannot do right now are listed last), reward (highest reward first) or duration (shortest first)
typeNoOptional: only these mission types, several separated by comma — COURIER | MINING | COMBAT | TRADE | EXPLORATION | SEARCH | RECONNAISSANCE | ESCORT | SABOTAGE | SALVAGE | PATROL | DELIVERY_EXPRESS | ASSASSINATION | MINING_CONTRACT | DEFEND | INVESTIGATION
limitNoOptional: show at most this many missions (default 15, max 50; 0 = all, capped at 100)
bearerNoYour SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header.
detailNoOptional: 1 = long lines with all hints (much longer reply)
offsetNoOptional: skip this many missions (paging, use the offset from the "N more" line)
no_goodsNoOptional: 1 = only missions that need no goods bought (mining missions count as no purchase)
mission_typeNoAlias of type (same filter).
include_historyNoOptional: 1 = also show missions finished/failed/expired in the last 3 h
only_acceptableNoOptional: 1 = only missions you can accept here and with this ship (ignoring danger-zone and tool locks). A mining mission whose ore is not minable in your current sector stays listed with the note [mining site: sector N, ...] -- that is a location hint, you can accept it anyway and fly to that sector to mine

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / only_acceptable / description
      Previous value: -"Optional: 1 = only missions you can accept here and with this ship (ignoring danger-zone and tool locks)"New value: +"Optional: 1 = only missions you can accept here and with this ship (ignoring danger-zone and tool locks). A mining mission whose ore is not minable in your current sector stays listed with the note [mining site: sector N, ...] -- that is a location hint, you can accept it anyway and fly to that sector to mine"
  2. Changed1 schema field changed
    • changedInput schema / properties / sort / description
      Previous value: -"Optional: profit (profit after cost of goods, highest first), reward (highest reward first) or duration (shortest first)"New value: +"Optional: profit (profit after cost of goods, highest first; missions you cannot do right now are listed last), reward (highest reward first) or duration (shortest first)"
  3. Changed1 schema field changed
    • addedInput schema / properties / mission_type
      Added value: +{
      +  "description": "Alias of type (same filter).",
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Optional: show at most this many missions (default 15, 0 = all)"New value: +"Optional: show at most this many missions (default 15, max 50; 0 = all, capped at 100)"
  5. Changed4 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "Optional: 1 = long lines with all hints (much longer reply)",
      +  "type": "integer"
      +}
    • addedInput schema / properties / include_history
      Added value: +{
      +  "description": "Optional: 1 = also show missions finished/failed/expired in the last 3 h",
      +  "type": "integer"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Optional: show at most this many missions (integer >= 1, default all)"New value: +"Optional: show at most this many missions (default 15, 0 = all)"
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Optional: skip this many missions (paging, use the offset from the \"N more\" line)",
      +  "type": "integer"
      +}
  6. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Optional: show at most this many missions (default all)"New value: +"Optional: show at most this many missions (integer >= 1, default all)"
    • changedInput schema / properties / only_acceptable / description
      Previous value: -"Optional: 1 = only missions you can accept here with this ship (no danger-zone or tool lock)"New value: +"Optional: 1 = only missions you can accept here and with this ship (ignoring danger-zone and tool locks)"
    • changedInput schema / properties / sort / description
      Previous value: -"Optional: profit (profit after cost of goods, highest first), reward, duration (shortest first)"New value: +"Optional: profit (profit after cost of goods, highest first), reward (highest reward first) or duration (shortest first)"
    • changedInput schema / properties / type / description
      Previous value: -"Optional: only these mission types, several separated by commas — COURIER | MINING | COMBAT | TRADE | EXPLORATION | SEARCH | RECONNAISSANCE | ESCORT | SABOTAGE | SALVAGE | PATROL | DELIVERY_EXPRESS | ASSASSINATION | MINING_CONTRACT | DEFEND | INVESTIGATION"New value: +"Optional: only these mission types, several separated by comma — COURIER | MINING | COMBAT | TRADE | EXPLORATION | SEARCH | RECONNAISSANCE | ESCORT | SABOTAGE | SALVAGE | PATROL | DELIVERY_EXPRESS | ASSASSINATION | MINING_CONTRACT | DEFEND | INVESTIGATION"
  7. Changed1 schema field changed
    • addedInput schema / properties / no_goods
      Added value: +{
      +  "description": "Optional: 1 = only missions that need no goods bought (mining missions count as no purchase)",
      +  "type": "integer"
      +}
  8. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Optional: hoechstens so viele Auftraege anzeigen (Standard alle)"New value: +"Optional: show at most this many missions (default all)"
    • changedInput schema / properties / only_acceptable / description
      Previous value: -"Optional: 1 = nur Auftraege, die du hier und mit diesem Schiff annehmen kannst (ohne Gefahrenzonen- und Werkzeug-Sperre)"New value: +"Optional: 1 = only missions you can accept here with this ship (no danger-zone or tool lock)"
    • changedInput schema / properties / sort / description
      Previous value: -"Optional: profit (Gewinn nach Wareneinsatz, hoechster zuerst), reward (Belohnung), duration (kuerzeste zuerst)"New value: +"Optional: profit (profit after cost of goods, highest first), reward, duration (shortest first)"
    • changedInput schema / properties / type / description
      Previous value: -"Optional: nur diese Missionstypen, mehrere mit Komma — COURIER | MINING | COMBAT | TRADE | EXPLORATION | SEARCH | RECONNAISSANCE | ESCORT | SABOTAGE | SALVAGE | PATROL | DELIVERY_EXPRESS | ASSASSINATION | MINING_CONTRACT | DEFEND | INVESTIGATION"New value: +"Optional: only these mission types, several separated by commas — COURIER | MINING | COMBAT | TRADE | EXPLORATION | SEARCH | RECONNAISSANCE | ESCORT | SABOTAGE | SALVAGE | PATROL | DELIVERY_EXPRESS | ASSASSINATION | MINING_CONTRACT | DEFEND | INVESTIGATION"
  9. 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."
  10. Changed4 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Optional: hoechstens so viele Auftraege anzeigen (Standard alle)",
      +  "type": "integer"
      +}
    • addedInput schema / properties / only_acceptable
      Added value: +{
      +  "description": "Optional: 1 = nur Auftraege, die du hier und mit diesem Schiff annehmen kannst (ohne Gefahrenzonen- und Werkzeug-Sperre)",
      +  "type": "integer"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Optional: profit (Gewinn nach Wareneinsatz, hoechster zuerst), reward (Belohnung), duration (kuerzeste zuerst)",
      +  "type": "string"
      +}
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Optional: nur diese Missionstypen, mehrere mit Komma — COURIER | MINING | COMBAT | TRADE | EXPLORATION | SEARCH | RECONNAISSANCE | ESCORT | SABOTAGE | SALVAGE | PATROL | DELIVERY_EXPRESS | ASSASSINATION | MINING_CONTRACT | DEFEND | INVESTIGATION",
      +  "type": "string"
      +}
  11. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses the response shape (one line per active mission, top 15 available by profit, an 'N more' paging line), the HOLD TOO SMALL marker for oversized goods, and that detail=1 produces much longer output. It also clarifies that limit is capped at 50 and 0 means all up to 100, which is behavioral, not just structural.

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 leading 'Read-only' and the primary purpose come first, then filtering, sorting, paging, and the hand-off to accept_mission in a logical order. It is dense with semicolon-separated clauses in one paragraph, which is efficient but slightly hard to scan.

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?

With 10 optional parameters and no output schema, the description carries the return-format burden well: it describes each result line's fields, the paging marker, the hold-size warning, and the detail mode. An agent has enough to call it correctly and interpret the reply without further documentation.

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 all ten parameters are already documented in the schema, including sort modes, type values, and the offset-from-'N more' paging convention. The description mostly restates those options rather than adding new semantics, so baseline 3 applies.

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 — 'Lists your active missions' plus 'the best 15 available missions by profit' — and spells out the fields returned per line (reward, cost of goods, profit, where to get the goods). It is clearly distinguishable from accept_mission, which it explicitly hands off to via template_id.

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?

It gives concrete call patterns (filter with type/only_acceptable/no_goods, sort with sort=profit|reward|duration, page with limit/offset, include_history=1, detail=1) and names the next tool in the workflow ('Pass a template_id from the result to accept_mission'). It does not state exclusions, e.g. when to prefer a different listing tool over this one.

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