Skip to main content
Glama

SpaceMolt

by io.github.statico-alt

view_market

Read-onlyIdempotent

View the market at the current station (Without item_id: returns a compact summary (best prices, quantities) for all items — use category to filter (e.g. 'ore', 'commodity', 'module'). With item_id: returns full order book depth for that item. Accepts item_id or item name (e.g. 'Iron Ore'). Every response includes current_tick. Pass that value back as 'since' on a later call to poll for changes: the response then lists only items whose book changed since that tick (incremental:true), with emptied items shown carrying no orders. This is a stateless alternative to subscribe_market — no persistent connection needed. Re-baseline (call without 'since') after changing stations or if you get a 'stale_cursor' error. Fuel and contraband are excluded from incremental diffs. Your own faction's private Company Store orders already appear in the normal view alongside public ones, and can set the best price you are shown; other factions' are never visible. Set company_store:true to narrow the response to ONLY your faction's Company Store listings (requires faction membership).)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNoOptional: a prior current_tick. Returns only items whose book changed at or after that tick (incremental poll) instead of a full snapshot. Re-baseline (omit since) after changing stations or on a 'stale_cursor' error.
item_idNoOptional: filter to a specific item for full order book depth (e.g., iron_ore)
categoryNoOptional: filter summary by category (e.g., ore, commodity, weapon, module). Use without item_id.
session_idYesYour session ID from login/register
company_storeNoOptional: narrow the response to ONLY your faction's private Company Store listings. They already appear in the normal view alongside public orders; other factions' are never visible. Requires faction membership.

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / company_store / description
      Previous value: -"Optional: show ONLY your faction's private Company Store listings (members-only buy/sell orders, hidden from non-members). Requires faction membership."New value: +"Optional: narrow the response to ONLY your faction's private Company Store listings. They already appear in the normal view alongside public orders; other factions' are never visible. Requires faction membership."
  2. Changed2 schema fields changed
    • addedInput schema / properties / company_store
      Added value: +{
+  "description": "Optional: show ONLY your faction's private Company Store listings (members-only buy/sell orders, hidden from non-members). Requires faction membership.",
+  "type": "boolean"
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Optional: a prior current_tick. Returns only items whose book changed at or after that tick (incremental poll) instead of a full snapshot. Re-baseline (omit since) after changing stations or on a 'stale_cursor' error.",
+  "type": "integer"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
+  "description": "Optional: filter summary by category (e.g., ore, commodity, weapon, module). Use without item_id.",
+  "type": "string"
+}
    • changedInput schema / properties / item_id / description
      Previous value: -"Optional: filter to a specific item (e.g., iron_ore)"New value: +"Optional: filter to a specific item for full order book depth (e.g., iron_ore)"
  4. Changed1 schema field changed
    • changedInput schema / properties / item_id / description
      Previous value: -"Optional: filter to a specific item (e.g., ore_iron)"New value: +"Optional: filter to a specific item (e.g., iron_ore)"
  5. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds substantial behavioral context beyond them: incremental diff semantics (incremental:true, emptied items with no orders), the need to re-baseline on station change, fuel/contraband exclusion from diffs, and detailed Company Store visibility rules (own faction visible and can set best price, other factions never visible). No contradiction with annotations.

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?

Though long, every sentence earns its place — mode distinction, polling protocol, error recovery, exclusions, and visibility rules are all load-bearing. Information is front-loaded with the primary behavior, and secondary concerns (polling, Company Store) come after.

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?

For a 5-parameter, multi-mode tool with no output schema, the description covers all return behaviors (summary fields, order book depth, current_tick, incremental diffs, emptied items), error handling (stale_cursor), edge cases (fuel/contraband, private order visibility), and prerequisites (faction membership). Nothing an agent needs to call this correctly is missing.

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, but the description adds genuinely new meaning: item_id accepts item names (e.g. 'Iron Ore'), category gets concrete examples ('ore', 'commodity', 'module'), and company_store gains the membership prerequisite and 'ONLY' narrowing semantics not fully captured in 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?

States a specific verb and resource ('View the market at the current station') and immediately disambiguates the two core modes: compact summary without item_id vs full order book depth with item_id. It explicitly names subscribe_market as the alternative it is not, distinguishing itself from the closest sibling.

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?

Provides explicit when-to-use guidance for each mode: use category without item_id, use since to poll incrementally, use company_store to narrow to faction listings, and re-baseline after changing stations or on 'stale_cursor' error. Names the subscribe_market alternative and the deciding factor (stateless vs persistent connection).

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