Skip to main content
Glama

get_team_robots

Read-onlyIdempotent

Retrieve a list of robots a team has built and named each year, including year and robot name. Use this to build historical team profiles.

Instructions

List the named robots a team has built and registered each year (e.g., 'Stronghold' for 2016, 'Citrus Circuits Quokka' patterns). Returns robot records with year, robot_name, robot key, and team key. Useful for retrospective profiles and historical references.

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

  • Handler for the 'get_team_robots' tool. Parses args for team_key, makes an API request to /team/{team_key}/robots, validates the response as an array of RobotSchema, and returns the robot data as JSON text.
    case 'get_team_robots': {
      const { team_key } = z.object({ team_key: TeamKeySchema }).parse(args);
      const data = await makeApiRequest(`/team/${team_key}/robots`);
      const robots = z.array(RobotSchema).parse(data);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(robots, null, 2),
          },
        ],
      };
    }
  • RobotSchema defines the shape of each robot record returned by the API: year (number), robot_name (string), key (string), and team_key (string).
    export const RobotSchema = z.object({
      year: z.number(),
      robot_name: z.string(),
      key: z.string(),
      team_key: z.string(),
    });
  • Input schema for get_team_robots: requires only a team_key parameter.
    export const GetTeamRobotsInputSchema = z.object({
      team_key: TeamKeySchema,
    });
  • src/tools.ts:179-185 (registration)
    Registration of the get_team_robots tool in the tools array, with its name, description, input schema (converted via toMCPSchema), and read-only annotations.
    {
      name: 'get_team_robots',
      description:
        "List the named robots a team has built and registered each year (e.g., 'Stronghold' for 2016, 'Citrus Circuits Quokka' patterns). Returns robot records with year, robot_name, robot key, and team key. Useful for retrospective profiles and historical references.",
      inputSchema: toMCPSchema(GetTeamRobotsInputSchema),
      annotations: { ...READ_ONLY_API, title: 'Get Team Robot Names' },
    },
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by specifying the exact fields returned (year, robot_name, robot key, team key) and the nature of the data (named robots per year). No contradictions.

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?

Three sentences with no wasted words. The most important information (what the tool does) is front-loaded, followed by example and return fields. Efficient and structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one parameter and no output schema, the description covers the purpose, return details, and use case adequately. It lacks mention of edge cases (e.g., empty results) but is sufficient for typical use.

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 100% coverage with a detailed description of the team_key parameter. The tool description does not add any additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 tool lists named robots a team has built each year, with specific examples and return fields. It distinguishes from sibling tools by focusing specifically on robot names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions usefulness for retrospective profiles and historical references, which provides some context but does not explicitly compare to alternative tools or specify when to use this tool over others.

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