Skip to main content
Glama
Sign In
hudl-mcp-server

hudl-mcp-server

by nick-graves
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_game_results

Retrieve game-by-game results with opponent, date, score, home/away, and win/loss/tie outcome. Filter by season or limit results.

Instructions

Get game-by-game results: opponent, date, score, home/away, and win/loss/tie outcome.

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_game_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of games to return. Omit for all games.
seasonNoSeason identifier. Defaults to current season.
refreshNoSet true to bypass cache and re-fetch from Hudl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It indicates it's a read operation ('Get') and hints at caching via the 'refresh' parameter, but does not disclose authentication needs, rate limits, or whether results are ordered. Adequate but minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the purpose and lists the result fields. No unnecessary words or redundancy.

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?

Given no output schema, the description partially compensates by listing the output fields. It covers the core results but omits details on pagination or ordering (though 'limit' parameter exists). Fairly complete for a simple list tool.

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 description coverage is 100% (all three parameters have descriptions in the input schema). The tool description does not add meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states the verb 'Get' and the resource 'game-by-game results'. It lists the fields returned (opponent, date, score, home/away, win/loss/tie), distinguishing it from sibling tools like get_box_score or get_game_stats which are likely more detailed.

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 description implies usage for basic game results but does not explicitly state when to use this tool versus alternatives (e.g., get_box_score for detailed stats). No exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools