Skip to main content
Glama
WaterSippin

OSRS MCP Server

Official
by WaterSippin

osrs_wiki_search

Search the Old School RuneScape Wiki for specific terms, retrieve relevant pages, and control result limits and pagination for precise data access.

Instructions

Search the OSRS Wiki for pages matching a search term.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (1-50)
offsetNoOffset for pagination (0-based)
searchYesThe term to search for on the OSRS Wiki

Implementation Reference

  • The handler function for the 'osrs_wiki_search' tool. Parses input arguments using Zod schema, makes an API request to the OSRS Wiki search endpoint with configurable limit and offset, and returns the search results.
    case "osrs_wiki_search":
        const wikiSearchArgs = getSchemaForTool(name).parse(args) as { search: string; limit?: number; offset?: number };
        const { search, limit = 10, offset = 0 } = wikiSearchArgs;
        const searchResponse = await osrsApiClient.get('', {
            params: {
                action: 'query',
                list: 'search',
                srsearch: search,
                srlimit: limit,
                sroffset: offset,
                srprop: 'snippet|titlesnippet|sectiontitle'
            }
        });
        return responseToString(searchResponse.data);
  • Zod schema defining the input parameters for the osrs_wiki_search tool: required 'search' string, optional 'limit' (1-50), and 'offset' (0+).
    const OsrsWikiSearchSchema = z.object({
        search: z.string().describe("The term to search for on the OSRS Wiki"),
        limit: z.number().int().min(1).max(50).optional().describe("Number of results to return (1-50)"),
        offset: z.number().int().min(0).optional().describe("Offset for pagination (0-based)")
    });
  • index.ts:302-304 (registration)
    Tool registration in the listTools response: defines the tool name and description for discovery.
        name: "osrs_wiki_search",
        description: "Search the OSRS Wiki for pages matching a search term.",
    },
  • index.ts:260-260 (registration)
    Registers the JSON schema for the tool in getToolSchemas() used for tool call validation.
    osrsWikiSearch: convertZodToJsonSchema(OsrsWikiSearchSchema),
  • Schema lookup in getSchemaForTool() switch statement, returns the Zod schema for validation during tool execution.
    case "osrs_wiki_search":
        return OsrsWikiSearchSchema;
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions searching for 'pages matching a search term,' it doesn't describe what the search returns (e.g., page titles, snippets, URLs), whether there are rate limits, authentication requirements, or error conditions. This leaves significant gaps in understanding how the tool behaves beyond basic functionality.

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 directly states the tool's purpose without any fluff. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place, and there's no wasted verbiage.

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 for a search tool with 3 parameters. It doesn't explain what the search returns (e.g., list of page objects, metadata), how results are ordered, or any limitations (e.g., search scope, timeouts). For a tool that likely returns structured data, more context is needed to use it effectively.

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 description adds no parameter-specific information beyond what's already in the schema, which has 100% coverage with clear descriptions for 'search', 'limit', and 'offset'. The baseline score of 3 reflects that the schema adequately documents parameters, so the description doesn't need to compensate, but it also doesn't provide additional context like search syntax examples or result ordering.

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 ('Search') and target resource ('the OSRS Wiki for pages'), making the purpose immediately understandable. It distinguishes from siblings like 'osrs_wiki_get_page_info' and 'osrs_wiki_parse_page' by focusing on search functionality rather than retrieving or parsing specific pages. However, it doesn't explicitly contrast with other search tools in the sibling list, which prevents 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. With many sibling search tools available (e.g., search_data_file, search_iftypes, etc.), there's no indication of what makes this tool unique for OSRS Wiki searches versus other data types. No context about prerequisites, exclusions, or typical use cases is 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/WaterSippin/mcp-osrs'

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