Skip to main content
Glama
jhaenen

wiseoldman-mcp

by jhaenen

Search competitions

wom_search_competitions

Search for competitions on Wise Old Man by title, type, status, or metric to find matching events.

Instructions

Searches Wise Old Man for competitions matching optional title/type/status/metric filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNo
limitNoMax number of results (pagination).
titleNoPartial or full competition title.
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).
offsetNoNumber of results to skip (pagination).
statusNo
Behavior2/5

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

With no annotations provided, the description carries full burden but only mentions that it searches with filters. It does not disclose that it is a read-only operation, nor does it describe pagination behavior, response format, or any side effects.

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?

A single, front-loaded sentence with no extraneous words. Every element serves to convey the core functionality efficiently.

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?

Given 6 parameters and no output schema, the description should explain more about result behavior (e.g., pagination, default filters). It is adequate but leaves gaps in understanding the full tool output.

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?

The description groups the parameters as 'filters', which adds some context beyond the schema's individual descriptions. However, schema coverage is 67% and the description does not resolve undocumented parameters (type, status) or add usage details.

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 verb 'searches' and the resource 'competitions', listing the filter criteria (title, type, status, metric). It distinguishes from sibling tools like wom_get_competition which retrieves a single competition.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., wom_get_competition, wom_create_competition). It only describes the filter options, leaving the agent to infer usage context.

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