Skip to main content
Glama
Backspace-me

SportScore

get_standings

Retrieve the current standings table for any league or competition using a sport and slug, such as premier-league or nba.

Instructions

Get the current standings table for a league or competition by slug (e.g. 'premier-league', 'la-liga', 'nba').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sportYesSport to query. One of football, basketball, cricket, tennis.
slugYesCompetition slug.

Implementation Reference

  • Input schema definition for get_standings tool: defines the sport (enum of football, basketball, cricket, tennis) and slug (competition slug like 'premier-league') parameters.
    {
      name: "get_standings",
      description:
        "Get the current standings table for a league or competition by slug (e.g. 'premier-league', 'la-liga', 'nba').",
      inputSchema: {
        type: "object",
        properties: {
          sport: sportSchema,
          slug: { type: "string", description: "Competition slug." },
        },
        required: ["sport", "slug"],
      },
      path: "/api/widget/standings/",
      paramMap: (args) => ({ sport: args.sport, slug: args.slug }),
    },
  • src/index.js:100-100 (registration)
    Tool name registration in TOOLS array with name 'get_standings', mapping to path '/api/widget/standings/' and paramMap function.
    name: "get_standings",
  • Generic CallToolRequestSchema handler that routes all tool calls (including get_standings) by looking up the tool config from TOOL_BY_NAME, calling the API via callApi() with tool.path and tool.paramMap(args), and returning the response.
    server.setRequestHandler(CallToolRequestSchema, async (req) => {
      const { name, arguments: rawArgs } = req.params;
      const tool = TOOL_BY_NAME.get(name);
      if (!tool) {
        return {
          isError: true,
          content: [{ type: "text", text: `Unknown tool: ${name}` }],
        };
      }
      const args = rawArgs ?? {};
      if (args.sport && !SPORTS.includes(args.sport)) {
        return {
          isError: true,
          content: [
            { type: "text", text: `Invalid sport '${args.sport}'. Must be one of: ${SPORTS.join(", ")}.` },
          ],
        };
      }
    
      const params = tool.paramMap(args);
      let result;
      try {
        result = await callApi(tool.path, params);
      } catch (err) {
        return {
          isError: true,
          content: [{ type: "text", text: `Network error calling SportScore API: ${err.message}` }],
        };
      }
    
      const envelope = {
        tool: name,
        request_url: result.url,
        http_status: result.status,
        data: result.body,
        ...attributionFooter(),
      };
    
      return {
        content: [{ type: "text", text: JSON.stringify(envelope, null, 2) }],
        isError: result.status >= 400,
      };
    });
Behavior2/5

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

No annotations provided, and the description only states 'get the current standings table' without disclosing whether it's read-only, requires auth, or any other behavioral traits such as rate limits or side effects.

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?

Single sentence, 17 words, with no redundancy. Essential information is front-loaded: action, resource, and usage example.

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?

Adequate for a simple two-parameter tool, but without annotations or an output schema, the description does not specify the return format (e.g., array of standings entries). Could be more complete by hinting at output structure.

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% with descriptions for both sport (enum) and slug. The description adds value by providing example slugs and clarifying the slug identifies the competition, going beyond the schema's minimal 'Competition slug.'

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 clearly states the tool retrieves current standings table for a league or competition by slug, with concrete examples like 'premier-league', 'la-liga', 'nba', distinguishing it from siblings like get_bracket or get_match_detail.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives like get_bracket or get_matches. The purpose is clear but lacks direct comparison or contextual triggers.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Backspace-me/sportscore-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server