Fetch current NBA scores from ESPN to check game results and updates.
Get current NBA scores from ESPN.
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": "espn_nba_scores"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is fully covered. The description adds essentially nothing beyond them — no indication of whether results are live-updating, how fresh they are, or whether it is a snapshot of one day's games.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short sentence, front-loaded with the verb and resource, with zero filler. Nothing in it is redundant or padded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a no-parameter read tool whose annotations carry the safety profile, the essentials are present, but 'current' is undefined and the overlap with nba_games is unaddressed. An agent can invoke it, but cannot predict whether it will get live scores or a finished-games summary.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters and the schema is empty with 100% coverage, so there is nothing for the description to disambiguate. A baseline 4 applies; a small deduction is warranted because the description never signals that no team/date filtering is possible, which an agent might otherwise assume.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource (get NBA scores) plus the source (ESPN), which separates it from the NFL/MLB/NHL/soccer siblings by sport. However, it does not distinguish itself from the non-ESPN sibling nba_games, which plausibly does the same thing, so the differentiation is only partial.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this versus nba_games, or versus espn_news/espn_team_info in the same family. It also never defines 'current' (live in-progress scores? today's finals? latest completed games), which is exactly the decision an agent needs to make before calling.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.