eve-online-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-market-pricesB | Get market prices for all items in EVE Online |
| get-market-ordersC | Get market orders from a specific region |
| get-market-historyC | Get market history for a specific item in a region |
| get-market-groupsC | Get grouped market data for a region and type |
| get-structure-ordersC | Get all market orders in a structure |
| get-market-statsC | Get market statistics for a region |
| get-structure-type-ordersC | Get all market orders for a specific type in a structure |
| get-auth-urlC | Get the authentication URL for EVE Online SSO |
| authenticateC | Exchange authorization code for access token |
| refresh-tokenB | Refresh an expired access token |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools have distinct purposes, with clear separation between authentication (authenticate, get-auth-url, refresh-token) and market data retrieval functions. However, get-market-orders and get-structure-orders could potentially be confused as they both retrieve market orders, differing only by location (region vs. structure), which might cause misselection if the agent doesn't carefully parse the descriptions.
All tools follow a consistent verb_noun pattern with clear, descriptive names. The naming convention is uniform throughout, using lowercase with hyphens, and verbs like 'get', 'authenticate', and 'refresh' are applied predictably across related functions.
With 10 tools, the count is well-scoped for the server's purpose of handling EVE Online authentication and market data. Each tool serves a specific function, such as authentication flow management and various market queries, making the set comprehensive without being overwhelming.
The tool surface is nearly complete for the domain of EVE Online market data and authentication, covering authentication lifecycle (get URL, authenticate, refresh) and diverse market queries (groups, history, orders, prices, stats). A minor gap exists in the lack of tools for placing or managing market orders, which could limit full market interaction, but core retrieval and authentication are well-covered.