Skip to main content
Glama

get_event_awards

Read-onlyIdempotent

Get a complete list of awards for any FRC event, with details on each award's name, type, recipient team, and individual awardee. Use an event key to access results after the ceremony.

Instructions

List every award given out at a specific FRC event. Returns each award's name, type code, recipient team key, awardee name (for individual honors like Woodie Flowers Finalist or Dean's List), and year. Available once awards ceremony has concluded.

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

  • Handler for 'get_event_awards' tool. Parses event_key from args, fetches /event/{event_key}/awards via API, validates with AwardSchema array, and returns JSON-stringified awards content.
    case 'get_event_awards': {
      const { event_key } = z.object({ event_key: EventKeySchema }).parse(args);
      const data = await makeApiRequest(`/event/${event_key}/awards`);
      const awards = z.array(AwardSchema).parse(data);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(awards, null, 2),
          },
        ],
      };
    }
  • Input schema for get_event_awards: takes a single event_key string validated by EventKeySchema.
    export const GetEventAwardsInputSchema = z.object({
      event_key: EventKeySchema,
    });
  • AwardSchema - the Zod schema used to parse and validate each award object from the API response.
    export const AwardSchema = z.object({
      name: z.string(),
      award_type: z.number(),
      event_key: z.string(),
      recipient_list: z.array(
        z.object({
          team_key: z.string().nullish(),
          awardee: z.string().nullish(),
        }),
      ),
      year: z.number(),
    });
  • src/tools.ts:228-234 (registration)
    Tool registration entry for 'get_event_awards' with name, description, inputSchema (GetEventAwardsInputSchema), and annotations.
    {
      name: 'get_event_awards',
      description:
        "List every award given out at a specific FRC event. Returns each award's name, type code, recipient team key, awardee name (for individual honors like Woodie Flowers Finalist or Dean's List), and year. Available once awards ceremony has concluded.",
      inputSchema: toMCPSchema(GetEventAwardsInputSchema),
      annotations: { ...READ_ONLY_API, title: 'List Awards at an Event' },
    },
Behavior3/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds the timing constraint (after ceremony) but does not elaborate on other behaviors like pagination or rate limits. This matches the baseline where annotations carry most of the burden.

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 two sentences: the first states purpose and return fields, the second adds timing. Every word is necessary, no fluff, and front-loaded with essential 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?

Given the single parameter, no output schema, and annotations covering safety, the description sufficiently explains what the tool returns and when to use it, making it complete for an agent to use correctly.

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?

The input schema has full coverage (100%) with a detailed description for event_key. The tool description does not add any new information about the parameter beyond what the schema already provides, so the baseline score of 3 applies.

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 'list' and resource 'awards at a specific FRC event', and enumerates the returned fields (name, type code, etc.), making it distinct from sibling tools like get_team_awards or other get_event_* tools.

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 explicitly says 'Available once awards ceremony has concluded', indicating when to use the tool. It does not mention alternatives or when not to use, but the context is sufficiently clear for an agent.

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