EVE Online Companion MCP Server

Overview Schema Source Related Servers Discussions Admin

eve_auth_login

Access the EVE Online Companion dashboard to manage multiple game characters and accounts for real-time game data interaction.

Instructions

Open the EVE MCP multi-character dashboard. Add, switch, or remove characters. Multiple accounts and characters supported simultaneously.

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": "eve_auth_login"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 16, 2026

TDQS

A4.1/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 full burden. It discloses behavioral traits like opening a dashboard and supporting multiple accounts/characters, but lacks details on permissions, rate limits, or what the dashboard interaction entails (e.g., UI-based vs. programmatic).

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 front-loaded with the main action ('Open the EVE MCP multi-character dashboard') and efficiently adds supporting details in two sentences, with no wasted words or redundant information.

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?

Given no annotations, no output schema, and low complexity (0 parameters), the description is somewhat complete but could benefit from more behavioral context (e.g., how the dashboard works, any side effects). It adequately covers the purpose but leaves gaps in operational details.

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 tool has 0 parameters with 100% schema description coverage, so no parameter information is needed. The description does not add parameter semantics, but this is acceptable given the baseline for zero parameters is 4, as it adequately describes the tool's action without parameter details.

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's purpose with specific verbs ('Open', 'Add, switch, or remove') and resources ('EVE MCP multi-character dashboard', 'characters'), distinguishing it from sibling tools like eve_auth_list_characters or eve_auth_remove_character by indicating it opens a dashboard for managing multiple characters rather than performing isolated actions.

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 clear context for when to use this tool ('Add, switch, or remove characters', 'Multiple accounts and characters supported simultaneously'), but does not explicitly state when not to use it or name alternatives among siblings, such as using eve_auth_remove_character for removal only.

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