osrs-companion
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchA | Search the Old School RuneScape Wiki for articles matching a query |
| summaryB | Get the introductory summary of an OSRS Wiki page |
| priceA | Look up the current Grand Exchange price for an item |
| playerC | Fetch RuneLite player data via the WikiSync plugin (requires RuneLite client) |
| list_synced_playersA | List all players that have synced data from RuneLite. Use this first to find available usernames. |
| get_my_profileA | Get a full summary of synced player data including stats, quest count, bank size, and diary progress. Data is synced from RuneLite via the MCP Sync plugin. |
| get_my_bankA | Search and browse the player's synced bank contents. Supports filtering by item name, bank tab, and minimum quantity. |
| get_my_statsA | Get the player's synced skill levels and XP. Optionally filter to a specific skill. |
| get_my_questsA | Get the player's synced quest completion status. Filter by state or search by name. |
| get_my_equipmentA | Get the player's currently equipped items (last synced state). |
| get_my_inventoryA | Get the player's current inventory contents (last synced state). |
| get_my_diariesA | Get the player's achievement diary completion status. Optionally filter by region. |
| get_my_combat_achievementsA | Get the player's combat achievement completion status. Optionally search by task name. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose: wiki search, summary, price, and the player data tools are all narrowly scoped (profile, bank, stats, quests, equipment, inventory, diaries, combat achievements). The 'player' tool is slightly generic but is differentiated from list_synced_players by fetching raw data, and from get_my_* by being a lower-level operation. No two tools appear to do the same thing.
The player data tools consistently follow a 'get_my_*' pattern, but the wiki tools use simple verbs/nouns (search, summary, price) and 'player' is a bare noun. This creates minor inconsistency across the set, but within each functional group the naming is predictable and readable.
Thirteen tools is well within the ideal 3-15 range for a server with two clear purposes: wiki lookup and player data retrieval. Every tool serves a distinct need without redundancy, making the set feel appropriately scoped.
The server covers the core companion features: wiki search with summary and price lookup, and comprehensive synced player data including profile, bank, stats, quests, equipment, inventory, diaries, and combat achievements. There are no obvious missing operations for the stated domain, as it is a read-only companion tool.