Skip to main content
Glama

get_event_rankings

Read-onlyIdempotent

Retrieve qualification rankings for an FRC event using its event key. Returns ordered team rows with records, scores, and sort criteria to assess performance and seed alliances.

Instructions

Retrieve the live or final qualification rankings for an FRC event. Returns ordered ranking rows (team key, rank, win/loss/tie record, matches played, qualification average, sort orders, extra stats, DQ count) plus metadata describing each sort criterion (e.g., Ranking Points, Auto, Endgame). Used to determine alliance selection order, seed playoff alliances, and assess team performance during qualification matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_keyYesTBA event key combining the season year and event code (e.g., '2023casj' for the 2023 Silicon Valley Regional, '2024txhou' for the 2024 Houston Championship, '2024micmp4' for a Michigan State Championship division). Use get_events or get_events_keys to discover valid event keys for a year.

Implementation Reference

  • The handler function that executes the get_event_rankings tool logic. It parses the event_key from args, makes an API request to /event/{event_key}/rankings, validates the response with RankingSchema, and returns the rankings data as JSON.
    case 'get_event_rankings': {
      const { event_key } = z.object({ event_key: EventKeySchema }).parse(args);
      const data = await makeApiRequest(`/event/${event_key}/rankings`);
      const rankings = RankingSchema.parse(data);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(rankings, null, 2),
          },
        ],
      };
    }
  • RankingSchema - Zod validation schema for the rankings response data, including rankings array (team_key, rank, dq, matches_played, qual_average, record, extra_stats, sort_orders) and metadata (extra_stats_info, sort_order_info).
    export const RankingSchema = z.object({
      rankings: z.array(
        z.object({
          team_key: z.string(),
          rank: z.number(),
          dq: z.number().nullish(),
          matches_played: z.number(),
          qual_average: z.number().nullish(),
          record: z
            .object({
              losses: z.number(),
              wins: z.number(),
              ties: z.number(),
            })
            .nullish(),
          extra_stats: z.array(z.number()).nullish(),
          sort_orders: z.array(z.number()).nullish(),
        }),
      ),
      extra_stats_info: z
        .array(
          z.object({
            name: z.string(),
            precision: z.number(),
          }),
        )
        .nullish(),
      sort_order_info: z
        .array(
          z.object({
            name: z.string(),
            precision: z.number(),
          }),
        )
        .nullish(),
    });
  • GetEventRankingsInputSchema - Zod validation schema for the input, requiring an event_key field.
    export const GetEventRankingsInputSchema = z.object({
      event_key: EventKeySchema,
    });
  • src/tools.ts:127-136 (registration)
    Registration of the get_event_rankings tool in the tools array with its name, description, inputSchema, and annotations.
    {
      name: 'get_event_rankings',
      description:
        'Retrieve the live or final qualification rankings for an FRC event. Returns ordered ranking rows (team key, rank, win/loss/tie record, matches played, qualification average, sort orders, extra stats, DQ count) plus metadata describing each sort criterion (e.g., Ranking Points, Auto, Endgame). Used to determine alliance selection order, seed playoff alliances, and assess team performance during qualification matches.',
      inputSchema: toMCPSchema(GetEventRankingsInputSchema),
      annotations: {
        ...READ_ONLY_API,
        title: 'Get Event Qualification Rankings',
      },
    },
  • src/tools.ts:11-11 (registration)
    Import of GetEventRankingsInputSchema used for tool registration.
    GetEventRankingsInputSchema,
Behavior5/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds transparency by detailing the returned data: ordered ranking rows with specific stats (win/loss/tie, matches played, DQ count, etc.) and metadata about sort criteria. No contradiction.

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?

Two sentences with no wasted words. The first sentence efficiently states purpose and return type; the second provides usage context. Front-loaded with key information.

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 read-only tool with one parameter and no output schema, the description is complete. It explains what the tool returns (ranking rows and metadata) and its typical usage, leaving no gaps given the tool's complexity.

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 description coverage is 100%, so the schema already documents the single parameter 'event_key' well. The description adds no new parameter semantics; it only references 'live or final' which relates to output, not input. Baseline score of 3 is appropriate.

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 verb 'retrieve' and the resource 'live or final qualification rankings for an FRC event'. It distinguishes from sibling tools (e.g., get_event_matches, get_event_oprs) by focusing specifically on rankings.

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?

The description explains when to use the tool: 'to determine alliance selection order, seed playoff alliances, and assess team performance during qualification matches'. It provides clear context but does not explicitly mention when not to use it or suggest alternatives.

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

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