Skip to main content
Glama
kongyo2

EVE Tycoon MCP Server

get_market_history

Read-only

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

Instructions

Returns the price history of an item in a particular region

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionIdYesRegion ID
typeIdYesItem type ID

Implementation Reference

  • The execute handler for the get_market_history tool, which constructs the EVE Tycoon API endpoint for market history using the provided regionId and typeId, fetches the data via makeApiRequest, and returns it as a formatted JSON string.
    execute: async (args) => {
      const endpoint = `/v1/market/history/${args.regionId}/${args.typeId}`;
      const data = await makeApiRequest(endpoint);
      return JSON.stringify(data, null, 2);
    },
  • Zod input schema defining the required parameters: regionId (number) and typeId (number) for the get_market_history tool.
    parameters: z.object({
      regionId: z.number().describe("Region ID"),
      typeId: z.number().describe("Item type ID"),
    }),
  • src/server.ts:97-114 (registration)
    Full registration of the 'get_market_history' tool using FastMCP's server.addTool method, including annotations, description, inline handler, name, and parameters schema.
    server.addTool({
      annotations: {
        openWorldHint: true,
        readOnlyHint: true,
        title: "Get Market History",
      },
      description: "Returns the price history of an item in a particular region",
      execute: async (args) => {
        const endpoint = `/v1/market/history/${args.regionId}/${args.typeId}`;
        const data = await makeApiRequest(endpoint);
        return JSON.stringify(data, null, 2);
      },
      name: "get_market_history",
      parameters: z.object({
        regionId: z.number().describe("Region ID"),
        typeId: z.number().describe("Item type ID"),
      }),
    });
  • Shared utility function used by the tool handler to perform HTTP GET requests to the EVE Tycoon API (https://evetycoon.com/api), handling errors and returning parsed JSON.
    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 already declare readOnlyHint=true and openWorldHint=true, indicating this is a safe read operation with potentially open-ended data. The description adds the specific behavioral context of returning 'price history', which implies time-series data, but doesn't disclose details like date ranges, pagination, or rate limits. With annotations covering core traits, this adds some value but not rich behavioral context.

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 any wasted words. It's appropriately sized for a simple tool with good annotations and schema coverage.

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 (2 required parameters, no output schema), the description is minimally adequate. It covers the basic purpose but lacks usage guidelines and detailed behavioral context. With annotations providing safety and openness hints, it's complete enough for basic use but could be improved with more 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 both parameters (regionId and typeId) documented in the schema. The description implies these parameters are used to specify the item and region for price history, but doesn't add syntax or format details beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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 the resource 'price history of an item in a particular region', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like get_market_stats or get_market_orders, which might also provide market-related data.

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 when to choose this over siblings like get_market_stats (which might provide aggregated statistics) or get_market_orders (which might show current orders), leaving the agent without contextual usage cues.

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