eve-sde-mcp

get_market_group

Navigate the Eve Online market group tree to get group info and children (subgroups or types). Omit market group ID for top-level groups.

Instructions

Navigate the Eve Online market group tree. Returns group info and children (subgroups or types).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_market_group"
  }
}

Input Schema

Name	Required	Description	Default
`market_group_id`	No	marketGroupID. Omit to get top-level market groups.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 19, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It states the output (group info and children) but lacks details on authentication, rate limits, or any side effects. It does not contradict annotations (none provided), but is minimal.

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, front-loaded sentence with no unnecessary words. Every part is informative.

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 tool with one optional parameter and no output schema, the description covers inputs and general output. However, it lacks details on the response structure (e.g., whether children are IDs or objects). Adequate but not fully complete.

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 schema covers the parameter 100%, and the description adds valuable context: omitting the parameter returns top-level groups. This enhances understanding beyond the schema alone.

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 navigates the market group tree and returns group info and children, distinguishing it from sibling tools like get_group or get_category. The verb 'Navigate' is slightly vague, but the resource and output are well-defined.

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

Usage Guidelines3/5

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

The description implies usage for exploring market hierarchy, and the parameter description adds guidance on omitting the ID for top-level groups. However, it does not explicitly state when to use this tool versus alternatives like get_group.

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

Deploy Server