Skip to main content
Glama

inara_search_nearest

Find the nearest stations or systems to a given Elite Dangerous system using Inara data, with website search fallback when API access is unavailable.

Instructions

Nearest stations/systems via Inara API (needs INARA_API_KEY + app access).

Falls back to website search URLs when the API app has no access.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "system_name": "<system_name>"
    },
    "name": "inara_search_nearest"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNostation
commanderNo
system_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does usefully disclose the auth requirement and the fallback to website search URLs (implying results may sometimes be URLs rather than structured data), but it says nothing about rate limits, failure modes, what 'search' selects, or why a commander value matters.

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 sentences with no filler, and the core capability is front-loaded before the auth caveat. It is efficient, though the parenthetical interrupts the main clause and no structure is given to the two distinct facts.

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 the auth/fallback note covers the most important environment concern. Still, for a 3-parameter proximity search with zero schema descriptions and several near-identical siblings, the omission of origin semantics, parameter meanings, and sibling routing leaves real gaps.

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 description coverage is 0% across 3 parameters, so the description should compensate and largely does not: system_name is never identified as the reference point, the 'search' enum-like values (default 'station', presumably also systems) are only hinted at by 'stations/systems', and 'commander' is unexplained.

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

Purpose3/5

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

The description names a resource (stations/systems) and an access route (Inara API), so the general purpose is inferable. But it never says 'nearest to what' — the required system_name as the origin point is left implicit — and it does not distinguish itself from close siblings like spansh_find_nearby_stations, inara_website_search, or spansh_search_stations.

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 guidance: no condition for choosing this over spansh_find_nearby_stations or inara_website_search, and no stated exclusions. The only situational note is a prerequisite (API key + app access) and a fallback, which is setup context rather than selection guidance.

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