Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

view_orders

Read-onlyIdempotent

View your own orders at a station (Shows your active buy and sell orders at a station, including fill progress. Provide station_id as either the station's Base ID or station POI ID to view without being docked; omit to use your current docked station. Supports pagination, filtering, and sorting. Options: scope ('personal' or 'faction', default 'personal'), page (default 1), page_size (default 20, max 50), order_type ('buy' or 'sell'), item_id (exact match on item name or ID), search (substring match on item names), sort_by ('newest', 'oldest', 'price_asc', 'price_desc', default 'newest').)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
scopeNoOrder scope: 'personal' (default) or 'faction' (requires faction membership)
searchNoFilter by substring match on item names
item_idNoFilter by item (exact match on item name or ID)
sort_byNoSort order: 'newest' (default), 'oldest', 'price_asc', 'price_desc'
page_sizeNoResults per page (default 20, max 50)
order_typeNoFilter by order type: 'buy' or 'sell'
session_idYesYour session ID from login/register
station_idNoOptional: station Base ID or station POI ID to view your orders at without being docked. If omitted, must be docked and uses the current station.

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / station_id / description
      Previous value: -"Optional: station ID to view your orders at without being docked. If omitted, must be docked and uses the current station."New value: +"Optional: station Base ID or station POI ID to view your orders at without being docked. If omitted, must be docked and uses the current station."
  2. Changed7 schema fields changed
    • addedInput schema / properties / item_id
      Added value: +{
+  "description": "Filter by item (exact match on item name or ID)",
+  "type": "string"
+}
    • addedInput schema / properties / order_type
      Added value: +{
+  "description": "Filter by order type: 'buy' or 'sell'",
+  "enum": [
+    "buy",
+    "sell"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page number (default 1)",
+  "type": "integer"
+}
    • addedInput schema / properties / page_size
      Added value: +{
+  "description": "Results per page (default 20, max 50)",
+  "type": "integer"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "Order scope: 'personal' (default) or 'faction' (requires faction membership)",
+  "enum": [
+    "personal",
+    "faction"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / search
      Added value: +{
+  "description": "Filter by substring match on item names",
+  "type": "string"
+}
    • addedInput schema / properties / sort_by
      Added value: +{
+  "description": "Sort order: 'newest' (default), 'oldest', 'price_asc', 'price_desc'",
+  "enum": [
+    "newest",
+    "oldest",
+    "price_asc",
+    "price_desc"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows this is a safe read. The description adds the important behavioral nuance that station_id may be a Base ID or POI ID and that omitting it requires being docked, plus it enumerates enumeration defaults. It does not mention what happens when there are no orders or whether pagination metadata is included, but for a read-only list tool the added context is already reasonably rich, so 4 is fair rather than 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?

The description is one dense paragraph, but every sentence earns its place: the first sentence states the purpose, the second clarifies docking behavior, and the third enumerates all filtering/sorting/default options. It is somewhat run-on and the option list is long, but it is front-loaded with the most important info (what it does) before the parameter details, and there is no fluff. Slightly better structure with bullets or shorter sentences would make it a 5.

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 read-only, idempotent list tool with 100% schema coverage and no output schema, the description covers the core invocation context: what it lists, when docking matters, how to paginate/filter/sort, and what the defaults are. The main omission is return-value context, but with readOnly/idempotent annotations and a straightforward orders list, that is not a critical gap. It is complete enough for an agent to select and call the tool correctly, though explicit return format or a note that results contain fill progress already mentioned in the first parenthetical.

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 the baseline is 3. The description adds value by explaining the station_id either/or behavior (Base ID or POI ID vs current docked station), which is not fully conveyed by the schema property alone. It also consolidates all parameters into one sentence with defaults and option lists, giving the agent a quick semantic map. The only gap is that the description doesn't state the exact return shape, but that's not parameter semantics per se.

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 'View your own orders at a station' and immediately distinguishes it as a read operation for buy and sell orders. Though siblings include create_buy_order, create_sell_order, cancel_order, and modify_order, there is no other 'view_orders' sibling, and the first sentence names the exact resource (orders at a station) and the agent's own scope, so the tool is unambiguously identified.

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?

The description explicitly explains the docking requirement: provide station_id to view without docking, or omit it to use the current docked station. It also documents the scope options and filtering/sorting capabilities. It does not explicitly name alternatives or say 'use X instead when...', but among the siblings the closest related tools are create_buy_order/create_sell_order/cancel_order/modify_order, which are clearly different actions; still, it never explicitly says 'use this instead of view_market when you want your own orders rather than the market's orders,' so it misses the explicit when-not/alternative guidance.

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