Skip to main content
Glama
jhaenen

wiseoldman-mcp

by jhaenen

Get competition details

wom_get_competition

Retrieve full competition details with participant progress. Optionally specify a metric to preview standings under that metric.

Instructions

Fetches a competition's full details, including participants and their progress.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe competition's numeric Wise Old Man ID.
metricNoOptional alternative A 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). to preview standings as if the competition used this metric.
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does not mention that this is a read-only operation, that it requires no special permissions, or any potential side effects or rate limits. It only states the core 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?

Single sentence, no unnecessary words. Concisely communicates the core function. Front-loaded with the 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?

Without an output schema, the description should hint at the return structure. It mentions 'participants and their progress' but does not explain the role of the optional 'metric' parameter, which alters the standings view. This is a significant gap for a tool with two parameters and no output schema.

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%, so baseline 3. The description does not add meaning beyond the schema; it does not explain the 'id' parameter's role or the optional 'metric' parameter's effect on the returned details. The schema descriptions are adequate on their own.

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 uses a specific verb ('fetches') and identifies the resource ('competition's full details') including participants and progress. It distinguishes from sibling tools like 'wom_search_competitions' or 'wom_get_competition_csv' by stating it returns full details, though it does not explicitly differentiate from 'wom_get_player_competitions' which lists competitions for a 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 is provided on when to use this tool versus alternatives. There are many sibling tools for competitions (search, create, edit, delete, CSV, history), but the description does not specify when to choose this one over others like 'wom_get_competition_csv' or 'wom_get_competition_top_history'.

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