Skip to main content
Glama

get_event

Read-onlyIdempotent

Retrieve a single FRC event's metadata, team statistics, and predictions using its event key. Get details like location, dates, and winner probabilities.

Instructions

Look up a single FIRST Robotics Competition (FRC) event by its event key. Returns metadata (event name, year, week, type, location, dates, district), aggregate EPA stats for participating teams, qualification and playoff status, and Statbotics predictions for the event (e.g. winner probabilities). Event keys follow the format <year><event-code>, e.g. "2024flor" (FLOR = Orlando regional 2024), "2024necmp" (New England district championship 2024), "2024cmptx" (Houston champs 2024). Use this to answer "what happened at 2024flor?", "show predictions for 2024cmptx", or to get context (week, type, location) for an event you have the key for. For browsing events by season, district, or week, use get_events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventYesEvent key, e.g. 2024flor

Implementation Reference

  • The get_event handler: parses input via GetEventInputSchema, calls the Statbotics API at /v3/event/{event}, and returns the event data as JSON.
    case 'get_event': {
      const { event } = GetEventInputSchema.parse(args);
      const data = await makeApiRequest(`/v3/event/${event}`);
      return {
        content: [{ type: 'text', text: JSON.stringify(data, null, 2) }],
      };
    }
  • The GetEventInputSchema Zod schema: validates input with a single required 'event' field of type string (EventKeySchema).
    export const GetEventInputSchema = z.object({
      event: EventKeySchema,
    });
  • src/tools.ts:134-151 (registration)
    The tool registration/definition for 'get_event' in the tools array, including name, description, annotations, and inputSchema.
    {
      name: 'get_event',
      description:
        'Look up a single FIRST Robotics Competition (FRC) event by its event key. ' +
        'Returns metadata (event name, year, week, type, location, dates, district), aggregate EPA stats for ' +
        'participating teams, qualification and playoff status, and Statbotics predictions for the event ' +
        '(e.g. winner probabilities). ' +
        'Event keys follow the format `<year><event-code>`, e.g. "2024flor" (FLOR = Orlando regional 2024), ' +
        '"2024necmp" (New England district championship 2024), "2024cmptx" (Houston champs 2024). ' +
        'Use this to answer "what happened at 2024flor?", "show predictions for 2024cmptx", or to get ' +
        'context (week, type, location) for an event you have the key for. ' +
        'For browsing events by season, district, or week, use get_events.',
      annotations: {
        title: 'Get FRC Event Details (Single Event)',
        ...readOnlyAnnotations,
      },
      inputSchema: toMCPSchema(GetEventInputSchema),
    },
  • The makeApiRequest helper function 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: {
Behavior5/5

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

Annotations already declare readOnly=true, destructive=false, idempotent=true. Description adds details: returns metadata, aggregate EPA stats, qualification/playoff status, and Statbotics predictions, plus explains event key format. 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?

Concise three-sentence structure. First sentence states purpose, second details what is returned, third gives usage examples and alternatives. No unnecessary words.

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?

Given the tool's simplicity (single parameter, no output schema, strong annotations), the description fully covers input format, output contents, and when to choose alternatives. No gaps.

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% with one required parameter 'event'. Description adds value by explaining event key format with examples and meaning, beyond the schema's brief description.

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 verb 'look up', resource 'single FRC event', and method 'by its event key'. It distinguishes from sibling get_events by specifying it's for a single event vs browsing multiple.

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?

Provides explicit when-to-use examples: 'what happened at 2024flor?', 'show predictions', 'get context'. Also gives explicit when-not-to-use and alternative: 'For browsing events by season, district, or week, use get_events'.

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