wiseoldman-mcp

Get player gains

wom_get_player_gained

Retrieve a player's gains across all stats over a specified time period or custom date range.

Instructions

Fetches how much a player has gained across all metrics, for a given period or custom date range.

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>"
    },
    "name": "wom_get_player_gained"
  }
}

Input Schema

Name	Required	Description
`period`	No	A time period. One of: five_min, day, week, month, year. Alternatively use startDate/endDate for a custom range.
`endDate`	No	End of a custom date range (ISO 8601), used instead of `period`.
`username`	Yes	The player's username (case-insensitive, spaces or underscores both work).
`startDate`	No	Start of a custom date range (ISO 8601), used instead of `period`.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions 'all metrics' without specifying what metrics (skills, activities, etc.) and provides no details on authentication, rate limits, or consequences of use. This is minimal for a read-only tool.

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 sentence that is front-loaded with the verb and resource. Every word is essential, and there is no unnecessary information. It is highly efficient.

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 the tool's simplicity (4 parameters, no output schema), the description is adequate but not complete. It lacks details on what 'all metrics' includes and does not hint at the return structure, which is important since there is no output schema. However, the schema and context signals provide some completeness.

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 description coverage is 100% with each parameter described (period, startDate, endDate, username). The description adds 'for a given period or custom date range' which is already captured in the parameter descriptions. It does not provide additional meaning beyond the schema.

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 'Fetches how much a player has gained across all metrics, for a given period or custom date range.' It specifies the verb 'fetches', resource 'player gains', and scope 'all metrics'. This differentiates it from sibling tools like wom_get_player (current stats) or wom_get_player_snapshots (historical snapshots).

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 for retrieving gains over time via period or custom date range, but does not explicitly state when to use this tool over alternatives like wom_get_player_snapshots or wom_group_gained. No comparisons or exclusions are provided.

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

Deploy Server