Skip to main content
Glama

get_event_matches_keys

Retrieve match keys for a specific FIRST Robotics Competition event to access detailed match data and results.

Instructions

Get match keys for an event

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_keyYesEvent key (e.g., 2023casj)

Implementation Reference

  • The handler case for 'get_event_matches_keys' that validates the event_key input, fetches match keys from the TBA API endpoint `/event/{event_key}/matches/keys`, parses the response as an array of strings, and returns it as JSON text.
    case 'get_event_matches_keys': { const { event_key } = z.object({ event_key: EventKeySchema }).parse(args); const data = await makeApiRequest(`/event/${event_key}/matches/keys`); const keys = z.array(z.string()).parse(data); return { content: [ { type: 'text', text: JSON.stringify(keys, null, 2), }, ], }; }
  • src/tools.ts:797-810 (registration)
    The tool registration entry in the tools array, defining the name, description, and input schema for 'get_event_matches_keys'.
    { name: 'get_event_matches_keys', description: 'Get match keys for an event', inputSchema: { type: 'object', properties: { event_key: { type: 'string', description: 'Event key (e.g., 2023casj)', }, }, required: ['event_key'], }, },
  • Zod schema definition for EventKey used in the handler for input validation.
    export const EventKeySchema = z.string();

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'

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