Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nba_playoff_picture

Fetch the current NBA playoff picture by conference as East and West tables with team, conference, and clinched status to track postseason positioning.

Instructions

NBA playoff picture by conference. Returns the current playoff picture as two tables, EastConfPlayoffPicture and WestConfPlayoffPicture. Verified columns are TEAM_ID, CONFERENCE and CLINCHED; the upstream sends more columns than were confirmed here (the sampled PLAYOFF_RANK column name did not match the response) and any extras are passed through as-is.

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

Input Schema

NameRequiredDescriptionDefault
league_idNoLeague id; only 00 (NBA) is verified
season_idNoFive-digit season id such as 22026; defaults to the current season

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the two-table return shape, the verified column set (TEAM_ID, CONFERENCE, CLINCHED), and critically warns that additional unverified columns are passed through and that at least one sampled column name (PLAYOFF_RANK) did not match. That is the kind of instability warning an agent cannot get from structured fields. It does not discuss permissions, freshness/caching, or error 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?

Front-loaded with purpose and return shape, then the reliability caveat. Mostly tight, though the parenthetical about the PLAYOFF_RANK sample mismatch is wordy relative to its importance.

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?

No output schema exists, so the description must describe return values, and it does so with concrete table names and confirmed columns. With no annotations it also covers the read-only nature implicitly via 'Returns' and flags upstream schema drift; only permission or freshness details are missing, which are minor for this tool.

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 both parameters (league_id with enum '00', season_id) are fully documented in the schema, including the default-to-current-season behavior. The description adds no parameter-level 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?

States a specific resource (NBA playoff picture by conference) and goes further by naming the two returned tables, EastConfPlayoffPicture and WestConfPlayoffPicture, so the agent knows exactly what comes back. It never names a sibling (e.g. yahoo_sports_playoff_bracket) to distinguish itself, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the word 'current' signals this is for live standings, not historical or bracket data. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling such as the playoff bracket tool.

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