Skip to main content
Glama
Render MCP Server

Render MCP Server

by meiti-dev

render_expect

Check expectations against the current screen and last action; get yes/no answers with proof from the exact element or request.

Instructions

Check what you expect against the current screen and the last action; each answer is yes or no with its proof (the exact element or request). Expectations: {"exists": "..."}, {"not_exists": "..."}, {"text": "...", "contains": "..."}, {"appeared": "..."}, {"disappeared": "..."}, {"no_changes": true}, {"no_issues": true | ["contraste", ...]}, {"no_errors": true}, {"request": {"method": "POST", "url_contains": "/api/x", "status": 201}}.

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>",
      "expectations": "<expectations>"
    },
    "name": "render_expect"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYes
expectationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does state the return contract (yes/no with the exact element or request as proof) and enumerates checkable conditions, which is above-average disclosure, but it never says whether the call is read-only, whether it waits or retries for appearing/disappearing conditions, or what happens on timeout.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and return contract in the first clause, followed by a compact enumeration of the expectation grammar. Every fragment earns its place; there is no filler.

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 two-parameter assertion tool with no annotations and no output schema, this covers the essential ground: what is compared, what is returned, and the grammar of the expectations array. The unexplained 'session' parameter and unstated waiting/timeout semantics are the remaining gaps.

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 coverage is 0% and the expectations items are declared as bare objects, so the description must supply all meaning — and it does, enumerating the accepted keys (exists, not_exists, text/contains, appeared, disappeared, no_changes, no_issues, no_errors, request). It stops short of explaining how the selector value is expressed or whether keys can be combined, and the 'session' parameter is never mentioned.

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?

The description uses a specific verb-plus-object framing: check supplied expectations against the current screen and the last action, returning yes/no plus proof. That distinguishes it clearly from mutating siblings like render_act and from observer siblings like render_scan or render_compare, though it never names an alternative 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?

Usage is implied rather than stated: the phrase 'current screen and the last action' suggests asserting after an action, and the near-synonym render_compare is left unaddressed. There is no explicit when-to-use / when-not-to-use guidance or prerequisite (e.g. an open session) spelled out.

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