Skip to main content
Glama
Sign In
wiseoldman-mcp

wiseoldman-mcp

by jhaenen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get player details by ID

wom_get_player_by_id

Fetch all player details by numeric Wise Old Man ID, including stats, activities, and other tracked data for any OSRS player.

Instructions

Fetches a player's full details by their numeric Wise Old Man ID.

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": {
      "id": "<id>"
    },
    "name": "wom_get_player_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe player's numeric Wise Old Man ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It only says 'Fetches full details' without specifying what those details include, any side effects, permissions needed, or rate limits. This is insufficient for safe usage.

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?

Single sentence with no fluff. Key information is front-loaded: the action, resource, and identifier type. Every word is necessary.

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

Completeness3/5

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

For a simple 1-parameter tool with no annotations or output schema, the description is adequate but leaves gaps. It does not relate to sibling tools or explain what 'full details' entails. Works as minimal viable.

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%, baseline is 3. Description adds no new meaning beyond the schema; it merely restates 'numeric Wise Old Man ID' which is already in the schema's parameter description. No additional details on usage, format, or constraints.

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?

Description clearly states verb 'Fetches', resource 'a player's full details', and the specific identifier 'numeric Wise Old Man ID'. This distinguishes it from sibling tools like wom_search_players or wom_get_player.

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?

No guidance on when to use this tool versus alternatives. For example, it should mention that this tool is for fetching by numeric ID, while wom_get_player might use a username. No when-not-to-use or alternative references.

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