Skip to main content
Glama
kongyo2

eve-online-mcp

get-auth-url

Generate the authentication URL for EVE Online SSO using the OAuth2 flow. Provide the state parameter to initiate secure authorization for accessing EVE Online market data.

Instructions

Get the authentication URL for EVE Online SSO

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYesState parameter for OAuth2 flow

Implementation Reference

  • Handler function for the 'get-auth-url' tool. It takes a state parameter, calls generateAuthUrl to create the SSO authorization URL, and returns it as text content.
    async ({ state }) => {
      const authUrl = generateAuthUrl(state);
      return {
        content: [
          {
            type: "text",
            text: authUrl
          }
        ]
      };
    }
  • Zod input schema for the tool, defining the required 'state' string parameter.
    {
      state: z.string().describe("State parameter for OAuth2 flow")
    },
  • src/index.ts:473-490 (registration)
    Registration of the 'get-auth-url' tool using server.tool(), including name, description, schema, and handler.
    server.tool(
      "get-auth-url",
      "Get the authentication URL for EVE Online SSO",
      {
        state: z.string().describe("State parameter for OAuth2 flow")
      },
      async ({ state }) => {
        const authUrl = generateAuthUrl(state);
        return {
          content: [
            {
              type: "text",
              text: authUrl
            }
          ]
        };
      }
    );
  • Helper function that generates the EVE Online SSO authorization URL using client config and provided state.
    function generateAuthUrl(state: string): string {
      const scopes = [
        "esi-markets.structure_markets.v1",
        "esi-markets.read_character_orders.v1"
      ].join(" ");
    
      const params = new URLSearchParams({
        response_type: "code",
        redirect_uri: EVE_CALLBACK_URL,
        client_id: EVE_CLIENT_ID,
        scope: scopes,
        state: state
      });
    
      return `https://login.eveonline.com/v2/oauth/authorize?${params.toString()}`;
    }
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 of behavioral disclosure. It states the tool retrieves an authentication URL but doesn't describe what the URL is used for (e.g., redirecting users), whether it's safe to call repeatedly, or any side effects. This leaves gaps in understanding the tool's behavior beyond its basic purpose.

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, clear sentence with no wasted words. It's appropriately sized for a simple tool and front-loads the essential information. Every part of the sentence contributes directly to understanding the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of authentication tools and the lack of annotations and output schema, the description is insufficient. It doesn't explain what the returned URL is used for, how it fits into the OAuth2 flow, or what happens after obtaining it. For a tool with no structured behavioral data, more context is needed to guide effective use.

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?

The input schema has 100% description coverage, with the 'state' parameter documented as 'State parameter for OAuth2 flow.' The description adds no additional parameter information beyond what the schema provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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's purpose: 'Get the authentication URL for EVE Online SSO.' It specifies the verb ('Get') and resource ('authentication URL'), and identifies the target system ('EVE Online SSO'). However, it doesn't explicitly differentiate from sibling tools like 'authenticate' or 'refresh-token', which might handle different aspects of authentication flow.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., initiating OAuth2 flow), or exclusions. Sibling tools like 'authenticate' and 'refresh-token' suggest related authentication functions, but the description offers no comparison or usage scenarios.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kongyo2/eve-online-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server