Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nba_team_info_common

Retrieve an NBA team's identity, conference, division, win/loss record, per-game averages, and available seasons by team ID for a chosen season or season type.

Instructions

Returns one team's identity and season summary: city, name, abbreviation, code, conference and division, the win/loss record and per-game team averages, plus the team's available seasons. Returns one team's identity and season summary: city, name, abbreviation, code, conference and division, the win/loss record and per-game team averages, plus the team's available seasons.

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

Input Schema

NameRequiredDescriptionDefault
seasonNoOptional season in YYYY-YY form; defaults to the current NBA season.
team_idYesRequired team id from nba-standings.
league_idNoOptional league id; only 00 (NBA) is verified.
season_typeNoOptional season type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does useful work by disclosing the return payload (identity fields, record, per-game averages, available seasons), which signals a read-only lookup. However, it says nothing about permission/auth needs, whether unknown team_id values error or return empty, how the season default resolves, or whether the payload is paginated.

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 single sentence is repeated verbatim twice, which is pure waste and pushes the actual content back rather than front-loading it. The underlying content is a reasonably tight enumeration of returned fields, but the duplication badly damages structure.

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

Completeness3/5

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

There is no output schema, so describing the return fields is genuinely necessary and is done here. With four parameters (two enum-constrained) and rich sibling competition, though, the definition leaves out any routing guidance and any note on failure modes or season scoping, so it is only minimally complete for this complexity.

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 description coverage is 100%: team_id, season, league_id, and season_type are all documented in the schema, including the enum restrictions and the season default. The description adds no additional parameter meaning beyond that, so the baseline of 3 applies.

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 specific verb and resource ("Returns one team's identity and season summary") and enumerates the returned fields: city, name, abbreviation, code, conference, division, record, per-game averages, and available seasons. That is far more specific than a restatement of the name. It stops short of a 5 because it never distinguishes itself from near-neighbors like nba_team_details, nba_team_stats, or nba_team_years.

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 or when-not-to-use guidance anywhere in the text. An agent cannot tell from this description whether to pick it over nba_team_details or nba_team_stats for team metadata, or over nba_team_years for the season list. Usage is only implied by the word "info" in the tool name.

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

Deploy Server

Other Tools