Skip to main content
Glama
Sports Hub MCP Server

Sports Hub MCP Server

by danmorris27

sportsrc: Get table

sportsrc_get_table
Read-onlyIdempotent

Retrieve the standings table for a specified football league by league ID to view team positions and points.

Instructions

Get the standings table for a specific football league.

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": {
      "league": "<league>"
    },
    "name": "sportsrc_get_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoKeys to keep (comma-separated).
leagueYesLeague id (use sportsrc_get_leagues to list). E.g. "PL", "CL", "BL1".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds nothing beyond that — no note on which seasons/competitions are covered, freshness of standings, or failure modes for an invalid league id.

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?

One short, front-loaded sentence with no wasted words. It is efficient, though it borders on under-specified rather than being fully informative.

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?

With no output schema, the description leaves the shape of the returned table (columns, ranking order, tie handling) unspecified; for a simple read-only lookup it is just adequate. An agent can call it, but cannot predict the return payload.

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% for both parameters, including the league id examples and the fields comma-separated format, so the schema carries this dimension. The description adds no parameter meaning beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb (get) and resource (standings table) scoped to a football league, which is clearer than a bare 'get table'. However, it gives no hint of how it differs from the many sibling standings tools (sportsdb_get_standings, openliga_get_table, espn_get_standings, nhl_get_standings), so sibling differentiation is absent.

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?

No when-to-use guidance, no exclusions, no named alternative. The only routing help is in the schema (league id via sportsrc_get_leagues), not the description. Usage is only implied by the tool name.

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

Deploy Server

Other Tools