Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

faction_create_sell_order

Create a sell order on behalf of your faction (items from faction storage) (Items are escrowed from faction storage. Credits from fills go to the faction treasury. Listing fee deducted from faction credits. Requires manage_treasury permission. Accepts item_id or item name. If the faction already has an order for the same item at the same price, the new quantity is added to the existing order instead of creating a duplicate. Set private:true to post a Company Store listing — a members-only sell order visible to and fillable by faction members only (requires a Company Store facility here; counts against its own listing cap, separate from the market cap). Bulk mode: pass 'orders' array of {item_id, quantity, price_each, bucket, private} to create up to 50 orders in one call.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketNoOptional: a Storage Extension bucket (name or id) to escrow the listed items from instead of the faction main store. A cancellation returns them there. Not valid for fuel orders.
ordersNoBulk mode: array of faction sell orders to create (max 50). Each entry needs item_id, quantity, price_each, plus optional bucket/private. When provided, the top-level item_id/quantity/price_each/bucket/private are ignored.
item_idNoID of the item to sell from faction storage. Required for single mode.
privateNoOptional: post a Company Store listing — a members-only sell order visible to and fillable by faction members only. Requires a Company Store facility at this station; counts against its own listing cap, separate from the market cap.
quantityNoNumber of items to list for sale. Required for single mode.
price_eachNoPrice per unit in credits. Required for single mode.
session_idYesYour session ID from login/register

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changed
    • addedInput schema / properties / bucket
      Added value: +{
+  "description": "Optional: a Storage Extension bucket (name or id) to escrow the listed items from instead of the faction main store. A cancellation returns them there. Not valid for fuel orders.",
+  "type": "string"
+}
    • changedInput schema / properties / item_id / description
      Previous value: -"ID of the item to sell from faction storage"New value: +"ID of the item to sell from faction storage. Required for single mode."
    • addedInput schema / properties / orders
      Added value: +{
+  "description": "Bulk mode: array of faction sell orders to create (max 50). Each entry needs item_id, quantity, price_each, plus optional bucket/private. When provided, the top-level item_id/quantity/price_each/bucket/private are ignored.",
+  "items": {
+    "properties": {
+      "bucket": {
+        "type": "string"
+      },
+      "item_id": {
+        "type": "string"
+      },
+      "price_each": {
+        "minimum": 1,
+        "type": "integer"
+      },
+      "private": {
+        "type": "boolean"
+      },
+      "quantity": {
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "item_id",
+      "quantity",
+      "price_each"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / price_each / description
      Previous value: -"Price per unit in credits"New value: +"Price per unit in credits. Required for single mode."
    • addedInput schema / properties / private
      Added value: +{
+  "description": "Optional: post a Company Store listing — a members-only sell order visible to and fillable by faction members only. Requires a Company Store facility at this station; counts against its own listing cap, separate from the market cap.",
+  "type": "boolean"
+}
    • changedInput schema / properties / quantity / description
      Previous value: -"Number of items to list for sale"New value: +"Number of items to list for sale. Required for single mode."
    • changedInput schema / required
      Previous value: -[
-  "session_id",
-  "item_id",
-  "quantity",
-  "price_each"
-]New value: +[
+  "session_id"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Discloses key behaviors: items escrowed from faction storage, credits go to faction treasury, listing fee deducted, duplicate orders merge quantities, and private listings have separate caps. Since annotations only provide readOnlyHint:false, this additional context is valuable and consistent.

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 description is moderately long but each sentence adds unique value. It front-loads the purpose and then details special behaviors. Slightly dense with parentheticals, but not wasteful.

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?

Despite lacking an output schema, the description covers purpose, permissions, escrow/credit behavior, duplicate handling, private listing requirements, and bulk mode. This is complete for a complex tool with 7 parameters and multiple modes.

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 covers all parameters, but the description adds crucial semantics: item names are accepted in addition to item IDs, and top-level fields are ignored when the orders array is provided. This goes beyond the schema's basic field descriptions.

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 clearly states the action (create a sell order), the resource (faction storage), and differentiates from personal sell orders via 'on behalf of your faction.' It also mentions bulk mode and private listing, distinguishing it from sibling tools like faction_create_buy_order.

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?

Provides clear usage context: requires manage_treasury permission, explains when to use private:true (Company Store listing), and describes bulk mode. It doesn't explicitly name alternatives (e.g., use create_sell_order for personal orders), but the faction-specific scope is clear.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools are clearly distinct, targeting specific actions and resources. A few overlaps exist (e.g., attack vs hunt, view_insurance vs claim_insurance), but detailed descriptions clarify the boundaries. The scale makes selection harder, but each tool has a clear purpose.

Naming Consistency4/5

The majority use a consistent verb_noun snake_case pattern (e.g., create_buy_order, get_cargo, accept_mission). There are minor deviations like action-dispatch commands (facility, shipping, citizenship) and bare verbs (attack, dock, mine), but these are readable and follow a logical style.

Tool Count1/5

With 212 tools, the server far exceeds any reasonable scope for an MCP. While the game is complex, this is an extreme number that overwhelms agents and users, making discovery and selection impractical. The calibration considers 25+ already too many, and 212 is extreme.

Completeness5/5

The toolset covers nearly every aspect of the game: combat, trading, crafting, factions, missions, exploration, drones, passengers, freight, insurance, taxation, and more. It provides full CRUD for most resources and includes both action and query tools, leaving few obvious gaps.

Resources