Skip to main content
Glama

get_team_events

Read-onlyIdempotent

Retrieve FRC team-event records with filters for team, year, event, country, state, district, type, and week. Sort and paginate results to analyze team performance across events.

Instructions

List FIRST Robotics Competition (FRC) team-event records with flexible filters. Each row represents one team's performance at one event (rank, record, EPA, awards). Filter any combination of team (one team across all events), year, event (all teams at one event - great for getting an event's full team list with stats), country, state, district, type (regional, district, district_cmp, champs_div, einstein, offseason), and week (0-8). Sort with metric/ascending and paginate with limit/offset. Use this to answer "show every event team 254 has attended in 2024", "list all teams at 2024flor with their ranks", or "rank teams by EPA across all 2024 district championships".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNoTeam number (no prefix), e.g. 86
yearNoFour-digit year (2002 onwards)
eventNoEvent key, e.g. 2024flor
countryNoCapitalized country name, e.g. USA or Canada.
stateNoCapitalized two-letter state code, e.g. NC.
districtNoDistrict abbreviation. One of: ca, fch, fim, fin, fit, fma, fnc, fsc, isr, ne, ont, pch, pnw, win.
typeNoOne of: regional, district, district_cmp, champs_div, einstein, or offseason.
weekNoWeek of the competition season. 8 is CMP.
metricNoHow to sort the returned values. Any column in the table is valid.
ascendingNoWhether to sort in ascending order. Default is ascending.
limitNoMaximum number of results to return (1-1000). Default is 1000.
offsetNoOffset from the first result to return.

Implementation Reference

  • The handler for 'get_team_events' in the switch statement. It parses args using GetTeamEventsInputSchema, builds a query string from the parsed fields (team, year, event, country, state, district, type, week, metric, ascending, limit, offset), makes a GET request to /v3/team_events with that query string, and returns the JSON result.
    case 'get_team_events': {
      const {
        team,
        year,
        event,
        country,
        state,
        district,
        type,
        week,
        metric,
        ascending,
        limit,
        offset,
      } = GetTeamEventsInputSchema.parse(args);
      const qs = buildQueryString({
        team,
        year,
        event,
        country,
        state,
        district,
        type,
        week,
        metric,
        ascending,
        limit,
        offset,
      });
      const data = await makeApiRequest(`/v3/team_events${qs}`);
      return {
        content: [{ type: 'text', text: JSON.stringify(data, null, 2) }],
      };
    }
  • The Zod input schema for 'get_team_events'. Defines optional fields: team (integer), year (2002+), event (string like '2024flor'), country, state, district, type (event type), week (0-8), plus pagination/sorting fields (metric, ascending, limit, offset).
    export const GetTeamEventsInputSchema = z.object({
      team: TeamNumberSchema.optional().describe(
        'Team number (no prefix), e.g. 86',
      ),
      year: YearSchema.optional().describe('Four-digit year (2002 onwards)'),
      event: EventKeySchema.optional().describe('Event key, e.g. 2024flor'),
      country: CountrySchema,
      state: StateSchema,
      district: DistrictSchema,
      type: EventTypeSchema,
      week: WeekSchema,
      ...PaginationSortFields,
    });
  • src/tools.ts:187-203 (registration)
    The tool registration definition for 'get_team_events'. Declares the tool name, human-readable description explaining usage and filters, annotations marking it read-only/idempotent, and associates it with GetTeamEventsInputSchema for input validation.
    {
      name: 'get_team_events',
      description:
        'List FIRST Robotics Competition (FRC) team-event records with flexible filters. Each row represents ' +
        "one team's performance at one event (rank, record, EPA, awards). " +
        'Filter any combination of `team` (one team across all events), `year`, `event` (all teams at one event - ' +
        "great for getting an event's full team list with stats), `country`, `state`, `district`, " +
        '`type` (regional, district, district_cmp, champs_div, einstein, offseason), and `week` (0-8). ' +
        'Sort with `metric`/`ascending` and paginate with `limit`/`offset`. ' +
        'Use this to answer "show every event team 254 has attended in 2024", "list all teams at 2024flor with their ranks", ' +
        'or "rank teams by EPA across all 2024 district championships".',
      annotations: {
        title: 'List/Search FRC Team-Event Records',
        ...readOnlyAnnotations,
      },
      inputSchema: toMCPSchema(GetTeamEventsInputSchema),
    },
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds crucial detail about output structure (rank, record, EPA, awards), sorting, and pagination. 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?

Every sentence adds unique value: purpose, row definition, filter enumeration, sort/pagination, and example queries. No redundancy, well front-loaded.

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?

With no output schema, description fully explains output structure, all filter options, sorting, pagination limits (1-1000), and includes three concrete example queries, making it self-contained for correct invocation.

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 covers all 12 parameters with descriptions (100% coverage). Description adds value by grouping filters, explaining sort metric flexibility, and providing concrete labeling ('district_cmp', 'week 8 is CMP').

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?

Description clearly states 'List FIRST Robotics Competition (FRC) team-event records with flexible filters' and explains each row represents a team's performance at an event. Examples concretely differentiate from sibling tools like get_team or get_event by emphasizing team-event granularity.

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

Usage Guidelines4/5

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

Provides explicit usage scenarios ('Use this to answer...') and filter combinations. Lacks explicit when-not-to-use or comparison to siblings, but context is clear enough for appropriate selection.

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