Build validated football table and World Cup group prediction links with TablePredict.
Validate a complete prediction and return a source-attributed TablePredict URL prefilled with that ranking. Domestic competitions require order; grouped competitions require every group. This tool does not save, publish, or create an account.
| Name | Required | Description | Default |
|---|---|---|---|
| order | No | Complete top-to-bottom club ranking for a domestic table competition. | |
| groups | No | Every group and its complete ranked team order for a grouped competition. | |
| season | No | Optional season check; must match the current catalog season. | |
| competition | Yes | Competition id, route slug, or display name. |
| Name | Required | Description |
|---|---|---|
| mode | Yes | |
| saved | Yes | |
| season | Yes | |
| source | Yes | |
| competitionId | Yes | |
| predictionUrl | Yes | |
| competitionName | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explicitly explains that the tool validates rather than persists, and that it does not save, publish, or create an account. This complements the annotation readOnlyHint=true and idempotentHint=true, giving an agent a clear mental model of the tool's side effects and boundaries.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences convey purpose, key validation rules, and notable non-behaviors with no redundancy. The description is front-loaded with the core action and immediately covers the most impactful constraints.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the presence of a clear input schema, an output schema, and annotations, the remaining gaps are small. The last sentence clarifies that no account or publishing side effect occurs, and the tool description covers the necessary condition split. It could improve by naming sibling tools to explicitly state when this tool is not needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although the schema already covers all parameter fields with descriptions, the description adds important relationship semantics: order is required for domestic competitions and every group is required for grouped competitions. This provides cross-parameter context beyond standalone schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states a specific action: validate a complete prediction and return a source-attributed TablePredict URL prefilled with the ranking. It clearly distinguishes this from sibling tools by focusing on URL generation rather than retrieving teams or listing competitions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides useful conditional usage guidance: domestic competitions require order and grouped competitions require every group. However, it never explicitly discusses when to prefer this tool over the sibling tools or what prerequisite steps like fetching teams or competitions should happen first.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| competition | Yes | Competition id, route slug, or display name. |
| Name | Required | Description |
|---|---|---|
| teams | No | |
| groups | No | |
| competition | Yes |
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.
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.
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.
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.
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.
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.
List competitions currently configured in TablePredict, including season, prediction mode, roster size, cutoff, and predictor URL. Call this before requesting a roster or building a prediction link. Returns no user data.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| total | Yes | |
| competitions | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive behavior, so the bar is lower. The description adds useful context by stating 'Returns no user data' and clarifying that it lists currently configured competitions, which supplements the annotation set.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with zero filler. It front-loads the action and resource, then provides essential usage context, making it maximally efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read-only tool with an output schema available, the description covers what is listed, when to call it, and a relevant behavioral note. Nothing an agent needs to invoke it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema coverage is trivially 100%, so the description need not explain parameters. No parameter information is missing, and the baseline for zero-parameter tools is satisfied.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') with a clear resource ('competitions currently configured in TablePredict') and enumerates the exact fields returned. This clearly distinguishes it from siblings that build prediction links or fetch competition teams.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly instructs to call this tool before requesting a roster or building a prediction link, naming the relevant sibling operations. This gives clear when-to-use guidance with no ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
tablepredict_get_competition_teams4 fields changedOutput schema / properties / competition / properties / acceptingPredictions / descriptionAdded value: +"Legacy preseason availability flag. False does not rule out domestic late entry; use entryStatus."Output schema / properties / competition / properties / entryStatusAdded 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"
+}Output schema / properties / competition / properties / predictionLockAt / descriptionAdded value: +"Preseason editing cutoff, not the domestic late-entry deadline."Output schema / properties / competition / requiredPrevious value: -[
- "id",
- "name",
- "country",
- "season",
- "mode",
- "teamCount",
- "predictionLockAt",
- "acceptingPredictions",
- "predictorUrl"
-]New value: +[
+ "id",
+ "name",
+ "country",
+ "season",
+ "mode",
+ "teamCount",
+ "predictionLockAt",
+ "acceptingPredictions",
+ "entryStatus",
+ "predictorUrl"
+]tablepredict_list_competitions4 fields changedOutput schema / properties / competitions / items / properties / acceptingPredictions / descriptionAdded value: +"Legacy preseason availability flag. False does not rule out domestic late entry; use entryStatus."Output schema / properties / competitions / items / properties / entryStatusAdded 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"
+}Output schema / properties / competitions / items / properties / predictionLockAt / descriptionAdded value: +"Preseason editing cutoff, not the domestic late-entry deadline."Output schema / properties / competitions / items / requiredPrevious value: -[
- "id",
- "name",
- "country",
- "season",
- "mode",
- "teamCount",
- "predictionLockAt",
- "acceptingPredictions",
- "predictorUrl"
-]New value: +[
+ "id",
+ "name",
+ "country",
+ "season",
+ "mode",
+ "teamCount",
+ "predictionLockAt",
+ "acceptingPredictions",
+ "entryStatus",
+ "predictorUrl"
+]tablepredict_build_prediction_link1 field changedInput schema / properties / order / descriptionPrevious value: -"Complete top-to-bottom team ranking for a table competition."New value: +"Complete top-to-bottom club ranking for a domestic table competition."tablepredict_build_prediction_linktablepredict_get_competition_teamstablepredict_list_competitionsClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Calibrated, sourced football predictions: odds, tournament sims, standings, brackets, model card.
Free World Cup 2026 prediction game with fixtures, picks, brackets, and leaderboards
Historical football results, teams, competitions and draw/streak statistics via 10 read-only tools.
Football fixtures, standings, and odds intelligence for AI agents.
Add one secure layer between your agents and this server.
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.
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.
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.
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.
