Skip to main content
Glama

Stratalize Intelligence

Get Sports Nba Scores

get_sports_nba_scores
Read-only

Live NBA scores, game status, and results for the past 7 days and next 7 days. Returns home/away teams, scores, game status (live, final, upcoming), and league/season context. Source: TheSportsDB. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, and non-destructive status, so the bar is lower; the description still adds the upstream source (TheSportsDB), a per-call cost ($0.02 USDC), and a signed receipt with a verification URL. Cost and provenance are real behavioral facts an agent cannot infer from the annotations, though the attestation sentence is partly promotional.

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 what the tool returns and how far the window extends; the source, price, and verification details follow in a compact block. The 'cryptographically attested with a post-quantum signed settlement receipt' phrasing is heavier than needed but still carries payment/trust information.

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?

With no output schema, the description correctly enumerates the returned fields (home/away teams, scores, status, league/season context). Nothing needed to invoke a zero-parameter tool is missing, though response shape and pagination/volume are not specified.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond confirming it is a fixed-window, filterless call. That baseline holds with no compensating need.

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?

The description opens with a specific verb-and-resource pairing ('Live NBA scores, game status, and results') and scopes it to a concrete window (past 7 days, next 7 days). The NBA qualifier alone makes it distinguishable from the MLB/NFL/NHL siblings without opening any 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?

The stated 7-day-back / 7-day-forward window tells the agent exactly what data is reachable, which is usable routing guidance. It does not explicitly name get_sports_scores_multi as the cross-league alternative or state exclusions, so the alternative's role is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources