Skip to main content
Glama

List team competitions

list_team_competitions
Read-onlyIdempotent

List the team competitions the player belongs to (Ryder cups, leagues and groups) with their id, version and the player's real role: leader, delegated captain or participant. Call it first to find a competition by name instead of guessing ids; then get_team_competition for its detail, get_team_competition_archive for an imported history, or manage_team_competition to propose a change. Read-only.

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": "list_team_competitions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description reinforces read-only status. It also adds valuable return semantics by naming the fields and role values, though it does not cover authorization or pagination behavior.

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 compact and front-loaded, with the core listing behavior stated first and the follow-up routing packed efficiently into a single sentence. Every clause contributes useful selection or follow-up guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter list tool with no output schema, the description is complete enough for an agent to call it correctly. It explains what will be returned, when to use it, and which sibling tools handle detail, archive, or mutations.

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 tool has no parameters, so there is no parameter meaning to explain and the baseline is 4. The description appropriately focuses on returned data and workflow instead of inventing input semantics.

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 names a specific verb and resource and enumerates the competition types and returned fields: id, version, and the player's real role. It is clearly distinguishable from list_competitions and the get_team_competition family.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to call this first to find a competition by name instead of guessing ids, and it routes the agent to get_team_competition, get_team_competition_archive, or manage_team_competition for follow-up actions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.