Skip to main content
Glama
kongyo2

eve-online-mcp

get-structure-type-orders

Retrieve market orders for a specific item type within a structure using structure ID and type ID. Ideal for accessing real-time market data in EVE Online via ESI API integration.

Instructions

Get all market orders for a specific type in a structure

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoWhich page to query, starts at 1
structure_idYesStructure ID to get market orders from
type_idYesItem type ID to get orders for

Implementation Reference

  • The handler function that constructs the ESI endpoint for structure market orders by type ID, fetches the orders using makeESIRequest, formats them by selecting key fields, and returns them as JSON text content.
    async ({ structure_id, type_id, page }) => {
      const endpoint = `/markets/structures/${structure_id}/types/${type_id}/${page ? `?page=${page}` : ''}`;
      const orders = await makeESIRequest<MarketOrder[]>(endpoint);
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(orders.map(order => ({
              order_id: order.order_id,
              price: order.price,
              volume_remain: order.volume_remain,
              volume_total: order.volume_total,
              is_buy_order: order.is_buy_order,
              duration: order.duration,
              issued: order.issued,
              range: order.range
            })), null, 2)
          }
        ]
      };
    }
  • Zod input schema defining parameters: structure_id (required number), type_id (required number), page (optional number).
    {
      structure_id: z.number().describe("Structure ID to get market orders from"),
      type_id: z.number().describe("Item type ID to get orders for"),
      page: z.number().optional().describe("Which page to query, starts at 1"),
    },
  • src/index.ts:440-470 (registration)
    The server.tool call that registers the 'get-structure-type-orders' tool with name, description, input schema, and inline handler function.
    server.tool(
      "get-structure-type-orders",
      "Get all market orders for a specific type in a structure",
      {
        structure_id: z.number().describe("Structure ID to get market orders from"),
        type_id: z.number().describe("Item type ID to get orders for"),
        page: z.number().optional().describe("Which page to query, starts at 1"),
      },
      async ({ structure_id, type_id, page }) => {
        const endpoint = `/markets/structures/${structure_id}/types/${type_id}/${page ? `?page=${page}` : ''}`;
        const orders = await makeESIRequest<MarketOrder[]>(endpoint);
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(orders.map(order => ({
                order_id: order.order_id,
                price: order.price,
                volume_remain: order.volume_remain,
                volume_total: order.volume_total,
                is_buy_order: order.is_buy_order,
                duration: order.duration,
                issued: order.issued,
                range: order.range
              })), null, 2)
            }
          ]
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'Get all market orders' but doesn't clarify whether this is a read-only operation, if it requires authentication, what pagination behavior exists (implied by 'page' parameter but not explained), or rate limits. The description is minimal and lacks essential operational 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 directly states the tool's purpose without any fluff. It's appropriately sized for a simple retrieval tool and front-loads the core functionality.

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?

For a tool with 3 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'market orders' means in this context, what format the results take, how pagination works, or authentication requirements. The description alone leaves significant gaps for an agent to understand how to properly use this tool.

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 all parameters are documented in the schema. The description adds no additional meaning about parameters beyond implying that 'structure_id' and 'type_id' are required (which is already in the schema's required array). It doesn't explain relationships between parameters or provide usage examples.

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 action ('Get all market orders') and the target ('for a specific type in a structure'), which is a specific verb+resource combination. It distinguishes itself from sibling tools like 'get-structure-orders' by specifying 'type' filtering, but doesn't explicitly contrast with 'get-market-orders' which might be broader in scope.

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 like 'get-structure-orders' (which presumably gets all orders in a structure) or 'get-market-orders' (which might be global). It states what it does but offers no context about prerequisites, exclusions, or comparative use cases.

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