Skip to main content
Glama

Stratalize Intelligence

Get Sports Nfl Scores

get_sports_nfl_scores
Read-only

Live NFL game scores, game status, and results for the past 7 days and next 7 days. Returns teams, scores, and game status. 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_nfl_scores"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely non-obvious facts: upstream data source (TheSportsDB), a per-call price ($0.02 USDC), and an attestation/verification receipt. It does not cover failure modes, latency, or what empty results look like, keeping it below 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.

Conciseness4/5

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

Purpose and coverage window are front-loaded in the first sentence, followed by return values, source, and trust/cost details. There is mild redundancy between 'game scores, game status' and 'Returns teams, scores, and game status', but the attestation and pricing sentences each carry distinct usable 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 input parameters and no output schema, the description carries the return-value burden and does so by naming the returned fields (teams, scores, status) and the temporal coverage. Only the shape of status values and empty-result behavior are left unspecified, which is minor for a simple read tool.

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 no parameter meaning to add and the baseline is 4. Nothing in the description conflicts with the empty input schema.

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+resource (live NFL game scores, game status, results) and a precise scope (past 7 days and next 7 days). The NFL scoping alone separates it cleanly from the mlb/nba/nhl siblings, so an agent can select it from the name plus first sentence without opening anything else.

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?

The 7-day-back / 7-day-forward window effectively defines the usable range, which is real usage guidance by implication. However, there is no explicit when-not statement and no reference to a multi-sport alternative such as get_sports_scores_multi or to the other league-specific siblings, so the agent must infer the routing itself.

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