Skip to main content
Glama

eddn_live_sample

Capture a bounded sample of live EDDN relay messages, optionally filtered by schema, to inspect current Elite Dangerous market or event data.

Instructions

Bounded sample of live EDDN relay messages (needs pyzmq + network).

schema: substring filter on $schemaRef, e.g. "commodity". None = all.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "eddn_live_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemaNo
timeout_sNo
max_messagesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / schema
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Schema"
      +}
  2. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does disclose one meaningful behavioral fact beyond the schema: the tool requires pyzmq and live network access, which implies it can fail or hang where other tools cannot. It does not say what happens on timeout, whether partial results are returned when max_messages is not reached, or whether the call blocks for the full timeout_s window.

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?

Two short lines with no filler, and the core purpose is front-loaded before the dependency note and the parameter hint. The dangling "schema:" fragment reads like a schema comment pasted into prose rather than an integrated sentence, which slightly hurts flow but not comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and all three parameters are optional with sensible defaults. What remains missing for a live-network tool is failure and timing behavior, plus any indication of message volume or rate considerations when sampling a relay feed.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, and it only covers one of three parameters: "schema" is explained as a substring filter on $schemaRef with "None = all." timeout_s and max_messages receive no explanation of units, semantics, or interaction with "bounded," leaving the two parameters that actually control the sampling behavior undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: "Bounded sample of live EDDN relay messages." The words "live" and "bounded" distinguish it from the many static-lookup siblings (edsm_system_info, spansh_query_systems), so an agent can tell it retrieves a real-time stream rather than a database record. It stops short of naming an explicit alternative, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives among the ~50 sibling tools. The parenthetical "needs pyzmq + network" is a runtime prerequisite, not usage guidance, and it does not say what an agent should do if that dependency is absent.

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