eve-sde-mcp

get_type

Retrieve detailed information for any Eve Online item type by its ID, including attributes, effects, and traits.

Instructions

Get full details for an Eve Online type by ID, including all dogma attributes (CPU, powergrid, damage, resistances, etc.), effects, traits, and meta info.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type_id": "<type_id>"
    },
    "name": "get_type"
  }
}

Input Schema

Name	Required	Description	Default
`type_id`	Yes	The typeID to look up

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 19, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It lists returned data categories but does not disclose error behavior (e.g., invalid type_id), authentication requirements, or response format. For a read-only lookup, this is adequate but not comprehensive.

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 sentence listing key details, which is efficient. However, it could be split into two sentences for readability, slightly reducing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple single-parameter tool and sibling tools that cover subsets, the description provides sufficient information about what the tool returns. It lacks details on authentication or potential errors, but for a basic lookup, completeness is good.

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 coverage is 100% with one parameter (type_id) described as 'The typeID to look up'. The tool description adds 'by ID' but does not provide additional context beyond the schema. Baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves full details for an Eve Online type by ID, listing specific data categories (dogma attributes, effects, traits, meta info). It distinguishes from sibling tools like get_type_attributes and get_type_effects, which focus on subsets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when full type details are needed and provides a clear action ('Get full details... by ID'). However, it lacks explicit guidance on when to use alternatives like get_type_attributes or get_type_effects, and does not mention prerequisites or context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server