Skip to main content
Glama
kongyo2

EVE University Wiki MCP Server

get_eve_wiki_sections

Read-only

Retrieve sections of an EVE University Wiki article by specifying its title, enabling structured access to EVE Online knowledge for AI assistants and users.

Instructions

Get the sections of an EVE University Wiki article

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the EVE University Wiki article

Implementation Reference

  • src/server.ts:120-146 (registration)
    Registers the get_eve_wiki_sections tool with FastMCP server.addTool, including annotations, description, input schema (Zod), and inline execute handler that delegates to eveWikiClient.getSections and formats JSON response.
    server.addTool({
      annotations: {
        openWorldHint: true,
        readOnlyHint: true,
        title: "Get EVE University Wiki Sections",
      },
      description: "Get the sections of an EVE University Wiki article",
      execute: async (args) => {
        try {
          const sections = await eveWikiClient.getSections(args.title);
          return JSON.stringify(
            {
              sections: sections,
              title: args.title,
            },
            null,
            2,
          );
        } catch (error) {
          return `Error getting sections: ${error}`;
        }
      },
      name: "get_eve_wiki_sections",
      parameters: z.object({
        title: z.string().describe("Title of the EVE University Wiki article"),
      }),
    });
  • Implements the core tool logic in EveWikiClient.getSections(): performs API request to MediaWiki parse endpoint to retrieve article sections, maps response to Section objects, with retryableRequest wrapper for reliability.
    async getSections(title: string): Promise<Section[]> {
      return this.retryableRequest(async () => {
        try {
          const response = await this.client.get("", {
            params: {
              action: "parse",
              format: "json",
              page: title,
              prop: "sections",
            },
          });
    
          if (response.data?.parse?.sections) {
            return response.data.parse.sections.map(
              (section: { index: string; level: string; line: string }) => ({
                index: parseInt(section.index) || 0,
                level: parseInt(section.level) || 1,
                title: section.line,
              }),
            );
          }
    
          return [];
        } catch (error) {
          console.error("Error getting sections:", error);
          throw new Error(`Failed to get sections for "${title}": ${error}`);
        }
      });
    }
  • TypeScript interface defining the structure of a wiki Section object used in the tool's output.
    export interface Section {
      content?: string;
      index: number;
      level: number;
      title: string;
    }
  • The tool's execute handler function: calls the helper getSections, formats results as JSON with title, handles errors.
    execute: async (args) => {
      try {
        const sections = await eveWikiClient.getSections(args.title);
        return JSON.stringify(
          {
            sections: sections,
            title: args.title,
          },
          null,
          2,
        );
      } catch (error) {
        return `Error getting sections: ${error}`;
      }
    },
Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, indicating this is a safe read operation with potentially unknown data. The description adds value by specifying it retrieves 'sections' of articles, which clarifies the scope beyond what annotations cover, but it doesn't detail behavioral traits like rate limits, error handling, or output format.

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 that directly states the tool's purpose without any unnecessary words. It is front-loaded and efficiently conveys the essential information, 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.

Completeness3/5

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

Given the tool has one parameter with full schema coverage and annotations covering safety and data scope, the description is adequate for a basic read operation. However, without an output schema, it doesn't explain return values or structure, and it lacks usage guidelines, leaving some gaps in context for optimal agent 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?

Schema description coverage is 100%, with the 'title' parameter fully documented in the schema. The description doesn't add any extra meaning or context about the parameter beyond what the schema provides, such as formatting 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.

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 the resource 'sections of an EVE University Wiki article', which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_eve_wiki_article' or 'get_eve_wiki_summary', which might retrieve different aspects of wiki content, so it doesn't reach the highest score.

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_summary'. It lacks any context about use cases, exclusions, or prerequisites, leaving the agent to infer usage from the tool name 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