Skip to main content
Glama
kongyo2

EVE Tycoon MCP Server

get_market_stats

Read-only

Retrieve price and volume statistics for EVE Online items in specific regions to analyze market trends and make informed trading decisions.

Instructions

Returns price and volume stats for an item type in a specific region

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionIdYesRegion ID
typeIdYesItem type ID
systemIdNoSystem ID to filter on
locationIdNoLocation ID (station, structure) to filter on

Implementation Reference

  • The async execute function that implements the core logic of the get_market_stats tool by constructing an API endpoint based on input parameters and fetching data from the EVE Tycoon API using the makeApiRequest helper.
    execute: async (args) => {
      let endpoint = `/v1/market/stats/${args.regionId}/${args.typeId}`;
      const params = new URLSearchParams();
      
      if (args.systemId) {
        params.append('systemId', args.systemId.toString());
      }
      if (args.locationId) {
        params.append('locationId', args.locationId.toString());
      }
      
      if (params.toString()) {
        endpoint += `?${params.toString()}`;
      }
      
      const data = await makeApiRequest(endpoint);
      return JSON.stringify(data, null, 2);
    },
  • Zod schema defining the input parameters for the get_market_stats tool, including required regionId and typeId, and optional systemId and locationId.
    parameters: z.object({
      regionId: z.number().describe("Region ID"),
      typeId: z.number().describe("Item type ID"),
      systemId: z.number().optional().describe("System ID to filter on"),
      locationId: z.number().optional().describe("Location ID (station, structure) to filter on"),
    }),
  • src/server.ts:24-56 (registration)
    The server.addTool call that registers the get_market_stats tool with FastMCP, including annotations, description, name, parameters schema, and execute handler.
    server.addTool({
      annotations: {
        openWorldHint: true,
        readOnlyHint: true,
        title: "Get Market Stats",
      },
      description: "Returns price and volume stats for an item type in a specific region",
      execute: async (args) => {
        let endpoint = `/v1/market/stats/${args.regionId}/${args.typeId}`;
        const params = new URLSearchParams();
        
        if (args.systemId) {
          params.append('systemId', args.systemId.toString());
        }
        if (args.locationId) {
          params.append('locationId', args.locationId.toString());
        }
        
        if (params.toString()) {
          endpoint += `?${params.toString()}`;
        }
        
        const data = await makeApiRequest(endpoint);
        return JSON.stringify(data, null, 2);
      },
      name: "get_market_stats",
      parameters: z.object({
        regionId: z.number().describe("Region ID"),
        typeId: z.number().describe("Item type ID"),
        systemId: z.number().optional().describe("System ID to filter on"),
        locationId: z.number().optional().describe("Location ID (station, structure) to filter on"),
      }),
    });
  • Reusable helper function used by get_market_stats (and other tools) to perform fetch requests to the EVE Tycoon API endpoints.
    async function makeApiRequest(endpoint: string): Promise<any> {
      const url = `${BASE_URL}${endpoint}`;
      const response = await fetch(url);
      
      if (!response.ok) {
        throw new Error(`API request failed: ${response.status} ${response.statusText}`);
      }
      
      return response.json();
    }
Behavior3/5

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

Annotations indicate readOnlyHint=true and openWorldHint=true, which the description doesn't contradict. The description adds value by specifying the type of data returned ('price and volume stats'), but it doesn't disclose additional behavioral traits like rate limits, authentication needs, or data freshness, which could be useful context beyond the annotations.

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 key action and resource without any wasted words. It's appropriately sized for a simple data retrieval tool, making it easy for an agent to parse quickly.

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?

Given the tool's moderate complexity (4 parameters, no output schema) and rich annotations, the description is adequate but incomplete. It covers the basic purpose but lacks details on output format, error handling, or usage scenarios, which could help the agent invoke it more effectively 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%, so the schema fully documents all parameters. The description adds minimal semantic context by implying that 'regionId' and 'typeId' are required for the core query, but it doesn't provide extra details beyond what the schema already specifies, such as how 'systemId' or 'locationId' refine the results.

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 verb ('Returns') and resource ('price and volume stats for an item type in a specific region'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_market_history' or 'get_market_orders', which might also return market-related data, so it doesn't reach the highest score.

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 or contexts where other tools might be more appropriate, such as using 'get_market_history' for historical data or 'get_market_orders' for order details, leaving the agent with minimal usage direction.

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

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/evetycoon-mcp-server'

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