wiseoldman-mcp

Get player competition standings

wom_get_player_competition_standings

Get a player's rank in their competitions filtered by status (upcoming, ongoing, or finished).

Instructions

Fetches a player's rank/standing in each of their competitions, filtered by status.

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": {
      "username": "<username>",
      "status": "<status>"
    },
    "name": "wom_get_player_competition_standings"
  }
}

Input Schema

Name	Required	Description	Default
`status`	Yes	Filter by competition status (required).
`username`	Yes	The player's username (case-insensitive, spaces or underscores both work).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose whether the tool is read-only, requires authentication, has rate limits, or returns paginated results. The term 'fetches' implies a read operation, but no explicit behavioral details are given.

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?

The description is a single, efficient sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to parse.

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?

With no output schema and no annotations, the description should compensate by explaining the return format, pagination, or data structure. It only mentions 'rank/standing' without describing the response type (array? object?) or any limits, leaving the agent with incomplete information.

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 both parameters already documented in the input schema (e.g., status enum, username case-insensitivity). The description adds no additional meaning beyond what the schema provides, so it meets the baseline of 3.

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 'fetches', the resource 'player's rank/standing in each of their competitions', and the filter condition 'by status'. This distinguishes it from sibling tools like wom_get_player_competitions (which likely lists competitions without standings) and wom_get_competition (which gives competition details).

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?

The description implies usage by mentioning the status filter but does not explicitly explain when to use this tool versus alternatives such as wom_get_player_competitions. No guidance on prerequisites or exclusions is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server