Skip to main content
Glama

SPACE-CORE

by at.space-core
OverviewDiscussionsAdmin

Accept mission

accept_mission

Accept a mission by template_id from list_missions (mission_id works as alias). Ship must be IDLE, DOCKED or ON_MISSION. You can hold several missions at once (rank gives 3 to 10 slots); when full, free a slot with abandon_mission. If the goods exceed your hold, deliver in parts with complete_mission; bought ore does not count for mining missions.

Input Schema

NameRequiredDescriptionDefault
bearerNoYour SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header.
mission_idNoAlias of template_id (if both are sent they must be equal).
template_idYesMission template ID from list_missions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / mission_id
      Added value: +{
+  "description": "Alias of template_id (if both are sent they must be equal).",
+  "type": "integer"
+}
  2. 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."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations, the description discloses important behavior: mission slot limits by rank, the ability to hold several missions, the need to free slots when full, partial delivery behavior, and the mining-mission restriction that bought ore does not count. These details materially help an agent avoid failed calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and parameter source, then proceeds to prerequisites and edge cases. Every sentence adds operational value, including the final mining-mission caveat.

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 mutation tool with no output schema, the description is rich about prerequisites, capacity, and alternatives. It could be slightly more complete by hinting at the response or error behavior after acceptance, but the operational guidance is otherwise strong.

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 both template_id and mission_id are already explained in the input schema. The description repeats that template_id comes from list_missions and that mission_id is an alias, but adds little parameter syntax or format detail beyond the schema.

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 specific verb and resource: accept a mission using template_id from list_missions. It distinguishes this operation from sibling tools by naming list_missions as the source, abandon_mission for freeing slots, and complete_mission for partial delivery.

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 explicitly gives prerequisites (ship must be IDLE, DOCKED, or ON_MISSION) and alternatives for edge cases. When mission slots are full it directs the agent to abandon_mission, and when cargo exceeds hold capacity it directs partial completion via complete_mission.

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