Skip to main content
Glama
kongyo2

EVE University Wiki MCP Server

get_eve_wiki_links

Read-only

Extract all links from an EVE University Wiki article by providing the article title. Access comprehensive EVE Online knowledge with enhanced reliability through automatic Wayback Machine fallback.

Instructions

Get the links contained within an EVE University Wiki article

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the EVE University Wiki article

Implementation Reference

  • The tool handler execute function that fetches links from EVE University Wiki using eveWikiClient and returns them as formatted JSON.
    execute: async (args) => {
      try {
        const links = await eveWikiClient.getLinks(args.title);
        return JSON.stringify(
          {
            links: links, // All links without limit
            title: args.title,
          },
          null,
          2,
        );
      } catch (error) {
        return `Error getting links: ${error}`;
      }
    },
  • Zod schema defining the input parameters for the get_eve_wiki_links tool (requires 'title' string).
    parameters: z.object({
      title: z.string().describe("Title of the EVE University Wiki article"),
    }),
  • src/server.ts:149-175 (registration)
    The complete server.addTool registration for the get_eve_wiki_links tool, including annotations, description, handler, name, and parameters schema.
    server.addTool({
      annotations: {
        openWorldHint: true,
        readOnlyHint: true,
        title: "Get EVE University Wiki Links",
      },
      description: "Get the links contained within an EVE University Wiki article",
      execute: async (args) => {
        try {
          const links = await eveWikiClient.getLinks(args.title);
          return JSON.stringify(
            {
              links: links, // All links without limit
              title: args.title,
            },
            null,
            2,
          );
        } catch (error) {
          return `Error getting links: ${error}`;
        }
      },
      name: "get_eve_wiki_links",
      parameters: z.object({
        title: z.string().describe("Title of the EVE University Wiki article"),
      }),
    });
  • The EveWikiClient.getLinks method that implements the core logic of querying the MediaWiki API for links in the specified article (limited to 500).
    async getLinks(title: string): Promise<string[]> {
      return this.retryableRequest(async () => {
        try {
          const response = await this.client.get("", {
            params: {
              action: "query",
              format: "json",
              pllimit: 500,
              prop: "links",
              titles: title,
            },
          });
    
          const pages = response.data?.query?.pages;
          if (!pages) {
            return [];
          }
    
          const pageId = Object.keys(pages)[0];
          const page = pages[pageId];
    
          if (page.missing || !page.links) {
            return [];
          }
    
          return page.links.map((link: { title: string }) => link.title);
        } catch (error) {
          console.error("Error getting links:", error);
          throw new Error(`Failed to get links for "${title}": ${error}`);
        }
      });
    }
  • Instantiation of the EveWikiClient used by the tool handler.
    const eveWikiClient = new EveWikiClient();
Behavior3/5

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

Annotations indicate readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe, read-only operation with open-world semantics. The description adds context by specifying it retrieves 'links' from an article, which is useful beyond annotations, but doesn't detail behavioral traits like rate limits, error handling, or output format, keeping it at a baseline level.

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 directly states the tool's purpose without any unnecessary words. It is front-loaded and appropriately sized, making it easy for an agent to parse quickly.

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 the tool's low complexity (1 parameter, no output schema) and good annotations, the description is minimally complete. It covers the basic purpose but lacks details on output (e.g., link format or structure) and usage context relative to siblings, which could be helpful for an agent to operate effectively.

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 single parameter 'title' clearly documented in the schema. The description doesn't add any meaning beyond this, such as format examples or constraints, so it meets the baseline score of 3 where the schema handles parameter documentation adequately.

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 verb ('Get') and resource ('links contained within an EVE University Wiki article'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_eve_wiki_article' or 'get_eve_wiki_sections', which might also involve article content, so it's not a perfect 5.

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 such as 'get_eve_wiki_article' or 'get_eve_wiki_related_topics'. It lacks explicit context, exclusions, or named alternatives, leaving the agent to infer usage from tool names alone.

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