Skip to main content
Glama

render_highlight

Renders a CS2 highlight to an MP4 as an asynchronous job, using 2D radar or in-game POV output, and returns a job ID with an optional wait for the video URL.

Instructions

Render a highlight to an mp4 (asynchronous). renderer: 'auto' (in-game POV if this server can, else 2D), 'radar' (2D tactical replay; extra: {camera:'follow'|'full', zoom:1-3}) or 'ingame' (real CS2 footage, slower). Returns job_id; if wait_seconds > 0 it waits and includes video_url when done.

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": {
      "highlight_id": "<highlight_id>"
    },
    "name": "render_highlight"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
extraNo
widthNo
heightNo
rendererNo
highlight_idYes
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=false, so the description adds the real behavioral payload: the call is asynchronous, returns a job_id, and wait_seconds>0 blocks and populates video_url. It also flags that 'ingame' is slower, which warns about latency. It stops short of stating a hard timeout or the polling pattern (get_job) once wait_seconds elapses.

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?

A single front-loaded paragraph that opens with the action and output, then enumerates modes, then states the return contract. Dense and waste-free, though the inline-brace shorthand for 'extra' is terse enough to require re-parsing.

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?

An output schema exists and the description still explains the key return fields (job_id, video_url), which is appropriate for an async tool. For a 7-parameter render tool the only meaningful omissions are fps/width/height semantics and the polling path after a non-zero wait returns without video_url.

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?

With 0% schema coverage the description carries the burden, and it covers the non-obvious params well: the three renderer values with semantics, the nested 'extra' shape for radar ({camera:'follow'|'full', zoom:1-3}), and wait_seconds behavior. fps, width, and height are left unexplained except by name, which is a modest remaining gap since they materially affect render output.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Render a highlight') plus the output artifact ('to an mp4') and the execution model ('asynchronous'). It does not name a sibling such as get_render or render_reel to clarify boundaries, but the resource/action pairing is unambiguous.

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?

Gives explicit selection guidance among renderer modes with trade-offs: 'auto' is in-game POV when the server supports it else 2D, 'radar' is a 2D tactical replay with extra camera/zoom options, 'ingame' is real CS2 footage 'slower'. It does not say when to use this tool versus get_render/render_reel, which is the remaining gap.

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