Skip to main content
Glama

LazyEdge

NBA hit rates

nba_hit_rates
Read-only

How often an NBA player has gone over a line: his recent game log for a stat, his averages, and with a line how many of his last 5, last 10 and season games went over it.

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": {
      "player": "<player>"
    },
    "name": "nba_hit_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineNoCount the games over this line.
statNo
gamesNo
playerYesThe player's name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value beyond that by disclosing the shape of the result: recent game log, averages, and over-counts for multiple time windows, which is important since no output schema exists.

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?

One dense but front-loaded sentence with no filler; the returned content is enumerated in a scannable order (game log, averages, over-counts). It is slightly clause-heavy, but every clause carries information.

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?

For a four-parameter tool with no output schema, the description does well on return content, but leaves gaps: what games controls, what happens when line is omitted (just averages and log?), and what stat defaults to. Those omissions matter for correct invocation.

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 50%: line and player are documented in the schema, while stat (enum) and games have no descriptions. The description compensates partly by explaining that line drives the over-count across 5/10/season windows and that stat selects the game log, but the games parameter is never explained and its interaction with the fixed last-5/last-10/season framing is left ambiguous.

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 resource and computation: an NBA player's game log for a stat, his averages, and the count of last-5, last-10 and season games over a line. The agent can tell this is a hit-rate/prop-history tool rather than a props listing or game feed, though no sibling (e.g. nba_props) is named to sharpen the boundary.

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 only implied: you'd call it to check how often a player cleared a line. The phrase 'with a line how many of his last 5, last 10 and season games went over it' hints that supplying line changes the output, but there is no explicit when-to-use, when-not-to-use, or alternative named.

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