Skip to main content
Glama

Get Standings

get_standings
Read-only

Fetch group standings tables for every stage of a BuzzerBeater competition using a competition ID and optional season filter.

Instructions

Standings table per group of each stage of a BuzzerBeater competition.

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": {
      "competition_id": "<competition_id>"
    },
    "name": "get_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
seasonNo
competition_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds structural context — results are broken down by group and by stage — which is useful, but says nothing about season defaulting behavior, empty results, or whether all stages are returned at once; the output schema covers return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with no filler and the scope front-loaded. It is efficient, though the fragment style leaves no room for the parameter or behavior detail that would actually help.

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?

The tool is simple (2 params, one required, output schema present), so the description needn't explain return values. However, with zero schema coverage the omission of season semantics and competition_id format leaves a real gap an agent would hit on first call.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, yet it only weakly gestures at competition_id and never explains the season parameter (nullable, defaults to null, presumably current season) or the expected format of the competition identifier. The two params remain largely opaque.

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 names a specific resource (standings table) and a concrete scope (per group, per stage, of a given competition), so an agent knows exactly what kind of data comes back. It does not use a verb or explicitly distinguish itself from siblings, but no sibling in the list covers standings, so ambiguity is low.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_team_stats or get_seasons for related data. The only implied usage is 'fetch standings for a competition,' which the agent has to infer from the noun phrase.

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