Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nba_standings

Fetch the full NBA standings table for a season and season type, returning one row per team with wins, losses, win percentage, playoff rank, streak, and clinched flag.

Instructions

NBA standings for a season and season type. Returns the standings table for one season and season type: one row per team with team id, city, name, slug, conference, division, wins, losses, win percentage, playoff rank, streak, conference record and clinched flag. Western/Eastern conference and division are columns rather than parameters, so one call returns the whole league and callers split on them.

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

Input Schema

NameRequiredDescriptionDefault
seasonNoSeason in YYYY-YY form; defaults to the current NBA season
league_idNoLeague id; only 00 (NBA) is verified
season_typeNoSeason type; Regular Season or Playoffs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does disclose the important behavior: the tool returns the full league table rather than a filtered subset, and it lists the returned fields (team id, city, name, slug, conference, division, W/L, win pct, playoff rank, streak, conference record, clinched). It omits edge behavior such as what happens for Pre Season or All Star types, which is a minor gap for a read-only standings endpoint.

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?

Front-loaded with purpose, followed by return shape, then the conference/division clarification. Two sentences with no filler, though the field enumeration is dense and slightly long; it still earns its place given there is no output schema.

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?

With no output schema and no annotations, the description supplies the return contract, the column-level schema of results, default season behavior is covered by the input schema, and the no-filter constraint is stated. Nothing material an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning the schema does not: conference and division are deliberately not parameters. That clarification prevents a caller from expecting or searching for a filtering parameter that does not exist.

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?

Names a specific verb+resource (NBA standings) and pins the exact scope: one season and one season type. The second sentence enumerates the returned row shape, so an agent knows precisely what this tool produces before opening the schema.

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 real usage guidance: Eastern/Western conference and division are columns, not parameters, so a single call covers the whole league and callers split client-side. That prevents an agent from attempting per-conference calls. It stops short of naming when to prefer another standings tool, but the within-tool guidance is explicit.

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