Volleymetrics MCP Server

Overview Schema Source Related Servers Discussions Admin

Download Match DataVolley (.dvw) File

download_match_dvw

Idempotent

Export and save a match's official raw DataVolley (.dvw) scouting file to local disk for import into external analysis software.

Instructions

Export and save the official raw DataVolley (.dvw) scouting file for a match to the local filesystem for external analysis software, unlike get_game_actions (which returns parsed touch events directly in the conversation).

When to Use

Save an authentic .dvw file ([3DATAVOLLEYSCOUT] format) to disk for import into DataVolley 4, VolleyStation, Click&Scout, or OpenVolley / R / Python (datavolley) pipelines.
Archive raw match scouting files locally.

When NOT to Use

Do NOT use when you only need to analyze player stats, rotations, or touches inside the chat; call get_match_player_stats, get_rotation_breakdown, or get_game_actions instead to avoid unnecessary filesystem writes.
Do NOT call if has_dvw is False in list_volleyball_matches.

Behavioral Guarantees & Filesystem Policy

Side Effects: Remote Volleymetrics interaction is strictly read-only (GET), but this tool writes a local file named match_<match_id>.dvw inside output_dir (hence readOnlyHint=False, destructiveHint=False, idempotentHint=True).
Path Sanitization: Strips unsafe characters from match_id and resolves output_dir via Path.expanduser().resolve() to prevent path traversal.
Fallback Generation: If the native .dvw endpoint returns plain JSON events, automatically synthesizes a standards-compliant .dvw file containing match metadata and [3SCOUT] codes.
Rate Limiting: Client token bucket (2 req/s, burst 4) with automatic retry.

Parameter & Workflow Semantics

Acquire match_id from list_volleyball_matches first; pass an explicit output_dir when organizing exports for a specific opponent or tournament folder.

Returns & Error States

Returns a Markdown confirmation containing Match ID, resolved absolute Local File path, and File Size in bytes.
Returns validation error if match_id is empty, or ⚠️ Authentication Error on HTTP 401/403.

Input Schema

Name	Required	Description	Default
`match_id`	Yes	Unique Volleymetrics match identifier obtained from list_volleyball_matches.
`output_dir`	No	Optional local directory path where the exported match_<match_id>.dvw file will be saved. When omitted or None, writes to the current working directory.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the local write side effect and resulting filename pattern, path sanitization via expanduser/resolve, a fallback that synthesizes a compliant .dvw from JSON events, token-bucket rate limits (2 req/s, burst 4) with retry, and 401/403 error behavior. The annotations only declare the safety flags; the description explains what actually happens on disk and over the network.

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 core purpose, then cleanly sectioned under headers, so an agent can scan to the relevant block. Slightly over-long, and the parenthetical restating `readOnlyHint=False, destructiveHint=False, idempotentHint=True` duplicates structured annotation data rather than adding to it.

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?

Covers the full lifecycle an agent needs for a file-writing export tool: precondition, parameters, side effects, failure modes, and the exact shape of the Markdown confirmation (Match ID, absolute path, file size). Nothing material is missing even though there is no output schema.

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 the baseline is 3; the description earns extra credit by adding workflow provenance for `match_id` (acquire from `list_volleyball_matches` first) and intent guidance for `output_dir` (organize by opponent or tournament folder). It does not add format constraints or edge cases for the path beyond what the schema already documents.

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 ('Export and save the official raw DataVolley (.dvw) scouting file') and immediately contrasts it with the sibling `get_game_actions`, which returns parsed events instead of a file. The agent can distinguish this tool from every sibling 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?

Provides explicit 'When to Use' and 'When NOT to Use' sections, naming concrete downstream consumers (DataVolley 4, VolleyStation, OpenVolley/R/Python) and three named alternatives (`get_match_player_stats`, `get_rotation_breakdown`, `get_game_actions`) with the condition that selects them. It also adds a hard precondition: do not call if `has_dvw` is False.

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

Deploy Server