Skip to main content
Glama

get_teams

Read-onlyIdempotent

List FRC teams with filters by country, state, district, and active status. Sort by metrics like EPA or win rate, and paginate results to find top teams.

Instructions

List FIRST Robotics Competition (FRC) teams from the Statbotics database with optional filters. Returns an array of team profiles (number, name, location, rookie year, active flag, career EPA stats, career win rate). Filter by country (e.g. "USA", "Canada"), state (two-letter code, e.g. "NC", "CA"), district (one of ca, fch, fim, fin, fit, fma, fnc, fsc, isr, ne, ont, pch, pnw, win), and active (true to limit to teams that competed in the last year). Sort with metric/ascending (e.g. metric="norm_epa", ascending=false to find the strongest active teams) and paginate with limit/offset. Use this to answer "which teams in Texas are most successful?", "list all teams in the FIM district", or "find the top 50 teams by normalized EPA".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoCapitalized country name, e.g. USA or Canada.
stateNoCapitalized two-letter state code, e.g. NC.
districtNoDistrict abbreviation. One of: ca, fch, fim, fin, fit, fma, fnc, fsc, isr, ne, ont, pch, pnw, win.
activeNoWhether the team has played in the last year.
metricNoHow to sort the returned values. Any column in the table is valid.
ascendingNoWhether to sort in ascending order. Default is ascending.
limitNoMaximum number of results to return (1-1000). Default is 1000.
offsetNoOffset from the first result to return.

Implementation Reference

  • The handler for 'get_teams' tool. Parses input (country, state, district, active, metric, ascending, limit, offset) using GetTeamsInputSchema, builds a query string from the parsed params, and makes an API GET request to /v3/teams with the query string.
    case 'get_teams': {
      const {
        country,
        state,
        district,
        active,
        metric,
        ascending,
        limit,
        offset,
      } = GetTeamsInputSchema.parse(args);
      const qs = buildQueryString({
        country,
        state,
        district,
        active,
        metric,
        ascending,
        limit,
        offset,
      });
      const data = await makeApiRequest(`/v3/teams${qs}`);
      return {
        content: [{ type: 'text', text: JSON.stringify(data, null, 2) }],
      };
    }
  • Zod schema for get_teams input validation. Defines optional fields: country (string), state (string), district (string), active (boolean), plus pagination/sorting fields (metric, ascending, limit, offset).
    export const GetTeamsInputSchema = z.object({
      country: CountrySchema,
      state: StateSchema,
      district: DistrictSchema,
      active: ActiveSchema,
      ...PaginationSortFields,
    });
  • src/tools.ts:81-99 (registration)
    Registration of the 'get_teams' tool as a Tool object. Contains the name 'get_teams', a detailed description explaining how to list/search FRC teams with optional filters, annotations marking it as read-only/idempotent, and the inputSchema derived from GetTeamsInputSchema.
    {
      name: 'get_teams',
      description:
        'List FIRST Robotics Competition (FRC) teams from the Statbotics database with optional filters. ' +
        'Returns an array of team profiles (number, name, location, rookie year, active flag, career EPA stats, ' +
        'career win rate). ' +
        'Filter by `country` (e.g. "USA", "Canada"), `state` (two-letter code, e.g. "NC", "CA"), ' +
        '`district` (one of ca, fch, fim, fin, fit, fma, fnc, fsc, isr, ne, ont, pch, pnw, win), ' +
        'and `active` (true to limit to teams that competed in the last year). ' +
        'Sort with `metric`/`ascending` (e.g. metric="norm_epa", ascending=false to find the strongest active teams) ' +
        'and paginate with `limit`/`offset`. ' +
        'Use this to answer "which teams in Texas are most successful?", "list all teams in the FIM district", ' +
        'or "find the top 50 teams by normalized EPA".',
      annotations: {
        title: 'List/Search FRC Teams',
        ...readOnlyAnnotations,
      },
      inputSchema: toMCPSchema(GetTeamsInputSchema),
    },
Behavior4/5

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

Annotations already declare readOnlyHint=true, so no contradiction. Description adds value beyond annotations by detailing return fields (number, name, location, etc.) and filter semantics (e.g., active filter limits to teams in last year). Could mention rate limits or data freshness, but overall good.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph, front-loaded with purpose, then details filters and examples. Every sentence adds value; could be slightly more concise but clear and well-structured. 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?

No output schema, so description fully compensates by explicitly listing return fields. All 8 parameters are explained with usage examples. Covers filtering, sorting, and pagination. Complete for a list/search tool with good annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant context: provides example values for country/state, lists all district options, explains how metric/ascending work with a concrete example, and clarifies pagination with limit/offset. This goes well beyond the schema descriptions.

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 'List FIRST Robotics Competition (FRC) teams from the Statbotics database with optional filters,' using a specific verb and resource. It distinguishes from sibling tools like get_team by focusing on listing multiple teams with filters.

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?

Provides explicit example queries ('which teams in Texas are most successful?') that guide when to use this tool. Does not explicitly exclude single-team lookup, but sibling context implies it. The examples are clear and actionable.

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