Skip to main content
Glama
WaterSippin

OSRS MCP Server

Official
by WaterSippin

osrs_wiki_get_page_info

Retrieve detailed information about specific pages on the Old School RuneScape Wiki by providing comma-separated titles, enabling quick access to essential game data and references.

Instructions

Get information about specific pages on the OSRS Wiki.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titlesYesComma-separated list of page titles to get info for (e.g., Dragon_scimitar,Abyssal_whip)

Implementation Reference

  • Handler implementation for the 'osrs_wiki_get_page_info' tool. Parses input arguments, makes an API call to the OSRS Wiki for page info using the 'query' action and 'info' prop, and returns the response.
    case "osrs_wiki_get_page_info":
        const pageInfoArgs = getSchemaForTool(name).parse(args) as { titles: string };
        const { titles } = pageInfoArgs;
        const pageInfoResponse = await osrsApiClient.get('', {
            params: {
                action: 'query',
                prop: 'info',
                titles: titles
            }
        });
        return responseToString(pageInfoResponse.data);
  • Zod schema defining the input parameters for the tool: a comma-separated list of page titles.
    const OsrsWikiGetPageInfoSchema = z.object({
        titles: z.string().describe("Comma-separated list of page titles to get info for (e.g., Dragon_scimitar,Abyssal_whip)")
    });
  • index.ts:305-308 (registration)
    Tool registration in the list of available tools returned by ListToolsRequestHandler.
    {
        name: "osrs_wiki_get_page_info", 
        description: "Get information about specific pages on the OSRS Wiki.",
    },
  • Schema lookup case in getSchemaForTool function used for input validation during tool calls.
    case "osrs_wiki_get_page_info":
        return OsrsWikiGetPageInfoSchema;
  • index.ts:260-261 (registration)
    JSON schema conversion and caching for the tool in getToolSchemas.
    osrsWikiSearch: convertZodToJsonSchema(OsrsWikiSearchSchema),
    osrsWikiGetPageInfo: convertZodToJsonSchema(OsrsWikiGetPageInfoSchema),
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 the tool 'gets information' but doesn't clarify what type of information (e.g., metadata, content, summaries), how it handles errors, rate limits, or authentication needs. 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 purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 information is returned, how results are formatted, or any behavioral traits like error handling. For a tool with no structured metadata, this leaves too many open questions for effective 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?

The input schema has 100% description coverage, with the 'titles' parameter well-documented as a comma-separated list of page titles. The description adds no additional parameter semantics beyond what the schema provides, 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 action ('Get information') and resource ('specific pages on the OSRS Wiki'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'osrs_wiki_parse_page' or 'osrs_wiki_search', which likely have overlapping domains but different functionalities.

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. It doesn't mention when to prefer this over 'osrs_wiki_parse_page' or 'osrs_wiki_search', nor does it specify any prerequisites or exclusions for usage.

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