Skip to main content
Glama

UXMachine

by io.github.qtorb
OverviewDiscussionsAdmin

Measure a web page

medir

Measures a web page with UXMachine in a real browser. Returns the measurement id right away; the result takes a few minutes and is read with estado. Each measurement uses 1 credit from the account; measurements that cannot be made use none.

Input Schema

NameRequiredDescriptionDefault
urlYesFull address of the page, including its protocol (https://…).
idiomaNoLanguage of the answers: "es" or "en". Defaults to "en".
anteriorNoOptional. Id of an earlier measurement from the same account to compare this one with.
iniciativaNoOptional. "agente" if you decide to measure on your own; "persona" if the person you work with asked you to.
esperar_segundosNoOptional. Seconds to wait for the measurement to finish before answering, from 0 to 50. Without it, medir answers at once. If it has not finished by then, call estado.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / esperar_segundos / description
      Previous value: -"Optional. Seconds to wait for the measurement to finish before answering, from 0 to 240. Without it, medir answers at once. If it has not finished by then, call estado."New value: +"Optional. Seconds to wait for the measurement to finish before answering, from 0 to 50. Without it, medir answers at once. If it has not finished by then, call estado."
    • changedInput schema / properties / esperar_segundos / maximum
      Previous value: -240New value: +50
  2. Changed1 schema field changed
    • addedInput schema / properties / esperar_segundos
      Added value: +{
+  "description": "Optional. Seconds to wait for the measurement to finish before answering, from 0 to 240. Without it, medir answers at once. If it has not finished by then, call estado.",
+  "maximum": 240,
+  "minimum": 0,
+  "type": "integer"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the asynchronous lifecycle (id returned right away, result takes minutes, read via `estado`), the credit cost per measurement, and the no-charge behavior for failed measurements. These are meaningful traits the structured fields do not convey.

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?

Three short sentences with zero filler; the async lifecycle and polling path are front-loaded, and the cost note is a single compact clause.

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?

With no output schema, the description carries the return-value burden and does so (an id, result via `estado`). Cost and async behavior are covered; only edge cases like comparison via `anterior` are left entirely to the schema.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents every parameter including the enum and the esperar_segundos polling semantics. The description only gestures at the wait/poll flow indirectly and adds no parameter meaning beyond the schema, which is the baseline-3 case.

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

Purpose5/5

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

States a specific verb (measures) and resource (a web page), plus the execution context (UXMachine, real browser). It also implicitly separates itself from the sibling 'estado' by naming it as the tool that reads the result.

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?

Clearly explains the async usage pattern — invoke, get an id immediately, then poll with `estado` — which tells the agent when this tool ends and the sibling begins. It lacks an explicit 'do not use this when...' exclusion, so it stops short of a 5.

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

All UXMachine toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources