Skip to main content
Glama

solar_system_name_to_id

Read-only

Convert EVE Online solar system names to their corresponding IDs using the ESI API. Input up to 500 system names for accurate and efficient ID retrieval.

Instructions

Convert EVE Online solar system names to their corresponding IDs using ESI API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
systemNamesYesArray of solar system names to convert to IDs (max 500). Use English proper nouns only (e.g., 'Jita', 'Amarr', 'Dodixie')

Implementation Reference

  • The execute handler function that implements the core logic of the solar_system_name_to_id tool. It takes system names, queries the ESI client for IDs, handles errors, and returns formatted JSON results.
    execute: async (args: { systemNames: string[] }) => {
      try {
        const results = await esiClient.getSolarSystemIds(args.systemNames);
        
        if (results.length === 0) {
          return JSON.stringify({
            success: false,
            message: "No solar systems found with the provided names",
            results: []
          });
        }
    
        return JSON.stringify({
          success: true,
          message: `Found ${results.length} solar system(s)`,
          results: results.map(system => ({
            id: system.id,
            name: system.name,
            type: "solar_system"
          }))
        });
      } catch (error) {
        return JSON.stringify({
          success: false,
          message: `Error: ${error instanceof Error ? error.message : 'Unknown error'}`,
          results: []
        });
      }
  • Zod input schema defining the parameters for the tool: an array of up to 500 solar system names.
    parameters: z.object({
      systemNames: z.array(z.string()).min(1).max(500).describe("Array of solar system names to convert to IDs (max 500). Use English proper nouns only (e.g., 'Jita', 'Amarr', 'Dodixie')")
    }),
  • src/server.ts:45-45 (registration)
    Registration of the solarSystemNameToIdTool with the FastMCP server.
    server.addTool(solarSystemNameToIdTool);
  • src/server.ts:3-6 (registration)
    Import of the solarSystemNameToIdTool for registration in the MCP server.
    solarSystemNameToIdTool,
    stationNameToIdTool,
    regionNameToIdTool,
    universalNameToIdTool
  • Helper method in ESIClient that performs the actual ESI API search for solar system names to IDs, used by the tool handler.
    async getSolarSystemIds(systemNames: string[]): Promise<Array<{ id: number; name: string }>> {
Behavior3/5

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

Annotations already declare readOnlyHint=true (safe read operation) and openWorldHint=true (can query arbitrary systems). The description adds that it uses the ESI API, which is useful context about the data source. However, it doesn't disclose rate limits, authentication needs, or error behavior beyond what annotations provide. No contradiction with annotations exists.

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 ('Convert EVE Online solar system names to their corresponding IDs') and adds necessary context ('using ESI API'). Every word earns its place with zero redundancy or fluff.

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?

Given the tool's low complexity (single parameter, read-only operation), rich annotations (readOnlyHint, openWorldHint), and 100% schema coverage, the description is reasonably complete. However, the lack of an output schema means the description doesn't explain return values (e.g., format of ID mapping), leaving a minor gap. It adequately covers the core functionality but could mention output expectations.

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 schema fully documenting the 'systemNames' parameter (array of strings, max 500 items, English proper nouns). The description doesn't add any parameter details beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without extra value.

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 EVE Online solar system names to their corresponding IDs') and the resource involved ('using ESI API'). It distinguishes from siblings like 'region_name_to_id', 'station_name_to_id', and 'universal_name_to_id' by specifying it's for solar systems only, not other entity types.

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 (when you have solar system names and need IDs), but doesn't explicitly state when to use this vs. alternatives like 'solar_system_info' (which might provide more details) or 'universal_name_to_id' (which handles multiple entity types). It provides clear scope (solar systems only) but no explicit exclusions or named alternatives.

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