Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_team_years

Read-only

Get Returns every franchise and the range of seasons it has played, one row per team. Use it as the franchise/season discovery surface before calling nba-franchise-history or nba-team-game-logs; it takes only the optional league id and makes one statistics read. Returns every franchise and the range of seasons it has played, one row per team. Use it as the franchise/season discovery surface before calling nba-franchise-history or nba-team-game-logs; it takes only the optional league id and makes one statistics read.

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": "nba_team_years"
  }
}

Input Schema

NameRequiredDescriptionDefault
league_idNoOptional league id; only 00 (NBA) is verified.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior beyond that: it takes only the optional league id and 'makes one statistics read', telling the agent the call is cheap and single-shot, and it specifies the return granularity as one row per team.

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?

The entire two-sentence description is duplicated verbatim, so roughly half the text is pure waste. The non-duplicated content is front-loaded and tight, but the repetition is a clear structural defect that should be removed.

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?

With an output schema present, a single fully-described parameter, and annotations covering the safety profile, the description supplies what remains: scope, row granularity, call cost, and where it sits in a call sequence. Nothing essential for correct invocation is missing, aside from guidance on using it when a franchise id is already in hand.

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?

Schema coverage is 100% and the single league_id parameter is fully documented in the schema, including the 'only 00 (NBA) is verified' caveat. The description only restates that the league id is optional and does not add format or default semantics, so the schema is doing the work here.

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

Purpose4/5

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

The description names a concrete resource and shape: every franchise plus the range of seasons played, one row per team. The awkward opening 'Get Returns' is a copy artifact, but the intent is still unambiguous, and it distinguishes itself from nba_franchise_history and nba_team_game_logs as a discovery/roster-of-franchises surface rather than a history or log query.

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?

It explicitly positions the tool as the 'franchise/season discovery surface before calling nba-franchise-history or nba-team-game-logs', which gives a clear sequencing rule an agent can act on. It stops short of stating when not to use it (e.g., when a franchise id is already known), so it is strong but not exhaustive.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources