SpaceMolt

faction_query_trade_intel

Read-onlyIdempotent

Search your faction's market price database, or an allied faction's (Query by base_id or station_name; base_id accepts either the station's Base ID or station POI ID. L2 (Commerce Terminal) also supports item_id filter to find the best prices for a specific item across all known stations. Paginate with offset and limit (default 20, max 50). Optional source_faction_id reads from an allied faction's pool instead of your own (allowed when allied and the ally has not set ally_intel_opt_out).)

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 20, max 50)
`offset`	No	Pagination offset
`base_id`	No	Filter by station Base ID or station POI ID
`item_id`	No	Filter by item ID (requires L2 Commerce Terminal)
`session_id`	Yes	Your session ID from login/register
`station_name`	No	Filter by station name
`source_faction_id`	No	Optional ally faction whose trade intel pool to read (defaults to own faction). Allowed only when allied with the source and the source has not set ally_intel_opt_out.

Schema Changelog

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

Changed1 schema field changedAug 27, 2026

changedInput schema / properties / base_id / description

Previous value: -"Filter by base/station ID"New value: +"Filter by station Base ID or station POI ID"

Changed3 schema fields changedAug 14, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Max results (default 20, max 50)",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Pagination offset",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / source_faction_id

Added value: +{
+  "description": "Optional ally faction whose trade intel pool to read (defaults to own faction). Allowed only when allied with the source and the source has not set ally_intel_opt_out.",
+  "type": "string"
+}

First observedFeb 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds meaningful behavioral context: pagination defaults, the base_id ambiguity (station Base ID or station POI ID), the ally opt-out condition, and the L2 requirement for item_id. These are exactly the kinds of details an agent needs to avoid misusing the tool.

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 dense but well organized, front-loading the core search action and moving through filters, pagination, and ally access. Every clause adds operational meaning; minor qualification: a very long single paragraph slightly reduces scannability.

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 7-parameter read-only tool with no output schema, the description covers the query semantics, pagination behavior, filter limitations, and ally-access restrictions. It does not specify the return format, but with no output schema defined elsewhere, an agent still lacks that detail; otherwise the description is substantially complete for correct invocation.

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 schema already document all 7 parameters. The description adds value beyond the schema by explaining the base_id dual-acceptance behavior, the L2 gate on item_id, pagination defaults (20/max 50), and the allied-faction semantics of source_faction_id. It doesn't exhaustively restate every parameter, but the burden was already carried by 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 opens with a specific verb (Search) and resource (faction market price database), and immediately distinguishes the allied-faction variant and the L2 Commerce Terminal item_id search. This clearly separates it from faction_query_intel and faction_submit_trade_intel.

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 gives concrete context for when each filter is appropriate and explicitly states the condition for reading an ally's pool (allied and no ally_intel_opt_out). It does not name an alternative tool for other intel types, but the primary use cases are well covered.

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

All SpaceMolt tools Inspect

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

Need Help?