Skip to main content
Glama

Stratalize Intelligence

Get Sports Scores Multi

get_sports_scores_multi
Read-only

Cross-sport intelligence brief — live and recent scores across all active leagues (NBA, NFL, MLB, NHL) in a single attested call. Returns only leagues with recent activity. Use when an agent needs sports context without knowing which leagues are in season. Source: TheSportsDB. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.10 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_scores_multi"
  }
}

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 declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely non-obvious behavior beyond that: only leagues with recent activity are returned, the data source is TheSportsDB, and each call costs $0.10 USDC — a cost signal an agent cannot get from annotations. The attestation/verify wording is more promotional than behavioral, which keeps it from 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?

The purpose and usage trigger are front-loaded in the first two sentences, which is the right ordering. However, three trailing sentences cover attestation, a verify URL, and pricing; the pricing matters for selection, but the cryptographic-receipt language is padding relative to the tool's job.

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 zero parameters and no output schema, the burden is light and the description covers scope, source, filtering behavior, and cost. Its one gap is that it never sketches the returned fields (teams, scores, game state), which an agent would otherwise have to discover by calling.

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 the baseline for this dimension is 4. There is nothing for the description to disambiguate, and it correctly implies no input is required by describing the call as a blanket cross-league fetch.

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 — live/recent scores across all active leagues (NBA, NFL, MLB, NHL) — and explicitly frames itself as a single cross-sport call, which distinguishes it from the per-league siblings like get_sports_nba_scores. An agent can tell immediately that this is the aggregate alternative to the league-specific tools.

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?

"Use when an agent needs sports context without knowing which leagues are in season" is an explicit trigger condition that implicitly routes to this tool over the single-league siblings. It lacks a stated when-not-to-use (e.g., 'if you already know the league, use the league-specific tool instead'), so it falls short of a 5.

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