Skip to main content
Glama
jhaenen

wiseoldman-mcp

by jhaenen

Get player records

wom_get_player_records

Retrieve a player's best recorded gains, filterable by time period or specific metric.

Instructions

Fetches a player's best recorded gains (records), optionally filtered by period and/or metric.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricNoA metric name. One of: a skill (overall, attack, defence, strength, hitpoints, ranged, prayer, magic, cooking, woodcutting, fletching, fishing, firemaking, crafting, smithing, mining, herblore, agility, thieving, slayer, farming, runecrafting, hunter, construction, sailing), a boss (abyssal_sire, alchemical_hydra, amoxliatl, araxxor, artio, barrows_chests, brutus, bryophyta, callisto, calvarion, cerberus, chambers_of_xeric, chambers_of_xeric_challenge_mode, chaos_elemental, chaos_fanatic, commander_zilyana, corporeal_beast, crazy_archaeologist, dagannoth_prime, dagannoth_rex, dagannoth_supreme, deranged_archaeologist, doom_of_mokhaiotl, duke_sucellus, general_graardor, giant_mole, grotesque_guardians, hespori, kalphite_queen, king_black_dragon, kraken, kreearra, kril_tsutsaroth, lunar_chests, maggot_king, mimic, nex, nightmare, phosanis_nightmare, obor, phantom_muspah, sarachnis, scorpia, scurrius, shellbane_gryphon, skotizo, sol_heredit, spindel, tempoross, the_gauntlet, the_corrupted_gauntlet, the_hueycoatl, the_leviathan, the_royal_titans, the_whisperer, theatre_of_blood, theatre_of_blood_hard_mode, thermonuclear_smoke_devil, tombs_of_amascut, tombs_of_amascut_expert, tzkal_zuk, tztok_jad, vardorvis, venenatis, vetion, vorkath, wintertodt, yama, zalcano, zulrah), an activity (bounty_hunter_hunter, bounty_hunter_rogue, clue_scrolls_all, clue_scrolls_beginner, clue_scrolls_easy, clue_scrolls_medium, clue_scrolls_hard, clue_scrolls_elite, clue_scrolls_master, last_man_standing, pvp_arena, soul_wars_zeal, guardians_of_the_rift, colosseum_glory, collections_logged), or a computed metric (ehp, ehb).
periodNoA time period. One of: five_min, day, week, month, year. Alternatively use startDate/endDate for a custom range.
usernameYesThe player's username (case-insensitive, spaces or underscores both work).
Behavior2/5

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

No annotations exist, so description must carry full burden. It fails to disclose behavioral traits such as authorization needs, what qualifies as a 'record', response structure, or rate limits. Only states basic function.

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, directly states purpose with no waste. Front-loaded with verb and resource.

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?

No output schema, and description does not explain return values or structure of 'records'. For a tool with 3 parameters, this is insufficient for an agent to fully understand the response.

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% with detailed descriptions for each parameter. Description adds no additional meaning beyond restating filtering options. Baseline score of 3 is appropriate.

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 it fetches a player's best recorded gains (records) with optional filtering by period and/or metric. This distinguishes it from sibling tools like wom_get_player (general player info) or wom_get_player_gained (gain over period).

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

Usage Guidelines3/5

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

Description implies use for records but does not explicitly compare to siblings like wom_get_player_gained or wom_get_player_snapshots. No when-not or alternative guidance provided.

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

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/jhaenen/wiseoldman_mcp'

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