griptonite-mcp

get_competition_rankings

Read-only

Retrieve rankings and standings for a specific competition or view all visible competition rankings in the Griptonite indoor climbing app.

Instructions

See rankings/standings for a competition (or all visible competitions).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_competition_rankings"
  }
}

Input Schema

Name	Required	Description	Default
`competition_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds no additional behavioral context, such as whether authentication is required, real-time updates, or error handling. For a read operation, more details on response characteristics would be valuable.

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 short sentence, front-loaded with the key action and resource. No extraneous words. It earns its place.

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 (one optional parameter, output schema exists), the description is minimally adequate. However, it does not mention what the rankings contain (points, positions, etc.), whether results are sorted, or if pagination applies, which would be helpful for a complete understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains that omitting competition_id returns rankings for all visible competitions, adding meaning beyond the schema (which only provides the parameter with no description). However, it does not specify the format or required structure of the competition_id, leaving some ambiguity for the agent.

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 states the tool shows rankings/standings for a competition or all visible competitions. It clearly identifies the resource (rankings) and scope (competition or all), but the verb 'See' is less specific than 'Retrieve' or 'List'. It distinguishes from siblings like get_gym_rankings and get_world_rankings by focusing on competition-level data.

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 on when to use or when to avoid. The description does not mention alternatives or exclusion criteria. For example, it does not say 'Use this for competition rankings; for gym-wide rankings use get_gym_rankings', which would help differentiate among siblings.

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