eve-sde-mcp

query_sde

Query the Eve Online SDE database using custom SQL to retrieve ship stats, module attributes, universe data, blueprints, and other information not accessible via other tools.

Instructions

Run a read-only SQL query against the Eve Online SDE database. Only SELECT statements are allowed. Use this for anything the other tools don't cover.

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": {
      "sql": "<sql>"
    },
    "name": "query_sde"
  }
}

Input Schema

Name	Required	Description	Default
`sql`	Yes	SQL SELECT query to execute
`params`	No	Bind parameters for the query

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 19, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool is read-only and only accepts SELECT statements, which are the key behavioral traits. It does not mention potential limits or response details, but the disclosed information is sufficient for a query tool.

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 consists of two sentences, front-loading the action and constraint with no wasted words. Every sentence serves a purpose: stating the operation and providing usage guidance.

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?

The tool has no output schema, so the agent must infer return values. The description does not explain the response format, error handling, or any execution limits. While the tool is relatively simple, the missing output details reduce completeness.

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% (both 'sql' and 'params' are described). The description reinforces the schema by restating 'SQL SELECT query' for the sql parameter. It does not add significant new meaning beyond the schema, so the baseline 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 verb 'Run' and resource 'SQL query against the Eve Online SDE database', with explicit constraints 'read-only' and 'Only SELECT statements'. It also distinguishes from siblings by stating 'Use this for anything the other tools don't cover'.

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 provides explicit usage context: 'Use this for anything the other tools don't cover' and specifies that only SELECT statements are allowed. It lacks explicit when-not scenarios but gives clear guidance for when to use the tool.

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

Deploy Server