TablePredict

Get competition roster

tablepredict_get_competition_teams

Read-onlyIdempotent

Return the exact canonical club names for domestic leagues or national-team names for grouped tournaments. Grouped competitions preserve their official group membership. Use an id, route slug, or display name from tablepredict_list_competitions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`competition`	Yes	Competition id, route slug, or display name.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`teams`	No
`groups`	No
`competition`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedSep 4, 2026

addedOutput schema / properties / competition / properties / acceptingPredictions / description

Added value: +"Legacy preseason availability flag. False does not rule out domestic late entry; use entryStatus."

addedOutput schema / properties / competition / properties / entryStatus

Added value: +{
+  "description": "Check live late-entry eligibility and penalties at predictorUrl; the catalog does not read member entries.",
+  "enum": [
+    "preseason",
+    "check_late_entry_on_site",
+    "closed"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / competition / properties / predictionLockAt / description
```
Added value: +"Preseason editing cutoff, not the domestic late-entry deadline."
```

changedOutput schema / properties / competition / required

Previous value: -[
-  "id",
-  "name",
-  "country",
-  "season",
-  "mode",
-  "teamCount",
-  "predictionLockAt",
-  "acceptingPredictions",
-  "predictorUrl"
-]New value: +[
+  "id",
+  "name",
+  "country",
+  "season",
+  "mode",
+  "teamCount",
+  "predictionLockAt",
+  "acceptingPredictions",
+  "entryStatus",
+  "predictorUrl"
+]

First observedAug 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds meaningful context beyond annotations by clarifying output semantics: canonical names, group membership preservation, and the distinction between domestic league and grouped tournament naming.

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, no filler. The first sentence front-loads the core behavior and output format; the second provides the crucial input provenance guidance. Every word earns its place.

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 single-parameter read-only tool with a full output schema, the description covers what is returned, naming conventions, grouping behavior, and how to source the input. Nothing essential is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value by explaining valid input forms—competition id, route slug, or display name—and tying them to the list_competitions tool. This clarifies what the parameter may contain beyond the schema's terse description.

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 states a specific action—'Return the exact canonical club names...'—with clear scope distinction between domestic leagues and grouped tournaments. It differentiates itself from sibling tools by specifying roster retrieval rather than prediction links or competition listing.

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?

The description tells the agent exactly how to identify the competition: use an id, route slug, or display name from tablepredict_list_competitions. It does not explicitly contrast with build_prediction_link, but the workflow guidance is clear and practical.

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

All TablePredict tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool has a clearly distinct responsibility: listing competitions, fetching team names, and building prediction links. There is no meaningful overlap between them, and the descriptions reinforce their unique roles.

Naming Consistency5/5

All tool names follow the same snake_case pattern with the consistent tablepredict_ prefix and a clear verb_noun structure: list_competitions, get_competition_teams, build_prediction_link. This makes the API predictable and easy to navigate.

Tool Count5/5

Three tools is appropriate for this focused server: discover competitions, retrieve teams, and generate a prediction link. Each tool is necessary for the intended workflow with no redundant entries.

Completeness5/5

The tool set covers the full prediction-link generation workflow: list available competitions, get canonical team names, then build and validate the link. The descriptions intentionally scope out account management and publishing, so there are no obvious dead ends for the stated purpose.

Resources

Need Help?