Skip to main content
Glama
Hudl Volleyball MCP Server

Hudl Volleyball MCP Server

by onnobos

list_volleyball_matches

Fetch recent volleyball matches for a team to get match IDs, dates, opponents, results, and set scores, then use those IDs for downstream performance analysis.

Instructions

Fetch recent volleyball matches for a team from Hudl.

Returns a table or compact JSON containing match IDs, dates, opponent names, results, and set scores. Call this tool first when a user asks about match results or team performance to discover the appropriate match_id for downstream analysis.

Args: team_id: Optional Hudl team ID. If omitted, uses auto-detected team ID. limit: Maximum number of recent matches to retrieve (default: 10). output_format: Output format: 'markdown' (table) or 'compact' (token-efficient JSON). force_refresh: If True, bypasses local 15-minute disk cache and forces a live fetch.

Returns: A formatted table or compact JSON of matches or an actionable error message.

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": "list_volleyball_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
team_idNo
force_refreshNo
output_formatNomarkdown

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden and does reasonably well: it discloses the 15-minute disk cache and force_refresh bypass, and that team_id is auto-detected when omitted. It doesn't mention authentication or rate-limit behavior, but the cache disclosure is meaningful non-obvious context.

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?

Front-loaded with purpose and usage, then cleanly sectioned into Args and Returns. Slightly long and the Returns line partially duplicates the output schema's role, but no sentence is wasteful.

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 four params at 0% schema coverage and no annotations, the description covers discovery purpose, cache behavior, and all parameter meanings adequately. An output schema exists, so return-value detail is a minor redundancy rather than a gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate and does: all four params are explained with meaning beyond the schema, including output_format's actual values ('markdown'/'compact') and force_refresh's cache relationship. This fully fills the documentation gap.

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 ('Fetch'), resource ('recent volleyball matches for a team'), and source ('from Hudl'). The 'discover the appropriate match_id for downstream analysis' line distinguishes it from siblings like get_match_player_stats and get_rotation_breakdown, which clearly operate downstream.

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?

Explicitly says 'Call this tool first when a user asks about match results or team performance,' giving clear trigger conditions. It implies but never names the alternative downstream tools, so it stops short of explicit when-not guidance.

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