Skip to main content
Glama

get_team_districts

Read-onlyIdempotent

Get district affiliations an FRC team has held over the years, showing year, district key, and name.

Instructions

List the FRC district affiliations a team has held across its history. Returns district records (abbreviation, display name, district key, year). Useful for tracking when a team participated in district play (FIRST in Michigan, New England, Chesapeake, Pacific Northwest, FIRST In Texas, etc.) versus open regional competition, and for analyzing a team's geographic competition history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_keyYesFRC team key formatted as 'frc' followed by the team number with no leading zeros (e.g., 'frc86', 'frc254', 'frc1114'). Uniquely identifies a FIRST Robotics Competition team on The Blue Alliance.

Implementation Reference

  • Case handler for 'get_team_districts' tool. Parses team_key from args, calls TBA API /team/{team_key}/districts, validates response with DistrictSchema array, and returns the district data as JSON.
    case 'get_team_districts': {
      const { team_key } = z.object({ team_key: TeamKeySchema }).parse(args);
      const data = await makeApiRequest(`/team/${team_key}/districts`);
      const districts = z.array(DistrictSchema).parse(data);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(districts, null, 2),
          },
        ],
      };
    }
  • Input schema for get_team_districts: requires team_key (string matching frcXXXX format).
    export const GetTeamDistrictsInputSchema = z.object({
      team_key: TeamKeySchema,
    });
  • DistrictSchema: defines the shape of a district object (abbreviation, display_name, key, year). Used both by get_team_districts and get_districts handlers.
    export const DistrictSchema = z.object({
      abbreviation: z.string(),
      display_name: z.string(),
      key: z.string(),
      year: z.number(),
    });
  • src/tools.ts:172-177 (registration)
    Tool registration for 'get_team_districts' with description, inputSchema (GetTeamDistrictsInputSchema), and read-only annotations.
    {
      name: 'get_team_districts',
      description:
        "List the FRC district affiliations a team has held across its history. Returns district records (abbreviation, display name, district key, year). Useful for tracking when a team participated in district play (FIRST in Michigan, New England, Chesapeake, Pacific Northwest, FIRST In Texas, etc.) versus open regional competition, and for analyzing a team's geographic competition history.",
      inputSchema: toMCPSchema(GetTeamDistrictsInputSchema),
      annotations: { ...READ_ONLY_API, title: 'Get Team District History' },
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds value by disclosing that the tool returns historical data (across team's history) and lists the specific fields (abbreviation, display name, district key, year). No contradictions with annotations.

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?

Description is two sentences, front-loaded with the action and resource, and uses concise language. Every sentence adds value: first states what it does, second explains its utility. No wasted 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 is simple (1 required parameter, no output schema), the description is complete. It explains the purpose, return fields, and use cases. No gaps. Output schema lacking is compensated by listing fields in description.

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% for the single parameter team_key, so the description does not need to add parameter details. It does not provide extra semantics beyond the schema description, which is adequate. Baseline 3.

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 the tool lists FRC district affiliations a team has held across its history, specifying the return fields. It distinguishes itself from sibling tools like get_district_teams (lists teams in a district) and get_team_events (lists events). Action verb 'List' plus resource 'district affiliations' is specific.

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?

Description provides context for when to use the tool (tracking district play participation and analyzing geographic competition history). It implies usage scenarios but does not explicitly state when not to use it or name alternatives. Still, the guidance is clear and helpful.

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