Skip to main content
Glama

get_event_simple

Read-onlyIdempotent

Retrieve a compact FRC event profile (key, name, code, type, location, dates, year) without district, webcast, division, or playoff metadata.

Instructions

Retrieve a reduced FRC event profile (key, name, event_code, type, location, dates, year). Lighter than get_event; use when district, webcast, division, and playoff metadata are not needed.

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_simple' tool. Parses event_key from args, calls TBA API /event/{event_key}/simple, validates response with EventSimpleSchema, returns JSON stringified result.
    case 'get_event_simple': {
      const { event_key } = z.object({ event_key: EventKeySchema }).parse(args);
      const data = await makeApiRequest(`/event/${event_key}/simple`);
      const event = EventSimpleSchema.parse(data);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(event, null, 2),
          },
        ],
      };
    }
  • Input schema for get_event_simple. Accepts an event_key string validated by EventKeySchema (regex pattern for TBA event keys like '2023casj').
    export const GetEventSimpleInputSchema = z.object({
      event_key: EventKeySchema,
    });
  • src/tools.ts:312-318 (registration)
    Tool registration entry for 'get_event_simple' in the tools array. Defines name, description, input schema reference, and read-only annotations.
    {
      name: 'get_event_simple',
      description:
        'Retrieve a reduced FRC event profile (key, name, event_code, type, location, dates, year). Lighter than get_event; use when district, webcast, division, and playoff metadata are not needed.',
      inputSchema: toMCPSchema(GetEventSimpleInputSchema),
      annotations: { ...READ_ONLY_API, title: 'Get FRC Event Details (Simple)' },
    },
Behavior4/5

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

Annotations already indicate readOnlyHint=true, etc. The description adds value by explaining the reduced profile and use case, going beyond what annotations provide.

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?

Single, front-loaded sentence with no filler. Every word contributes to purpose or usage guidance.

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 simple parameter set and no output schema, the description fully covers what the tool does and when to use it.

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 coverage is 100% and the schema description is detailed. The tool description does not add additional meaning to the parameter.

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 specifies the exact fields (key, name, event_code, type, location, dates, year) and contrasts with the heavier get_event, making it distinct and clear.

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?

Explicitly states when to use this tool ('when district, webcast, division, and playoff metadata are not needed'), providing direct guidance on when to choose this over 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