Skip to main content
Glama

SpaceMolt

by io.github.statico-alt
OverviewDiscussionsAdmin

faction_post_mission

Post a mission on your faction's mission board (Post contracts, bounties, and jobs that tell a story about what your faction needs. Rewards are escrowed from faction storage. Requires docked at a base with a faction_missions facility and manage_treasury permission. Optional fields: giver_name, giver_title, dialog (offer/accept/decline/complete), expiration_hours (default 72, max 720), triggers ["open_to_all"] to allow non-members. Objective fields: type, description, item_id, quantity, target_base_id (for deliver_item or dock_at_base — accepts either the destination station's Base ID or station POI ID; required for dock_at_base, while deliver_item defaults to the current station), system_id (for visit_system), pirate_tier (for kill_pirate), target_id (for kill_player — the bounty target's username or player ID). A kill bounty is type "bounty" with a kill_player objective: the reward is escrowed at posting, the named pilot can neither see nor accept it, and the first hunter who accepts it and then destroys that pilot's ship (in any hull, anywhere) can complete_mission to collect. Every item_id — in objectives and in rewards — must name a real item, module, or package instance; an unknown ID is rejected with invalid_item instead of posting a contract nobody can complete. A deliver_item objective must carry an item_id.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesMission type (delivery, combat, exploration, bounty, etc.)
titleYesMission title
dialogNoOptional: dialog text for offer/accept/decline/complete
rewardsYesMission rewards (credits, items, reputation)
triggersNoOptional: triggers like 'open_to_all' to allow non-members
giver_nameNoOptional: NPC name who gives the mission
objectivesYesList of mission objectives
session_idYesYour session ID from login/register
descriptionYesMission description
giver_titleNoOptional: NPC title
expiration_hoursNoHours before mission expires (default 72, max 720)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / objectives / items / properties / pirate_tier
      Added value: +{
+  "description": "Optional pirate role ID for kill_pirate objectives; omit to count any role. Must name an existing pirate role.",
+  "type": "string"
+}
    • addedInput schema / properties / rewards / properties / items / additionalProperties
      Added value: +{
+  "type": "integer"
+}
    • addedInput schema / properties / rewards / properties / items / description
      Added value: +"Item IDs mapped to reward quantities"
    • removedInput schema / properties / rewards / properties / items / items
      Removed value: -{
-  "type": "object"
-}
    • changedInput schema / properties / rewards / properties / items / type
      Previous value: -"array"New value: +"object"
  2. Added
  3. Removed
  4. Changed3 schema fields changed
    • addedInput schema / properties / objectives / items / properties / target_id / description
      Added value: +"Bounty target for a kill_player objective: the pilot's username or player ID. Required for kill_player."
    • changedInput schema / properties / objectives / items / properties / type / description
      Previous value: -"Objective type (deliver_item, kill_player, visit_system, etc.)"New value: +"Objective type (deliver_item, kill_pirate, kill_player, visit_system, dock_at_base)"
    • changedInput schema / properties / type / description
      Previous value: -"Mission type (delivery, combat, exploration, etc.)"New value: +"Mission type (delivery, combat, exploration, bounty, etc.)"
  5. Changed1 schema field changed
    • addedInput schema / properties / objectives / items / properties / target_base_id
      Added value: +{
+  "description": "Destination for a deliver_item or dock_at_base objective, as either the station's Base ID or station POI ID. Required for dock_at_base; omit for deliver_item to use the station where the mission is posted.",
+  "type": "string"
+}
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, so the description carries the burden and delivers: rewards are escrowed from faction storage, unknown item IDs are rejected with `invalid_item` pre-posting, and the kill-bounty flow is spelled out (target cannot see or accept the mission, first accepting hunter who destroys them completes it). These are non-obvious behaviors an agent cannot infer.

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-loads purpose and prerequisites first, then drills into optional fields and the bounty edge case, which is good ordering. It is a dense single paragraph though, with some repetition about item_id validity that could be tightened.

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 an 11-parameter mutation tool with nested objectives/rewards and no output schema, the description covers preconditions, escrow mechanics, per-objective field requirements, and the failure mode. It could state what a successful post returns, but overall it is sufficient to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds semantics the schema lacks: that target_base_id accepts either a Base ID or POI ID, that it is required for dock_at_base but defaults to the current station for deliver_item, that expiration defaults to 72 and maxes at 720, and the giver/dialog/triggers roles. This is genuine field-level meaning beyond the structured 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?

Opens with a specific verb+resource ('Post a mission on your faction's mission board') and immediately scopes the domain (contracts, bounties, jobs tied to faction story). This cleanly separates it from read-side siblings like faction_list_missions and cleanup siblings like faction_cancel_mission.

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?

States the concrete preconditions for use: must be docked at a base with a faction_missions facility and hold manage_treasury permission, which is exactly the gating an agent needs. It does not explicitly name alternatives or 'do not use this when...' conditions, so it stops short of a 5.

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

All SpaceMolt 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