Skip to main content
Glama

List public ladders

list_public_ladders
Read-onlyIdempotent

Public ladders on Club Ladder: ladders whose organizers made them public, with name, id, player count and link. Use to find a club's ladder by name before reading its standings. Private ladders and ladders shared only by link are never listed.

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_public_ladders"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoWords from the ladder's name or description. Leave out to list them all.

Output Schema

NameRequiredDescriptionDefault
totalYes
laddersYes
filteredNo
directoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / filtered
      Added value: +{
      +  "type": "boolean"
      +}
    • removedOutput schema / properties / query
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ]
      -}
  2. Changed2 schema fields changed
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Words from the ladder's name or description. Leave out to list them all.",
      +  "maxLength": 60,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "directory": {
      +      "type": "string"
      +    },
      +    "ladders": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "query": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "total": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "ladders",
      +    "total"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds real value beyond that by disclosing the visibility boundary (private and link-only ladders are excluded) and the field set returned per ladder. It does not mention result limits or pagination, which keeps it at 4.

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?

Two sentences with zero filler: the first establishes identity, scope and return fields; the second establishes the call site and the exclusions. The scoping constraint and the exclusion boundary are both front-loaded rather than buried.

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 one-optional-parameter read tool with full annotation coverage, an output schema, and 100% schema coverage, the description supplies everything an agent needs: what is listed, what is excluded, and when to call it. No behavioral or caller-facing gap remains.

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% and the single 'name' parameter is already fully documented, including the 'leave out to list them all' behavior. The description only adds a usage framing ('find a club's ladder by name') rather than any new syntax, matching, or format detail, so the baseline 3 is appropriate.

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 resource and scope (public ladders, i.e. those whose organizers made them public) and enumerates the returned fields: name, id, player count and link. The phrase 'before reading its standings' implicitly distinguishes this listing tool from the single-ladder read tool, so an agent can tell what it does and what it does not do without opening the schema.

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

Usage Guidelines4/5

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

It gives explicit when-to-use guidance ('Use to find a club's ladder by name before reading its standings') and an explicit exclusion boundary ('Private ladders and ladders shared only by link are never listed'). It stops short of naming the concrete follow-up sibling (get_public_ladder) by name, so 4 rather than 5.

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.