Skip to main content
Glama

Stratalize Healthcare

Get Sports Mlb Scores

get_sports_mlb_scores
Read-only

Live MLB game scores 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_mlb_scores"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.9/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, and the description adds value beyond them: the data source (TheSportsDB), the returned fields (teams, scores, game status), an attestation mechanism with a verification URL, and a per-call price. That commercial and provenance context is exactly the kind of thing annotations cannot convey. It does not cover error or empty-result behavior, which keeps it short of 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?

Three short sentences, front-loaded with the capability and time window before provenance and pricing. Every sentence carries distinct information, though the attestation/pricing pair reads as boilerplate relative to the retrieval itself.

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 must carry the return-value burden, and it does name the key fields (teams, scores, game status) plus the time window. An agent has enough to decide and call correctly; only edge-case behavior (no games today, rate limits) is absent.

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?

The tool takes zero parameters, so the 4-baseline applies and there is no parameter meaning to add. The description does not need to explain inputs at all, and the schema coverage figure is vacuous with an empty properties object. Nothing is gained or lost here.

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 + resource + scope: 'Live MLB game scores and results for the past 7 days and next 7 days.' The league is named explicitly in both the tool name and description, so an agent can distinguish it from the NBA/NFL/NHL siblings without opening a schema.

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 implicitly defines when this tool is the right choice, but there is no explicit when-to-use guidance and no mention of the multi-sport sibling (get_sports_scores_multi) that an agent might prefer for cross-league queries. Usage is inferable rather than stated.

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