Skip to main content
Glama
Sign In
onnobos

Volleymetrics MCP Server

by onnobos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get User Volleymetrics Teams

get_user_teams
Read-onlyIdempotent

Retrieve all Volleymetrics team profiles and memberships linked to the authenticated account to discover team IDs, names, conferences, roles, and the active team before querying matches or stats.

Instructions

Retrieve all Volleymetrics volleyball team profiles and organization memberships linked to the authenticated account, unlike list_volleyball_matches (which lists match schedules for a single team).

When to Use

  • Discover the user's accessible team_id values, team names, school/club organizations, conferences, and coaching roles at the start of an analysis workflow.

  • Verify which team is currently marked active before calling list_volleyball_matches.

When NOT to Use

  • Do NOT use to search for external opponent teams or public league rosters not tied to the user's account; call list_volleyball_matches to inspect opponents on your match schedule.

  • Do NOT call before every match query once team_id is known, as list_volleyball_matches automatically resolves the active team when team_id is omitted.

Behavioral Guarantees & Caching

  • Execution Contract: Strictly read-only, idempotent HTTPS GET against https://api.volleymetrics.hudl.com.

  • Caching Policy: Cached on local disk (~/.volleymetrics_mcp/cache) with a 15-minute TTL (900s). Set force_refresh=True only after account membership changes.

  • Rate Limiting: Governed by a client-side token bucket (2 req/s, burst capacity 4) with exponential backoff on HTTP 429/5xx.

  • Authentication: Reads Bearer JWT credentials from ~/.volleymetrics_mcp/auth_state.json, OS Keychain, or .env.

Parameter & Workflow Semantics

  • Pass the team_id returned by this tool into list_volleyball_matches, get_match_player_stats, or get_rotation_breakdown when the user coaches multiple squads and wants to switch away from their default active team.

  • Prefer output_format='compact' when chaining team discovery into automated multi-step tool calls to save context tokens.

Returns & Error States

  • 'markdown': Markdown table with columns Team ID, Team Name, School / Club, Conference, Role, and Active.

  • 'compact': JSON object {"active_team_id": str, "count": int, "teams": [{"team_id": str, "name": str, "school_name": str, "conference": str, "role": str, "is_current": bool}]}.

  • On missing or expired credentials (HTTP 401/403), returns an actionable ⚠️ Authentication Error instructing the agent to invoke login_to_volleymetrics.

Input Schema

NameRequiredDescriptionDefault
force_refreshNoWhen True, bypasses the 15-minute local disk cache (~/.volleymetrics_mcp/cache) and forces a live HTTPS GET request to the Volleymetrics user profile endpoint.
output_formatNoResponse representation format: 'markdown' returns a formatted Markdown table for human display; 'compact' returns a token-minimized JSON object for downstream agent chaining.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial context beyond them: an idempotent HTTPS GET contract, a 15-minute disk cache with TTL and when to bypass it, a token bucket with 2 req/s and burst 4 plus backoff on 429/5xx, and credential sources (auth_state.json, Keychain, .env). It also discloses the 401/403 error behavior and the remediation step (invoke `login_to_volleymetrics`).

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 the one-line purpose and a sibling contrast, then cleanly sectioned by usage, behavior, parameters and returns. It is long, and the 'Returns' section partly duplicates the `output_format` enum descriptions already in the schema, but the bulk of the text carries non-redundant operational detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter, zero-required discovery tool with no output schema, the description covers everything an agent needs: what comes back in both formats (with the compact JSON shape), when to call it, when not to, and how auth failures surface. Nothing material is missing.

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?

Schema coverage is 100%, so 3 is the floor, and the description improves on it by giving decision rules rather than restating types: set `force_refresh=True` only after account membership changes, and prefer `output_format='compact'` when chaining team discovery into automated multi-step calls. That adds genuine selection guidance the schema lacks.

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 ('Retrieve all Volleymetrics volleyball team profiles and organization memberships linked to the authenticated account') and immediately contrasts it with `list_volleyball_matches`, which lists match schedules for a single team. An agent can pick between the two 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'When to Use' and 'When NOT to Use' sections name the alternatives (`list_volleyball_matches`) and the exact conditions selecting them, including the nuance that the sibling auto-resolves the active team when `team_id` is omitted. This is about as complete as routing guidance gets.

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