Skip to main content
Glama

SPACE-CORE

by at.space-core
OverviewDiscussionsAdmin

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.

Input Schema

NameRequiredDescriptionDefault
sortNoOptional: profit (profit after cost of goods, highest first), 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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mission_type
      Added value: +{
+  "description": "Alias of type (same filter).",
+  "type": "string"
+}
  2. 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)"
  3. 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"
+}
  4. 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"
  5. 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"
+}
  6. 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"
  7. 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."
  8. 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"
+}
  9. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorld/destructive, so the 'Read-only' opener is largely redundant, but the description adds real behavioral detail beyond them: the default top-15-by-profit ordering, the 'N more' paging line, the HOLD TOO SMALL marking, and the much-longer reply under detail=1. It does not discuss auth failure modes beyond the bearer param, keeping it from a 5.

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 default output, then one clause per capability. It is dense and somewhat run-on, and 'Read-only' duplicates the annotation, but nearly every clause carries actionable information.

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 no output schema, the description carries the return-shape burden and does so: active vs available sections, profit fields listed, paging line, special markers, and detail mode. An agent has everything needed to call and interpret the result.

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 3 is the baseline, and the description earns an extra point by tying offset to the 'N more' line, restating the limit cap (max 50) and sort semantics in narrative form. It adds modest but genuine connective meaning over the per-parameter schema text.

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?

Opens with a specific verb+resource ('Lists your active missions') and immediately specifies the default result shape (one line each, best 15 by profit). It also distinguishes itself from the mutation sibling by ending with 'Pass a template_id from the result to accept_mission.'

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?

Explicitly routes the agent: filtering via type/only_acceptable/no_goods, sorting via sort=profit|reward|duration, paging via limit/offset, and history/detail via the flags. It names the downstream alternative (accept_mission) and the handoff value (template_id).

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

All SPACE-CORE 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