Skip to main content
Glama

render_quad_view

Capture all four viewport panes as separate images, using an optional base output path and resolution to save each pane for review or comparison.

Instructions

Capture all four viewport panes to separate images.

Args: output_path: Base image path; viewport names are appended, variables ($JOB) are expanded. Default: a new PNG in the temp dir. resolution: [width, height] in pixels. Default: the viewport's own size.

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

Input Schema

NameRequiredDescriptionDefault
resolutionNo
output_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.24.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / output_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / output_path / default
      Added value: +null
    • removedInput schema / properties / output_path / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "output_path"
      -]
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real value: it discloses the default temp-dir output, that viewport names are appended to the base path, and that $JOB-style variables are expanded. It omits side-effect details an agent would want — image format, whether existing files are overwritten, and whether the call blocks until capture completes.

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-sentence purpose, then a compact args block with no filler. The docstring-style formatting is slightly raw but every line carries information.

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

Completeness3/5

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

For a two-optional-parameter tool with no annotations and no output schema, the parameter coverage is adequate, but nothing is said about what the call returns (e.g., the generated file paths) or how the four panes are named, which an agent would need to use the result.

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 description coverage is 0%, so the description must compensate, and it largely does: output_path is explained as a base path with viewport names appended and variable expansion plus a default, and resolution is given as [width, height] with the viewport-size default. Only the exact expected array length for resolution is left implicit.

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: 'Capture all four viewport panes to separate images.' The scope ('all four', 'separate images') clearly distinguishes it from a single-pane capture, though it never names the sibling render_viewport that an agent would otherwise compare against.

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?

Usage is only implied by the phrase 'all four viewport panes' — an agent can infer this is the multi-pane variant, but there is no explicit when-to-use/when-not guidance and no named alternative such as render_viewport or capture_screenshot.

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