Skip to main content
Glama

Get Seasons

get_seasons
Read-only

Retrieve BuzzerBeater seasons in chronological order, oldest first, with optional limit and offset controls for paging through results.

Instructions

Seasons, oldest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_seasons"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered structurally. The description adds one genuine behavioral fact beyond that — results come back oldest first — but says nothing about pagination defaults, total count, or whether the full list is returned when limit is null.

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

Conciseness3/5

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

Four words with zero waste and the ordering fact is front-loaded, which is good. But the brevity crosses into under-specification: there is no structure beyond a fragment, and no sentence carries the pagination or scope information the tool needs.

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, which lowers the bar. Even so, a paginated list tool with two undocumented parameters deserves at least a note on paging behavior and on how many seasons typically exist — neither is present.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the description must carry the burden and it does not: limit and offset are never mentioned, and their default null behavior is unexplained. An agent must guess whether offset is an item count or a page number and what happens at the boundaries.

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

Purpose3/5

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

"Seasons, oldest first" names the resource and its ordering but supplies no verb of its own; the action is only inferable from the tool name get_seasons. It does distinguish the output ordering, which no sibling name suggests, but an agent gets no statement of what a "season" object represents here.

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 at all: nothing says when an agent should fetch seasons versus using a sibling that may embed season data, and no prerequisites or exclusions are given. The only usable cue is the ordering, which implies a reference/lookup list.

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