Skip to main content
Glama
kongyo2

EVE University Wiki MCP Server

get_eve_wiki_article

Read-only

Retrieve full EVE University Wiki article content by title, with Wayback Machine fallback for reliable access to EVE Online knowledge.

Instructions

Get the full content of an EVE University Wiki article (with Wayback Machine fallback)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the EVE University Wiki article

Implementation Reference

  • src/server.ts:53-85 (registration)
    Registers the 'get_eve_wiki_article' tool using server.addTool, including name, description, input schema, and inline handler function.
    server.addTool({
      annotations: {
        openWorldHint: true,
        readOnlyHint: true,
        title: "Get EVE University Wiki Article",
      },
      description: "Get the full content of an EVE University Wiki article (with Wayback Machine fallback)",
      execute: async (args) => {
        try {
          const article = await eveWikiClient.getArticle(args.title);
          const isArchived = article.pageid === -1;
          
          return JSON.stringify(
            {
              content: article.content, // Full content without limit
              pageid: article.pageid,
              timestamp: article.timestamp,
              title: article.title,
              source: isArchived ? "wayback_machine" : "live_wiki",
              note: isArchived ? "Content retrieved from Internet Archive Wayback Machine" : undefined,
            },
            null,
            2,
          );
        } catch (error) {
          return `Error getting article: ${error}`;
        }
      },
      name: "get_eve_wiki_article",
      parameters: z.object({
        title: z.string().describe("Title of the EVE University Wiki article"),
      }),
    });
  • The tool's execute handler: fetches article via EveWikiClient, determines source (live or archived), formats and returns JSON response.
    execute: async (args) => {
      try {
        const article = await eveWikiClient.getArticle(args.title);
        const isArchived = article.pageid === -1;
        
        return JSON.stringify(
          {
            content: article.content, // Full content without limit
            pageid: article.pageid,
            timestamp: article.timestamp,
            title: article.title,
            source: isArchived ? "wayback_machine" : "live_wiki",
            note: isArchived ? "Content retrieved from Internet Archive Wayback Machine" : undefined,
          },
          null,
          2,
        );
      } catch (error) {
        return `Error getting article: ${error}`;
      }
    },
  • Zod input schema defining the 'title' parameter.
    parameters: z.object({
      title: z.string().describe("Title of the EVE University Wiki article"),
    }),
  • Core implementation in EveWikiClient.getArticle: queries MediaWiki API for article content, falls back to Wayback Machine HTML scraping if unavailable.
    async getArticle(title: string): Promise<Article> {
      return this.retryableRequest(async () => {
        try {
          const response = await this.client.get("", {
            params: {
              action: "query",
              format: "json",
              prop: "revisions",
              rvprop: "content|timestamp|ids",
              rvslots: "main",
              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`);
          }
    
          const revision = page.revisions?.[0];
          if (!revision) {
            throw new Error("No revision found");
          }
    
          return {
            content: revision.slots?.main?.["*"] || "",
            pageid: page.pageid,
            revid: revision.revid,
            timestamp: revision.timestamp,
            title: page.title,
          };
        } catch (error) {
          console.error("Primary EVE Wiki 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);
            
            return {
              content: textContent,
              pageid: -1, // Indicate this is from Wayback Machine
              revid: -1,
              timestamp: new Date().toISOString(),
              title: `${title} (Archived)`,
            };
          } catch (waybackError) {
            console.error("Wayback Machine fallback also failed:", waybackError);
            throw new Error(`Failed to get article "${title}" from both primary source and Wayback Machine`);
          }
        }
      });
    }
  • TypeScript interface defining the structure of an Article returned by getArticle.
    export interface Article {
      content: string;
      pageid: number;
      revid: number;
      timestamp: string;
      title: string;
    }
Behavior4/5

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

Annotations provide readOnlyHint=true and openWorldHint=true, indicating a safe read operation with potentially unknown outputs. The description adds valuable context beyond this by mentioning the 'Wayback Machine fallback', which implies resilience behavior not covered by annotations. It does not contradict annotations, as 'Get' aligns with read-only.

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 ('Get the full content') and includes essential context ('with Wayback Machine fallback') without unnecessary words. Every part earns its place, making it highly concise and well-structured.

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 (1 parameter, no output schema) and rich annotations (readOnlyHint, openWorldHint), the description is mostly complete. It covers the purpose and a key behavioral trait (fallback), but lacks details on output format or error handling, which could be useful despite the annotations.

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 description coverage is 100%, with the parameter 'title' clearly documented in the schema. The description does not add any additional meaning or details about the parameter beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 specific action ('Get the full content') and resource ('EVE University Wiki article'), distinguishing it from siblings like get_eve_wiki_summary (which likely provides a summary) and get_eve_wiki_sections (which might list sections). The mention of 'Wayback Machine fallback' adds unique scope, further differentiating it.

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 implies usage context by specifying 'full content' and 'Wayback Machine fallback', suggesting this tool is for retrieving complete articles, possibly when the main source is unavailable. However, it does not explicitly state when to use it versus alternatives like get_eve_wiki_summary or search_eve_wiki, 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