Skip to main content
Glama

Get Team Schedule

get_team_schedule
Read-only

Retrieve a BuzzerBeater team's club schedule, oldest first, with optional season, limit, and offset filters to page through match history.

Instructions

A club schedule, oldest info come first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "team_id": "<team_id>"
    },
    "name": "get_team_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
seasonNo
team_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds one genuine behavioral fact, that results are ordered oldest-first, but says nothing about pagination behavior, season filtering semantics, or how large a schedule can be.

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

Conciseness2/5

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

It is short, but this is under-specification rather than conciseness; the single sentence fragment is grammatically broken ('oldest info come first') and carries almost no information for the space it takes.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but a four-parameter tool with 0% schema coverage needs the description to define season and paging semantics. Nothing about the required team_id or pagination defaults is addressed.

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

Parameters1/5

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

Schema description coverage is 0% for four parameters (team_id, season, limit, offset), and the description explains none of them. An agent must guess what 'season' means (year? season id?) and how limit/offset interact with the stated ordering.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the name as a noun phrase ('A club schedule') without a verb or scope, so it is essentially tautological. The only distinguishing detail is the ordering note, and nothing separates it from siblings such as get_team_training_history or get_team_roster.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no indication of when an agent should pick this over the many other get_team_* tools. The ordering note hints at what the result looks like but says nothing about selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.