Skip to main content
Glama
Sign In
wiseoldman-mcp

wiseoldman-mcp

by jhaenen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get group competitions

wom_get_group_competitions

Retrieve all competitions hosted by a group using its numeric Wise Old Man ID.

Instructions

Fetches all competitions hosted by a group.

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": {
      "id": "<id>"
    },
    "name": "wom_get_group_competitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe group's numeric Wise Old Man ID.
limitNoMax number of results (pagination).
offsetNoNumber of results to skip (pagination).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must convey behavior. It correctly states 'fetches' implying a read-only operation. However, it does not disclose pagination behavior or return format, which are partly inferred from the schema. It adds little beyond the name.

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, front-loaded sentence with no redundancy. Every word is necessary.

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?

Despite having pagination parameters, the description does not mention that the result is a paginated list. It lacks details on output format or potential edge cases, making it incomplete for the tool's complexity.

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 is 3. The description does not add any extra meaning beyond the parameter descriptions in the schema (e.g., explaining that id is the group ID, limit/offset for pagination).

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 tool fetches all competitions hosted by a group, specifying both the action and the resource. It distinguishes from siblings like wom_get_competition (single) and wom_search_competitions (search across groups).

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_group for group details, wom_search_competitions for searching). No when-not or prerequisite information is given.

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

Deploy Server

Other Tools