Skip to main content
Glama
withinfocus

tba

by withinfocus
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

get_status

Read-onlyIdempotent

Check The Blue Alliance API status: current season, max season, datafeed health, down event keys, team page index, and mobile app versions. Useful for verifying API health and season bounds before other queries.

Instructions

Retrieve TBA API status: current FRC season, max season available, datafeed health flag, list of currently down event keys, max team page index, and minimum/latest mobile app versions for iOS and Android. Useful for sanity-checking the API, discovering season bounds, and detecting outages before issuing other queries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/handlers.ts:319-330 (handler)
    Handler that executes the get_status tool logic: calls TBA /status API, parses response with StatusSchema, and returns formatted JSON text.
    case 'get_status': {
  const data = await makeApiRequest('/status');
  const status = StatusSchema.parse(data);
  return {
    content: [
      {
        type: 'text',
        text: JSON.stringify(status, null, 2),
      },
    ],
  };
}
  • src/schemas.ts:292-306 (schema)
    Zod schema for the API status response, defining the shape including season data, datafeed flags, mobile app versions, and max team page.
    export const StatusSchema = z.object({
  current_season: z.number(),
  max_season: z.number(),
  is_datafeed_down: z.boolean(),
  down_events: z.array(z.string()),
  ios: z.object({
    latest_app_version: z.number(),
    min_app_version: z.number(),
  }),
  android: z.object({
    latest_app_version: z.number(),
    min_app_version: z.number(),
  }),
  max_team_page: z.number(),
});
  • src/schemas.ts:587-587 (schema)
    Input schema for get_status - takes no parameters (empty object).
    export const GetStatusInputSchema = z.object({});
  • src/tools.ts:207-213 (registration)
    Registration of the get_status tool in the tools array with metadata, description, and input schema binding.
    {
  name: 'get_status',
  description:
    'Retrieve TBA API status: current FRC season, max season available, datafeed health flag, list of currently down event keys, max team page index, and minimum/latest mobile app versions for iOS and Android. Useful for sanity-checking the API, discovering season bounds, and detecting outages before issuing other queries.',
  inputSchema: toMCPSchema(GetStatusInputSchema),
  annotations: { ...READ_ONLY_API, title: 'Get TBA API Status' },
},

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value by listing the specific output fields, but does not cover auth or rate limits.

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?

Two concise sentences: first enumerates fields, second gives usage context. No wasted words, front-loaded with action and resource.

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?

Given no output schema, the description adequately lists return fields. Could include structure hint, but for a simple status tool it is complete enough.

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

Parameters4/5

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

No parameters exist; schema coverage is 100%. Baseline for 0 params is 4, and description does not contradict or omit anything.

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 retrieves TBA API status and lists the specific fields included (season, health flag, etc.), distinguishing it from sibling tools that fetch resource data.

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?

The description explicitly advises using this tool for 'sanity-checking the API, discovering season bounds, and detecting outages before issuing other queries,' providing clear when-to-use context.

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