Skip to main content
Glama
kongyo2

eve-online-mcp

get-market-stats

Retrieve real-time market statistics for a specified region in EVE Online using region ID. Access data via ESI API for accurate market insights and analysis.

Instructions

Get market statistics for a region

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
region_idYesRegion ID to get statistics from

Implementation Reference

  • The handler function that executes the tool logic: fetches market statistics from the EVE ESI API endpoint `/markets/${region_id}/stats/` using the makeESIRequest helper and returns a text content block with JSON-stringified stats.
    async ({ region_id }) => {
      const stats = await makeESIRequest<MarketStat[]>(
        `/markets/${region_id}/stats/`
      );
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(stats, null, 2)
          }
        ]
      };
    }
  • Zod input schema defining the required 'region_id' parameter for the tool.
    {
      region_id: z.number().describe("Region ID to get statistics from"),
    },
  • src/index.ts:417-437 (registration)
    Registration of the 'get-market-stats' tool with server.tool(), including description, input schema, and inline handler.
    server.tool(
      "get-market-stats",
      "Get market statistics for a region",
      {
        region_id: z.number().describe("Region ID to get statistics from"),
      },
      async ({ region_id }) => {
        const stats = await makeESIRequest<MarketStat[]>(
          `/markets/${region_id}/stats/`
        );
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(stats, null, 2)
            }
          ]
        };
      }
    );
  • TypeScript interface defining the structure of individual market stat entries (name-value pairs) used for typing the API response in the handler.
    interface MarketStat {
      name: string;
      value: number;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Get') but doesn't describe whether this is a read-only operation, requires authentication, has rate limits, returns paginated data, or what the output format might be. This leaves significant gaps for a tool that likely queries market data.

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 with zero waste. It's appropriately sized for a simple tool and front-loaded with the core purpose, making it easy to parse quickly.

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

Completeness2/5

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

Given the complexity of market data tools, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'market statistics' includes, how results are structured, or behavioral traits like authentication needs. This leaves the agent under-informed for effective use.

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?

The schema description coverage is 100%, with the parameter 'region_id' documented as 'Region ID to get statistics from'. The description adds no additional meaning beyond this, such as examples of valid region IDs or how they relate to market data. Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Get market statistics for a region' clearly states the verb ('Get') and resource ('market statistics'), but it's vague about what 'market statistics' entails compared to siblings like get-market-prices or get-market-history. It doesn't specify what type of statistics (e.g., aggregates, trends, summaries) are returned, leaving ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives like get-market-prices or get-market-history. The description doesn't mention prerequisites (e.g., authentication), exclusions, or contextual cues, leaving the agent to infer usage based on tool names alone.

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-mcp'

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