Skip to main content
Glama
Render MCP Server

Render MCP Server

by meiti-dev

render_scan

Rescan the current screen after it stabilizes and return the full element map with detected visual issues such as overflow, clipped text, or low contrast.

Instructions

Scan the current screen again (waits until it is stable) and return the full map with its visual issues.

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": {
      "session": "<session>"
    },
    "name": "render_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 disclose two real traits: it blocks until the screen is stable, and it returns the map plus detected visual issues. It says nothing about failure modes, cost/latency beyond the wait, or whether the session is mutated.

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 well-formed sentence with the action front-loaded and the blocking behavior tucked into a parenthetical. No wasted wording, though the return clause is slightly vague.

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?

Behavior and rough return content are covered for a simple one-parameter tool, but with no output schema and no annotations, the unexplained 'session' parameter and the undefined 'full map' leave real gaps an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, 'session', at 0% schema description coverage, and the description never mentions it or explains what a session identifier means here. For a low-coverage schema the description should compensate, and it does not.

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 ('scan') on a specific resource ('the current screen') and names the return content ('full map with its visual issues'). The word 'again' signals it is a re-scan, which differentiates it from an initial open/render call, though it never names a sibling explicitly.

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?

'Scan ... again' implies this is called after a prior scan or after the screen changed, which is useful implicit guidance. There is no explicit statement of when to prefer this over render_expect, render_compare, or render_open, and no preconditions are given.

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