Skip to main content
Glama

region_name_to_id

Read-only

Convert EVE Online region names into their corresponding IDs using the ESI API. Input an array of up to 500 region names for accurate ID mapping within the 'eve-online-traffic-mcp' server.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNamesYesArray of region names to convert to IDs (max 500). Use English proper nouns only (e.g., 'The Forge', 'Domain', 'Sinq Laison')

Implementation Reference

  • The execute function that implements the core logic of the region_name_to_id tool. It calls the ESI client to resolve region names to IDs, handles empty results and errors, and returns a formatted JSON response.
    execute: async (args: { regionNames: string[] }) => {
      try {
        const results = await esiClient.getRegionIds(args.regionNames);
        
        if (results.length === 0) {
          return JSON.stringify({
            success: false,
            message: "No regions found with the provided names",
            results: []
          });
        }
    
        return JSON.stringify({
          success: true,
          message: `Found ${results.length} region(s)`,
          results: results.map(region => ({
            id: region.id,
            name: region.name,
            type: "region"
          }))
        });
      } 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 up to 500 region names.
    parameters: z.object({
      regionNames: z.array(z.string()).min(1).max(500).describe("Array of region names to convert to IDs (max 500). Use English proper nouns only (e.g., 'The Forge', 'Domain', 'Sinq Laison')")
    }),
  • src/server.ts:47-47 (registration)
    Registration of the regionNameToIdTool object with the FastMCP server.
    server.addTool(regionNameToIdTool);
  • Supporting helper method in ESIClient that filters region results from the universal namesToIds ESI API call.
    async getRegionIds(regionNames: string[]): Promise<Array<{ id: number; name: string }>> {
      const result = await this.namesToIds(regionNames);
      return result.regions || [];
    }
  • src/server.ts:3-6 (registration)
    Import of the regionNameToIdTool from name-to-id-tools.js for use in server registration.
    solarSystemNameToIdTool,
    stationNameToIdTool,
    regionNameToIdTool,
    universalNameToIdTool
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating a safe read operation with potentially unbounded data. The description adds that it uses the ESI API, which implies external API calls and potential rate limits, but doesn't explicitly mention these behavioral traits. 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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core functionality and includes the API context, making every part of the sentence valuable.

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?

For a simple conversion tool with good annotations (readOnlyHint, openWorldHint) and full schema coverage, the description is minimally adequate. However, it lacks output details (no output schema provided), doesn't mention error handling or API constraints, and doesn't guide usage relative to siblings, leaving gaps in context.

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 'regionNames' fully documented in the schema (array of strings, max 500 items, English proper nouns only). 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.

Purpose4/5

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

The description clearly states the tool's purpose: converting EVE Online region names to IDs using the ESI API. It specifies the verb ('convert'), resource ('region names'), and mechanism ('ESI API'). However, it doesn't explicitly differentiate from sibling tools like 'solar_system_name_to_id' or 'universal_name_to_id', which perform similar conversions for different 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 Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'region_info' (which might provide more detailed region data) or 'universal_name_to_id' (which might handle multiple entity types). There's no context about prerequisites, limitations, or typical use cases beyond the basic conversion.

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