Skip to main content
Glama
Sign In
osrs-wiki-mcp

osrs-wiki-mcp

by SSanderV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_wiki_sections

Read-onlyIdempotent

Retrieve section metadata for any Old School RuneScape Wiki page to locate specific sections before fetching their content.

Instructions

List bounded section metadata for an Old School RuneScape Wiki page before calling get_wiki_section.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "get_wiki_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesExact Wiki page title

Output Schema

NameRequiredDescriptionDefault
titleYes
totalYes
returnedYes
sectionsYes
warningsYes
truncatedYes
provenanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds 'bounded section metadata' but does not explain what 'bounded' means or what metadata fields are included. With rich annotations, the description adds marginal value.

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 concise sentence that front-loads the action and purpose, with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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

Given the output schema exists (not shown but indicated), the description need not explain return values. For a simple tool with one parameter and thorough annotations, the description covers the essential task and usage context fully.

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 coverage is 100% and the schema clearly describes the 'title' parameter as 'Exact Wiki page title'. The description adds no additional parameter information beyond the schema, so baseline score 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists 'bounded section metadata' for a Wiki page and explicitly positions it as a prerequisite to get_wiki_section, distinguishing it from that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use this tool 'before calling get_wiki_section', providing clear when-to-use guidance. It does not explicitly mention when not to use it, but the context implies it's for exploring sections.

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