Skip to main content
Glama
Backspace-me

SportScore

get_bracket

Retrieve the knockout bracket for a tournament by specifying the sport and competition slug. Access bracket data for football, basketball, cricket, or tennis.

Instructions

Get the knockout bracket for a tournament (e.g. 'uefa-champions-league', 'nba-playoffs').

Input Schema

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

Implementation Reference

  • Tool schema definition for 'get_bracket' — defines input params (sport enum + slug), maps to API path /api/widget/bracket/
    {
      name: "get_bracket",
      description:
        "Get the knockout bracket for a tournament (e.g. 'uefa-champions-league', 'nba-playoffs').",
      inputSchema: {
        type: "object",
        properties: {
          sport: sportSchema,
          slug: { type: "string", description: "Competition slug." },
        },
        required: ["sport", "slug"],
      },
      path: "/api/widget/bracket/",
      paramMap: (args) => ({ sport: args.sport, slug: args.slug }),
    },
  • src/index.js:183-183 (registration)
    Registration: TOOLS array includes get_bracket; TOOL_BY_NAME map allows name-based dispatch at runtime
    const TOOL_BY_NAME = new Map(TOOLS.map((t) => [t.name, t]));
  • Generic CallTool handler that dispatches to any tool (including get_bracket) by looking up the TOOL_BY_NAME map, calling paramMap, then invoking callApi with the tool's path
    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,
      };
    });
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates a read operation ('Get') but does not disclose potential errors (e.g., if tournament has no bracket), auth requirements, rate limits, or return structure. The description is minimal but adequate for a simple retrieval tool.

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?

The description is a single, front-loaded sentence that immediately states the tool's purpose and provides examples. Every word is substantive, with no waste.

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?

Given the tool's simplicity (2 required params, no output schema), the description is reasonably complete but lacks details on output format or how the bracket is structured. It does not mention sibling tools or edge cases, so while functional, it could be more informative.

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?

The input schema has 100% description coverage with details for both parameters. The description adds value by providing concrete slug examples ('uefa-champions-league', 'nba-playoffs'), which help the agent understand the format and scope beyond the schema's generic '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 the knockout bracket for a tournament, with verb 'Get' and resource 'knockout bracket'. Examples 'uefa-champions-league' and 'nba-playoffs' provide concrete context, and it is easily distinguished from siblings like get_matches or get_standings which deal with different data.

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?

The description does not provide guidance on when to use this tool versus alternatives like get_matches or get_standings. No when-not-to-use instructions or prerequisites are mentioned, leaving the agent without contextual decision support.

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