Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

nba_games

Read-only

Get the NBA games page's embedded game feed from www.nba.com and return the same normalized game shape as nba_scoreboard: id, status, teams, scores and period lines. This is the independent fallback source when stats.nba.com is unreachable; it takes no parameters and reflects the games the website currently shows, so a quiet day returns count 0 with an empty games list rather than an error.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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.7/5.0
Behavior4/5

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

Annotations already give readOnlyHint and openWorldHint, but the description adds genuinely non-obvious behavior: it takes no parameters, it mirrors the live website state rather than a query, and an empty day yields 'count 0 with an empty games list rather than an error'. That empty-versus-error distinction is exactly what an agent needs to avoid misreading a zero result. It stops short of describing failure behavior when the site itself is unreachable, which keeps it off a 5.

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

Conciseness5/5

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

Two sentences, front-loaded with purpose, then fallback condition, then empty-result semantics. No filler, no restatement of the tool name, and the enumeration of returned fields is compact.

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?

For a parameterless, open-world read tool with an output schema already present, the description covers everything material: data source, cross-tool shape compatibility, when to choose it, and how an empty result presents. Nothing an agent needs in order to call it 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?

Zero parameters, so the baseline is 4; the description confirms 'it takes no parameters', which matches the empty schema and prevents an agent from hunting for filter arguments. No additional parameter meaning is possible here.

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 the NBA games page's embedded game feed from www.nba.com') and pins down the return shape ('id, status, teams, scores and period lines'). It explicitly distinguishes itself from the sibling nba_scoreboard by being the 'independent fallback source' with a different upstream origin.

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

Usage Guidelines5/5

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

Names the alternative (nba_scoreboard) and the exact condition that selects this tool instead: 'when stats.nba.com is unreachable'. An agent has a clear decision rule without needing to inspect any other tool's schema.

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