Skip to main content
Glama
WaterSippin

OSRS MCP Server

Official
by WaterSippin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

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

  • index.ts:418-430 (handler)
    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.');
  • index.ts:48-50 (schema)
    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.",
  • index.ts:281-282 (schema)
    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),

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't cover important aspects like whether it's a read-only operation, potential rate limits, authentication needs, error handling, or the format of the returned HTML. This leaves significant gaps in understanding the tool's behavior.

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 efficiently conveys the core function without any unnecessary words. It is front-loaded and appropriately sized for the tool's purpose, making it easy to parse and understand quickly.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what the parsed HTML content includes, how it's structured, or any limitations (e.g., partial content, errors for missing pages). For a tool with no structured behavioral data, more context is needed to be fully helpful.

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?

The input schema has 100% description coverage, with the 'page' parameter well-documented in the schema itself. The description adds no additional meaning beyond what the schema provides, such as examples or usage tips, so it meets the baseline score of 3 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 action ('Get') and resource ('parsed HTML content of a specific OSRS Wiki page'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'osrs_wiki_get_page_info' or 'osrs_wiki_search', which might have overlapping or related functions, so it falls short of a perfect 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 the sibling tools 'osrs_wiki_get_page_info' or 'osrs_wiki_search'. It lacks context on use cases, exclusions, or prerequisites, leaving the agent to infer usage based on 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.

Deploy Server

Other Tools

Related Tools