Skip to main content
Glama
kongyo2

EVE University Wiki MCP Server

get_eve_wiki_summary

Read-only

Retrieve concise summaries of EVE University Wiki articles, with automatic fallback to Wayback Machine for uninterrupted access to EVE Online knowledge.

Instructions

Get a summary of an EVE University Wiki article (with Wayback Machine fallback)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the EVE University Wiki article

Implementation Reference

  • The tool handler function that executes the tool logic by calling eveWikiClient.getSummary and formatting the JSON response with source detection.
    execute: async (args) => {
      try {
        const summary = await eveWikiClient.getSummary(args.title);
        const isArchived = summary.includes("(Retrieved from archived version)");
        
        return JSON.stringify(
          {
            summary: summary,
            title: args.title,
            source: isArchived ? "wayback_machine" : "live_wiki",
          },
          null,
          2,
        );
      } catch (error) {
        return `Error getting summary: ${error}`;
      }
    },
  • Zod input schema defining the 'title' parameter for the tool.
    parameters: z.object({
      title: z.string().describe("Title of the EVE University Wiki article"),
    }),
  • src/server.ts:88-117 (registration)
    Registration of the 'get_eve_wiki_summary' tool using FastMCP server.addTool, including annotations, description, name, handler, and parameters.
    server.addTool({
      annotations: {
        openWorldHint: true,
        readOnlyHint: true,
        title: "Get EVE University Wiki Summary",
      },
      description: "Get a summary of an EVE University Wiki article (with Wayback Machine fallback)",
      execute: async (args) => {
        try {
          const summary = await eveWikiClient.getSummary(args.title);
          const isArchived = summary.includes("(Retrieved from archived version)");
          
          return JSON.stringify(
            {
              summary: summary,
              title: args.title,
              source: isArchived ? "wayback_machine" : "live_wiki",
            },
            null,
            2,
          );
        } catch (error) {
          return `Error getting summary: ${error}`;
        }
      },
      name: "get_eve_wiki_summary",
      parameters: z.object({
        title: z.string().describe("Title of the EVE University Wiki article"),
      }),
    });
  • Core implementation of summary retrieval using MediaWiki extracts API with retry logic and Wayback Machine fallback for archived content.
    async getSummary(title: string): Promise<string> {
      return this.retryableRequest(async () => {
        try {
          const response = await this.client.get("", {
            params: {
              action: "query",
              exintro: true,
              explaintext: true,
              exsectionformat: "plain",
              format: "json",
              prop: "extracts",
              titles: title,
            },
          });
    
          const pages = response.data?.query?.pages;
          if (!pages) {
            throw new Error("No pages found");
          }
    
          const pageId = Object.keys(pages)[0];
          const page = pages[pageId];
    
          if (page.missing) {
            throw new Error(`Article "${title}" not found`);
          }
    
          return page.extract || "No summary available";
        } catch (error) {
          console.error("Primary EVE Wiki summary request failed, trying Wayback Machine fallback:", error);
          
          // Try Wayback Machine fallback
          try {
            const articleUrl = `https://wiki.eveuniversity.org/wiki/${encodeURIComponent(title.replace(/ /g, '_'))}`;
            const waybackContent = await this.getWaybackContent(articleUrl);
            const textContent = this.extractTextFromHtml(waybackContent);
            
            // Extract first paragraph as summary
            const paragraphs = textContent.split('\n\n').filter(p => p.trim().length > 0);
            const summary = paragraphs[0] || textContent.substring(0, 500);
            
            return `${summary} (Retrieved from archived version)`;
          } catch (waybackError) {
            console.error("Wayback Machine fallback also failed:", waybackError);
            throw new Error(`Failed to get summary for "${title}" from both primary source and Wayback Machine`);
          }
        }
      });
    }
Behavior4/5

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

Annotations provide readOnlyHint=true and openWorldHint=true, indicating safe read operations and potential unknown inputs. The description adds valuable context by mentioning the 'Wayback Machine fallback', which is not covered by annotations and informs about reliability and data retrieval behavior beyond basic hints.

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, efficient sentence that front-loads the core purpose and includes the fallback detail without unnecessary words. Every part of the sentence contributes directly to understanding the tool's function.

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

Completeness4/5

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

Given the tool's low complexity (one parameter, read-only, open-world) and lack of output schema, the description is reasonably complete. It covers the main action and fallback mechanism, though it could benefit from more detail on output format or error handling to be fully comprehensive.

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 'title' parameter clearly documented. The description does not add any additional meaning or details about the parameter beyond what the schema provides, so it meets the baseline for high schema coverage without extra value.

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 action ('Get a summary') and resource ('EVE University Wiki article'), and distinguishes it from siblings by specifying the fallback mechanism ('with Wayback Machine fallback'). This is specific and differentiates it from tools like 'get_eve_wiki_article' or 'search_eve_wiki'.

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 for retrieving summaries rather than full articles or other data, but does not explicitly state when to use this tool versus alternatives like 'get_eve_wiki_article' or 'search_eve_wiki'. No exclusions or clear alternatives are named, leaving some ambiguity.

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-University-Wiki-MCP-Server'

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