Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_franchise_history

Read-only

Get NBA franchise history, including defunct teams. Returns every franchise's history as two tables: FranchiseHistory for active franchises and DefunctTeams for the ones that no longer play. Verified columns are TEAM_ID, TEAM_NAME, START_YEAR, END_YEAR, YEARS and GAMES. The table is league-wide and needs no team id; pass team_id only to narrow it.

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_franchise_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idNoOptional team id from nba-standings; narrows the history to that franchise.
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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is to add context, which it does: it discloses that results come back as two separate tables and enumerates the verified column set (TEAM_ID, TEAM_NAME, START_YEAR, END_YEAR, YEARS, GAMES). It also flags that only league 00 is verified, a useful caveat for an open-world tool. It does not discuss row counts, ordering, or empty-result behavior.

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

Conciseness4/5

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

Four short sentences, front-loaded with purpose and output shape before the calling guidance. Slight redundancy between "the table is league-wide and needs no team id" and "pass team_id only to narrow it," but nothing is wasted.

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

Completeness5/5

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

An output schema exists, yet the description still usefully names the two returned tables and the verified columns, and it covers the only real decision (whether to pass team_id). For a two-optional-parameter read tool, nothing an agent needs is missing.

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%, so both parameters are already documented, and the description largely restates the schema's meaning for team_id (optional narrowing) and league_id (only 00 verified). It adds the useful framing that the underlying table is league-wide, but no new syntax or value detail beyond the schema.

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?

States a specific verb and resource ("Get NBA franchise history") and immediately scopes it with "including defunct teams," which is exactly what separates it from team- or player-oriented siblings like nba_common_all_players. The mention of two named result tables (FranchiseHistory, DefunctTeams) makes the output shape unambiguous.

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?

Gives clear operational guidance: the table is league-wide, no team id is required, and team_id should be passed "only to narrow it." That tells the agent how to call it in the default case versus the filtered case. It stops short of naming an alternative tool or a when-not-to-use condition, so it is not a full 5.

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