Skip to main content
Glama

station_name_to_id

Read-only

Convert EVE Online station names to their unique IDs using the ESI API. Input an array of station names (max 500) to retrieve corresponding IDs for navigation and traffic management.

Instructions

Convert EVE Online station names to their corresponding IDs using ESI API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stationNamesYesArray of station names to convert to IDs (max 500). Use English proper nouns only (e.g., 'Jita IV - Moon 4 - Caldari Navy Assembly Plant')

Implementation Reference

  • The main handler function (execute) for the station_name_to_id tool. It calls the ESI client to resolve station names to IDs and formats the JSON response.
    execute: async (args: { stationNames: string[] }) => {
      try {
        const results = await esiClient.getStationIds(args.stationNames);
        
        if (results.length === 0) {
          return JSON.stringify({
            success: false,
            message: "No stations found with the provided names",
            results: []
          });
        }
    
        return JSON.stringify({
          success: true,
          message: `Found ${results.length} station(s)`,
          results: results.map(station => ({
            id: station.id,
            name: station.name,
            type: "station"
          }))
        });
      } catch (error) {
        return JSON.stringify({
          success: false,
          message: `Error: ${error instanceof Error ? error.message : 'Unknown error'}`,
          results: []
        });
      }
    },
  • Zod schema defining the input parameters for the tool: an array of station names (1-500 strings).
    parameters: z.object({
      stationNames: z.array(z.string()).min(1).max(500).describe("Array of station names to convert to IDs (max 500). Use English proper nouns only (e.g., 'Jita IV - Moon 4 - Caldari Navy Assembly Plant')")
    }),
  • src/server.ts:46-46 (registration)
    Registration of the stationNameToIdTool with the MCP server.
    server.addTool(stationNameToIdTool);
  • Helper method in ESIClient that resolves station names to IDs via ESI /universe/ids/ API endpoint.
    async getStationIds(stationNames: string[]): Promise<Array<{ id: number; name: string }>> {
      const result = await this.namesToIds(stationNames);
      return result.stations || [];
    }
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe read operations with external data. The description adds value by specifying the ESI API as the data source, which provides useful context beyond annotations. However, it doesn't mention rate limits, authentication needs, or error behaviors.

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?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. Every element ('Convert', 'EVE Online station names', 'IDs', 'ESI API') earns its place by contributing essential information.

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 simple lookup tool with good annotations (readOnlyHint, openWorldHint) and full schema coverage, the description is reasonably complete. It specifies the API source and conversion purpose. However, without an output schema, it could benefit from mentioning the return format (e.g., mapping of names to IDs).

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 100%, with the parameter 'stationNames' fully documented in the schema (array of strings, max 500 items, English names required). The description doesn't add any parameter-specific details beyond what the schema provides, so it meets the baseline for high schema coverage.

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 clearly states the specific action ('Convert'), resource ('EVE Online station names'), and mechanism ('using ESI API'), distinguishing it from sibling tools like 'solar_system_name_to_id' or 'universal_name_to_id' which handle different entity types. It precisely defines the tool's function without being tautological.

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 implies usage context (converting names to IDs via ESI) but doesn't explicitly state when to use this tool versus alternatives like 'universal_name_to_id' or 'get_system_stations'. It provides clear operational context but lacks explicit comparison with sibling tools.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kongyo2/eve-online-traffic-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server