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

Name	Required	Description	Default
`sport`	Yes	Sport to query. One of football, basketball, cricket, tennis.
`slug`	Yes	Competition slug.

Implementation Reference

src/index.js:151-165 (schema)

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]));
```

src/index.js:228-270 (handler)

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,
  };
});

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Apr 23, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, and the description only states it gets data. It fails to disclose behavioral traits such as authentication requirements, rate limits, or error handling (e.g., what happens if the bracket doesn't exist).

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 with no extraneous words, efficiently conveying the tool's purpose and providing illustrative examples.

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 has 2 required parameters and no output schema, the description is adequate but not complete—it doesn't describe the response structure or potential error states, which an agent would need to interpret results correctly.

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 coverage is 100%, so the schema already documents both parameters. The description adds marginal value by giving a concrete example of a slug format, but it doesn't clarify the relationship between slug and sport beyond what the schema provides.

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 specific examples that differentiate it from sibling tools like get_matches or get_standings.

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?

The description provides examples of tournament slugs but offers no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites.

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

Deploy Server