Skip to main content
Glama

get_team_match

Read-onlyIdempotent

Retrieve a team's contribution to a specific FRC match, including alliance, EPA, predicted score components, and outcome flags. Ideal for scouting and post-match analysis.

Instructions

Get a single team's contribution to a single FIRST Robotics Competition (FRC) match - the per-robot view of one match. Returns which alliance the team was on (red/blue), the team's EPA going into the match, the team's predicted score contribution by component, and post-match outcome flags. Useful for scouting and post-match analysis: "how much did team 2056 contribute to alliance score in 2024onham_sf2m1?". Requires both team (integer, no prefix) and match (match key like "2024flor_qm20"). For listing many team-match rows, use get_team_matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamYesTeam number (no prefix), e.g. 86
matchYesMatch key, e.g. 2024flor_qm20

Implementation Reference

  • Handler for get_team_match: parses team and match from args, calls Statbotics API endpoint /v3/team_match/{team}/{match}, and returns the JSON response.
    case 'get_team_match': {
      const { team, match } = GetTeamMatchInputSchema.parse(args);
      const data = await makeApiRequest(`/v3/team_match/${team}/${match}`);
      return {
        content: [{ type: 'text', text: JSON.stringify(data, null, 2) }],
      };
    }
  • Input schema for get_team_match: requires 'team' (integer, min 1) and 'match' (string match key).
    export const GetTeamMatchInputSchema = z.object({
      team: TeamNumberSchema,
      match: MatchKeySchema,
    });
  • src/tools.ts:241-257 (registration)
    Registration of get_team_match tool in the tools array with description, read-only annotations, and input schema.
    {
      name: 'get_team_match',
      description:
        "Get a single team's contribution to a single FIRST Robotics Competition (FRC) match - the per-robot " +
        'view of one match. ' +
        "Returns which alliance the team was on (red/blue), the team's EPA going into the match, the team's " +
        'predicted score contribution by component, and post-match outcome flags. ' +
        'Useful for scouting and post-match analysis: "how much did team 2056 contribute to alliance score in ' +
        '2024onham_sf2m1?". ' +
        'Requires both `team` (integer, no prefix) and `match` (match key like "2024flor_qm20"). ' +
        'For listing many team-match rows, use get_team_matches.',
      annotations: {
        title: 'Get FRC Team Contribution in Match (Single Team-Match)',
        ...readOnlyAnnotations,
      },
      inputSchema: toMCPSchema(GetTeamMatchInputSchema),
    },
  • Helper function makeApiRequest used by the handler to make HTTP GET requests to the Statbotics API.
    export async function makeApiRequest(endpoint: string): Promise<unknown> {
      try {
        const url = `https://api.statbotics.io${endpoint}`;
    
        const response = await fetch(url, {
          headers: {
            Accept: 'application/json',
          },
        });
    
        if (!response.ok) {
          const errorMessage = `Statbotics API request failed: ${response.status} ${response.statusText} for endpoint ${endpoint}`;
          await log('error', errorMessage);
          throw new Error(errorMessage);
        }
    
        return response.json();
      } catch (error) {
        if (error instanceof Error) {
          const errorMessage = `API request error for endpoint ${endpoint}: ${error.message}`;
          await log('error', errorMessage);
          throw error;
        }
        const errorMessage = `Unknown error during API request for endpoint ${endpoint}`;
        await log('error', `${errorMessage}: ${error}`);
        throw new Error(errorMessage);
      }
    }
Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral details about the return data (alliance, EPA, predicted score components, outcome flags) and parameter requirements. No contradictions.

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 concise (two sentences plus usage example) and front-loaded with the purpose. Every sentence adds value, no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with two parameters and no output schema, the description covers what the tool returns, how to use it, and when to use alternatives. It is complete enough for an agent to select and invoke correctly.

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% and already describes parameters. The description adds clarity by explaining 'team (integer, no prefix)' and providing a match key example ('2024flor_qm20'), which aids agent understanding beyond the schema.

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 uses a specific verb ('Get'), identifies the resource ('single team's contribution to a single FRC match'), and distinguishes from the sibling tool 'get_team_matches' which lists many rows. It clearly states the per-robot view and provides an example query.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('scouting and post-match analysis') and provides an alternative ('For listing many team-match rows, use get_team_matches'). It also specifies required parameters and format.

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/withinfocus/statbotics-mcp-server'

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