Skip to main content
Glama

produce_match

Generate all videos for a match in one call: radar replays of every highlight plus first-person POV of featured plays, in 16:9, 9:16, or 1:1, skipping up-to-date files.

Instructions

Make the videos of a match in one call: 2D replays ('radar') of every highlight and first-person POV ('ingame') of the featured ones - pov='all' records every play instead - in each shape ('16:9', '9:16' ready to post on phones, '1:1'). Videos that already exist and are up to date are skipped. First-person plays without recorded footage are captured together in one game session (capture_job_id, wait with get_job); their videos are queued when it finishes. detail explains anything that could not be queued (for example: recording is not enabled here).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "match_id": "<match_id>"
    },
    "name": "produce_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
povNofeatured
forceNo
formatsNo
match_idYes
renderersNo
highlight_idsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, it discloses that existing up-to-date videos are skipped, that missing footage triggers a capture_job_id and requires waiting with get_job, and that detail explains anything that could not be queued. These are meaningful behavioral traits for a non-read-only render tool.

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?

The description is dense but front-loaded, starting with the core action and then covering variants, skip behavior, and async capture. Parentheticals are used heavily, but each sentence contributes useful information without excessive repetition.

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?

For a complex batch-rendering tool with an output schema, the description covers the essential workflow: what gets rendered, how pov and formats work, skip semantics, and the capture_job_id follow-up. The main gap is the lack of explanation for force and highlight_ids, but the overall definition is sufficient to call the tool correctly.

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 0%, so the description has to carry parameter meaning. It explains pov ('all' records every play), formats, and renderers, but it omits force and highlight_ids entirely, leaving two input parameters undocumented.

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 states a specific verb and resource: it makes the videos of a match in one call, covering both radar and ingame renderers and all formats. It clearly distinguishes itself from single-highlight rendering siblings by emphasizing batch production for a whole match.

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?

It implies when to use the tool by saying 'in one call' and explaining pov='all' versus featured, but it does not explicitly name alternatives like render_highlight or state when not to use this batch tool. The usage context is inferable but not spelled out.

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