Skip to main content
Glama
kongyo2

EVE Tycoon MCP Server

get_market_orders

Read-only

Retrieve current market order books for EVE Online items with filtering by region, system, or location to analyze trading opportunities.

Instructions

Returns the current order book for an item type, with metadata about the type and locations

Input Schema

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

Implementation Reference

  • The execute handler function constructs the API endpoint based on typeId and optional filters (regionId, systemId, locationId), fetches data from evetycoon.com API using makeApiRequest, and returns JSON string.
    execute: async (args) => {
      let endpoint = `/v1/market/orders/${args.typeId}`;
      const params = new URLSearchParams();
      
      if (args.regionId) {
        params.append('regionId', args.regionId.toString());
      }
      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 for input parameters: required typeId, optional regionId, systemId, locationId.
    parameters: z.object({
      typeId: z.number().describe("Item type ID"),
      regionId: z.number().optional().describe("Region ID to filter on"),
      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:59-94 (registration)
    Registers the 'get_market_orders' tool with FastMCP server, including annotations, description, execute handler, name, and parameters schema.
    server.addTool({
      annotations: {
        openWorldHint: true,
        readOnlyHint: true,
        title: "Get Market Orders",
      },
      description: "Returns the current order book for an item type, with metadata about the type and locations",
      execute: async (args) => {
        let endpoint = `/v1/market/orders/${args.typeId}`;
        const params = new URLSearchParams();
        
        if (args.regionId) {
          params.append('regionId', args.regionId.toString());
        }
        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_orders",
      parameters: z.object({
        typeId: z.number().describe("Item type ID"),
        regionId: z.number().optional().describe("Region ID to filter on"),
        systemId: z.number().optional().describe("System ID to filter on"),
        locationId: z.number().optional().describe("Location ID (station, structure) to filter on"),
      }),
    });
  • Shared helper function used by get_market_orders (and other tools) to perform fetch requests to the EVE Tycoon API.
    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 provide readOnlyHint=true and openWorldHint=true, indicating a safe read operation with potentially large data sets. The description adds value by specifying it returns 'current order book' and 'metadata about the type and locations,' which clarifies the scope beyond annotations. However, it lacks details on rate limits, pagination, or data freshness, which would enhance behavioral understanding. No contradiction with annotations is present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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. It avoids redundancy and waste, making it easy to parse. However, it could be slightly more structured by explicitly separating the main function from filtering details, but overall it is concise and well-formed.

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), the description is adequate but incomplete. It covers what the tool does and filtering options, but lacks details on output format, error handling, or usage examples. With annotations providing safety hints, it meets minimum viability, but could be more comprehensive to fully guide an agent in invocation and interpretation.

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 clear descriptions for all four parameters (typeId, regionId, systemId, locationId). The description adds minimal semantics by implying these are used for filtering ('to filter on'), but does not provide additional context like format examples or interdependencies. Since the schema already documents parameters well, the baseline score of 3 is appropriate as the description adds little extra value.

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: 'Returns the current order book for an item type, with metadata about the type and locations.' It specifies the verb ('Returns') and resource ('current order book for an item type'), making the function understandable. However, it does not explicitly differentiate from sibling tools like 'get_market_history' or 'get_market_stats', which likely provide different market data, so it misses full sibling distinction.

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 mentions filtering by region, system, or location but does not specify when to choose this over siblings like 'get_market_history' (for historical data) or 'get_market_stats' (for statistical summaries). Without such context, users may struggle to select the appropriate tool for their needs.

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