Skip to main content
Glama
kongyo2

EVE University Wiki MCP Server

get_eve_wiki_related_topics

Read-only

Retrieve related topics for an EVE University Wiki article using its categories. Specify the article title and limit results to explore relevant content efficiently.

Instructions

Get topics related to an EVE University Wiki article based on categories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of related topics to return
titleYesTitle of the EVE University Wiki article

Implementation Reference

  • src/server.ts:177-214 (registration)
    Registration of the 'get_eve_wiki_related_topics' MCP tool, including annotations, description, input schema, output formatting, and handler function that delegates to EveWikiClient.getRelatedTopics.
    // Get related topics from EVE University Wiki
    server.addTool({
      annotations: {
        openWorldHint: true,
        readOnlyHint: true,
        title: "Get Related EVE University Wiki Topics",
      },
      description:
        "Get topics related to an EVE University Wiki article based on categories",
      execute: async (args) => {
        try {
          const relatedTopics = await eveWikiClient.getRelatedTopics(
            args.title,
            args.limit,
          );
          return JSON.stringify(
            {
              related_topics: relatedTopics,
              title: args.title,
            },
            null,
            2,
          );
        } catch (error) {
          return `Error getting related topics: ${error}`;
        }
      },
      name: "get_eve_wiki_related_topics",
      parameters: z.object({
        limit: z
          .number()
          .min(1)
          .max(20)
          .default(10)
          .describe("Maximum number of related topics to return"),
        title: z.string().describe("Title of the EVE University Wiki article"),
      }),
    });
  • Main handler logic for fetching related topics: retrieves categories of the given wiki article title, then fetches up to 5 member pages from each of the first 3 categories (excluding the original title), collecting up to the specified limit.
    async getRelatedTopics(title: string, limit: number = 10): Promise<string[]> {
      return this.retryableRequest(async () => {
        try {
          // First get categories for the article
          const categoriesResponse = await this.client.get("", {
            params: {
              action: "query",
              cllimit: 10,
              format: "json",
              prop: "categories",
              titles: title,
            },
          });
    
          const pages = categoriesResponse.data?.query?.pages;
          if (!pages) {
            return [];
          }
    
          const pageId = Object.keys(pages)[0];
          const page = pages[pageId];
    
          if (page.missing || !page.categories) {
            return [];
          }
    
          // Get articles from the same categories
          const categories = page.categories.slice(0, 3); // Limit to first 3 categories
          const relatedArticles: Set<string> = new Set();
    
          for (const category of categories) {
            try {
              const categoryResponse = await this.client.get("", {
                params: {
                  action: "query",
                  cmlimit: 5,
                  cmtitle: category.title,
                  cmtype: "page",
                  format: "json",
                  list: "categorymembers",
                },
              });
    
              if (categoryResponse.data?.query?.categorymembers) {
                categoryResponse.data.query.categorymembers.forEach(
                  (member: { title: string }) => {
                    if (member.title !== title && relatedArticles.size < limit) {
                      relatedArticles.add(member.title);
                    }
                  },
                );
              }
            } catch (error) {
              console.warn(
                `Error getting category members for ${category.title}:`,
                error,
              );
            }
          }
    
          return Array.from(relatedArticles);
        } catch (error) {
          console.error("Error getting related topics:", error);
          throw new Error(`Failed to get related topics for "${title}": ${error}`);
        }
      });
    }
  • Input schema validation using Zod: requires 'title' string and optional 'limit' number (1-20, default 10).
    parameters: z.object({
      limit: z
        .number()
        .min(1)
        .max(20)
        .default(10)
        .describe("Maximum number of related topics to return"),
      title: z.string().describe("Title of the EVE University Wiki article"),
    }),
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe read operations with potentially incomplete results. The description adds valuable context about the relationship mechanism ('based on categories'), which isn't covered by annotations. No contradictions exist, and it provides useful behavioral insight beyond the structured 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, focused sentence that efficiently conveys the tool's purpose without unnecessary words. It's front-loaded with the core functionality and avoids redundancy with the structured fields.

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?

For a read-only tool with good annotations and full schema coverage, the description provides adequate context about the relationship mechanism. However, without an output schema, it doesn't describe the format of returned topics (e.g., whether they include metadata or just titles), leaving a minor gap in completeness.

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 clear documentation for both parameters. The description doesn't add any parameter-specific information beyond what the schema provides (e.g., it doesn't explain category selection or ranking algorithms). Baseline 3 is appropriate when the schema fully documents parameters.

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 topics related to') and resource ('an EVE University Wiki article'), with explicit scope ('based on categories'). It distinguishes from siblings like get_eve_wiki_article (retrieves article content) and get_eve_wiki_links (retrieves hyperlinks) by focusing on category-based topic relationships.

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 when category-based topic relationships are needed, but provides no explicit guidance on when to use this tool versus alternatives like get_eve_wiki_links (which might retrieve different relationship types) or search_eve_wiki (which searches content). No exclusions or prerequisites are mentioned.

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