Skip to main content
Glama

inspect_render

Returns metadata for a recently captured or rendered image to verify render output and diagnose visual results.

Instructions

Return metadata about the latest captured/rendered image.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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; it does disclose that the tool returns metadata rather than image data, which is a meaningful behavioral distinction. It does not say what happens when no render has been captured yet, whether it is read-only, or how 'latest' is determined, leaving real gaps.

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 sentence with no filler, well matched to a zero-parameter tool. The only weakness is the ambiguous 'captured/rendered' construction, which adds a word without resolving whether these are two distinct sources.

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?

An output schema exists, so return-value details need not be restated, and with no parameters the surface area is small. Still, a metadata-inspection tool should say whether it fails when no render exists and what 'latest' scopes over (scene, camera, viewport) — that context is absent.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description adds no misleading parameter-like language, though the 'captured/rendered' slash phrasing hints at a modality choice that has no corresponding input.

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 ('Return') and resource ('metadata about the latest captured/rendered image'), so an agent knows it retrieves inspection data rather than the image itself. It does not distinguish itself from nearby siblings such as get_render_result or get_render_settings, leaving some ambiguity about which retrieval tool to pick.

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: the word 'latest' hints this should be called after a capture/render exists, but there is no explicit when-to-use statement and no named alternative for retrieving render output or settings. An agent must infer the sequencing and the boundary against get_render_result.

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