Skip to main content
Glama
kongyo2

EVE Tycoon MCP Server

get_market_groups

Read-only

Retrieve all market groups from the EVE Tycoon API to categorize and organize EVE Online items for market analysis and trading decisions.

Instructions

Returns the list of all market groups

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Inline handler function for the get_market_groups tool. Fetches the list of market groups from the EVE Tycoon API endpoint and returns the JSON stringified data.
    execute: async () => {
      const data = await makeApiRequest("/v1/market/groups");
      return JSON.stringify(data, null, 2);
    },
  • Zod schema defining the input parameters for get_market_groups tool: no required parameters.
    parameters: z.object({}),
  • src/server.ts:133-146 (registration)
    Registration of the get_market_groups tool using FastMCP's server.addTool method, including annotations, description, name, handler, and schema.
    server.addTool({
      annotations: {
        openWorldHint: true,
        readOnlyHint: true,
        title: "Get Market Groups",
      },
      description: "Returns the list of all market groups",
      execute: async () => {
        const data = await makeApiRequest("/v1/market/groups");
        return JSON.stringify(data, null, 2);
      },
      name: "get_market_groups",
      parameters: z.object({}),
    });
  • Utility helper function used by get_market_groups (and other tools) to perform HTTP requests to the EVE Tycoon API base URL.
    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 incomplete data. The description adds no behavioral context beyond this, such as rate limits, authentication needs, or data freshness. It doesn't contradict annotations, but adds minimal value beyond them.

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 front-loaded with the core action and resource, making it immediately clear. Every word earns its place, and there's no redundancy or unnecessary elaboration.

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 read-only tool with no parameters and good annotations, the description is adequate but minimal. It lacks output details (no schema provided), doesn't explain data format or scope limitations, and misses sibling differentiation. It's complete enough for basic use but leaves gaps in contextual understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to explain parameters, and it correctly implies no filtering or options are available. This meets expectations for a parameterless tool.

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 ('list of all market groups'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_market_group_types' or 'get_market_stats', which likely return different market-related data. The description is specific but lacks 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. With siblings like 'get_market_group_types' and 'get_market_stats', there's no indication of what distinguishes this tool's scope or when it's appropriate. The description only states what it does, not when to choose it.

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