Skip to main content
Glama
WaterSippin

OSRS MCP Server

Official
by WaterSippin

osrs_wiki_parse_page

Extract parsed HTML content from any OSRS Wiki page using the exact title for precise data retrieval and integration into applications or workflows.

Instructions

Get the parsed HTML content of a specific OSRS Wiki page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesThe exact title of the wiki page to parse (e.g., 'Dragon scimitar', 'Abyssal whip'). Case-sensitive.

Implementation Reference

  • The handler function that executes the tool logic: validates input, makes API call to parse the specified wiki page, and returns the parsed HTML text.
    case "osrs_wiki_parse_page":
        const parsePageArgs = getSchemaForTool(name).parse(args) as { page: string };
        const { page } = parsePageArgs;
        const parseResponse = await osrsApiClient.get('', {
            params: {
                action: 'parse',
                page: page,
                prop: 'text',
                formatversion: 2
            }
        });
        return responseToString(parseResponse.data?.parse?.text || 'Page content not found.');
  • Zod schema defining the input parameter 'page' for the tool.
    const OsrsWikiParsePageSchema = z.object({
        page: z.string().describe("The exact title of the wiki page to parse (e.g., 'Dragon scimitar', 'Abyssal whip'). Case-sensitive.")
    });
  • index.ts:309-311 (registration)
    Registration of the tool in the list of available tools returned by listTools, with name and description.
    {
        name: "osrs_wiki_parse_page",
        description: "Get the parsed HTML content of a specific OSRS Wiki page.",
  • Mapping of tool name to its Zod schema in the getSchemaForTool function used for input validation.
    case "osrs_wiki_parse_page":
        return OsrsWikiParsePageSchema;
  • index.ts:262-262 (registration)
    Schema conversion and inclusion in toolSchemas object (note: uses camelCase key).
    osrsWikiParsePage: convertZodToJsonSchema(OsrsWikiParsePageSchema),
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions 'parsed HTML content' but doesn't explain what parsing entails (e.g., cleaned markup, extracted data), potential rate limits, authentication needs, or error handling. This leaves significant gaps for a tool that interacts with an external wiki.

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 without unnecessary words. Every element ('Get', 'parsed HTML content', 'specific OSRS Wiki page') 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.

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'parsed HTML content' means in practice, what format or structure is returned, or any behavioral traits like network dependencies or failure modes. For a tool fetching external data, this leaves critical context gaps.

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 'page' well-documented in the schema (including case-sensitivity and examples). The description adds no additional parameter semantics beyond what's already in the schema, meeting the baseline for high 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 resource ('parsed HTML content of a specific OSRS Wiki page'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'osrs_wiki_get_page_info' or 'osrs_wiki_search', which likely serve related but distinct functions.

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. With siblings like 'osrs_wiki_get_page_info' and 'osrs_wiki_search' available, there's no indication of what distinguishes this parsing tool from those, leaving the agent to guess based on 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/WaterSippin/mcp-osrs'

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