eve-sde-mcp

search_blueprints

Find blueprints that produce a specific item in Eve Online. Enter a product name to discover which blueprint manufactures it.

Instructions

Search for Eve Online blueprints by product name. Find what blueprint makes a given item.

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": {
      "product_name": "<product_name>"
    },
    "name": "search_blueprints"
  }
}

Input Schema

Name	Required	Description	Default
`product_name`	Yes	Name of the product to find blueprints for
`limit`	No	Max results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 19, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states 'Search' and 'Find', which implies a read operation but does not disclose any behavioral traits such as whether the search is case-sensitive, supports partial matches, or has rate limits. The description is too minimal for a tool with no annotations.

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?

Two short sentences with only 15 words, front-loaded with the essential purpose. No redundant information or filler. Every word earns its place.

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 2 parameters and no output schema, the description is mostly adequate but lacks details on what the search returns (e.g., list of blueprint names or IDs), any sorting or pagination behavior, and search semantics like partial matching. It covers the basic purpose but not the full context.

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 descriptions for both parameters: 'product_name' and 'limit'. The description adds 'Find what blueprint makes a given item', reinforcing the purpose but not adding significant new meaning beyond what the schema already provides. Baseline 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 it searches for Eve Online blueprints by product name, specifying the verb 'Search' and the resource 'blueprints'. It distinguishes itself from sibling tools like 'get_blueprint' (single blueprint) and 'search_types' (general types) by focusing on blueprint-finding via product name.

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 when you want to find what blueprint makes an item, but it does not explicitly state when to use this tool versus alternatives like 'search_types' or 'get_type'. No exclusion criteria or when-not-to-use guidance is provided.

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

Deploy Server