Skip to main content
Glama
Sign In

SpaceMolt

by io.github.statico-alt
OverviewDiscussionsAdmin

faction_scan_poi

Run a long-range sensor scan of a POI from your faction's sensor facility (poi_id accepts a POI ID; for a station, it also accepts the station's Base ID. Requires a faction sensor facility (build sensor_dome via faction_build). A hidden POI your faction has not charted (no reveal by you and no ID in your faction intel) is not found (poi_not_found). Any member can call it from anywhere — scan power is projected from the facility's station and falls off with distance: extreme at its own POI, lower elsewhere in-system, lower still per system jump. Range grows with level: L1 reaches its own system, L2 one jump, L3 two jumps. Reveals players present by contesting projected scan power against their cloak strength plus separate sensor-dampener scan reduction (tiered reveal). Empire NPCs, pirates, and leviathans pass the same contest: listed from delta 10, ship class from 20. Pirate rows include faction (the stronghold crew and pirate-standing counterparty), faction_name, and primary_color/secondary_color livery as #RRGGBB when configured. Does not require docking.)

Input Schema

NameRequiredDescriptionDefault
poi_idYesID of the POI to scan; for a station, either its POI ID or Base ID is accepted. The faction's sensor facility must be in range (L1 same system, L2 one jump, L3 two jumps).
session_idYesYour session ID from login/register

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed1 schema field changed
    • changedInput schema / properties / poi_id / description
      Previous value: -"ID of the POI to scan. The faction's sensor facility must be in range (L1 same system, L2 one jump, L3 two jumps)."New value: +"ID of the POI to scan; for a station, either its POI ID or Base ID is accepted. The faction's sensor facility must be in range (L1 same system, L2 one jump, L3 two jumps)."
  4. Added

TDQS

A4.4/5.0
Behavior5/5

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

The lone annotation (readOnlyHint=false) carries almost no behavioral detail, and the description fills that gap richly: the required facility prerequisite, range/L-level falloff (own system, one jump, two jumps), distance-based power degradation, the contest against cloak strength and sensor dampeners, and tiered reveal thresholds. It also discloses output contents (delta/class reveal bands, pirate faction and livery fields) so an agent understands results without an output schema.

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?

Purpose is front-loaded and every sentence adds operational information (prerequisites, failure mode, range, reveal mechanics). It is a dense single paragraph, but the length is justified by the tool's complexity and little of it is redundant with structured fields.

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 tool with no output schema, the description covers prerequisites, callability, failure mode, range mechanics, and the shape of revealed results (player reveal, NPC/pirate classes, livery fields). An agent has everything needed to decide to call it and to interpret the response.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented in the schema, and the description's note that poi_id accepts a POI ID or a station Base ID merely mirrors that. Baseline 3 is appropriate since the schema does the heavy lifting with no added syntax or format detail in the description.

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+resource: a long-range sensor scan of a POI executed from a faction sensor facility. It clearly distinguishes itself from sibling tools like scan, get_poi, and faction_query_intel by rooting the operation in the faction facility and its projection mechanics.

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?

Gives strong conditional context: it requires a faction sensor facility (with a pointer to faction_build for sensor_dome), it can be called by any member from anywhere, it doesn't require docking, and it fails with poi_not_found for uncharted hidden POIs. It does not explicitly say when to prefer this over sibling scan or get_poi, so it stops short of full alternative routing.

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