Skip to main content
Glama

UXMachine

by io.github.qtorb
OverviewDiscussionsAdmin

Check a measurement

estado
Read-onlyIdempotent

Tells where a measurement stands and, once it has finished, what was observed, with its limits, where the report is and, if an earlier measurement was given, how it compares with it. While it is queued or running, call it again until it has finished; each call waits up to 25 seconds by default.

Input Schema

NameRequiredDescriptionDefault
idYesThe id returned by `medir`.
idiomaNoLanguage of the answer: "es" or "en". Defaults to the language of the measurement.
esperar_segundosNoSeconds to wait for the measurement to finish before answering, from 0 to 50. Default 25. If it has not finished by then, call estado again.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description contributes genuinely non-structured behavior: a call blocks for up to 25 seconds, and unfinished states require repeated calls. It does not disclose rate limits or failure behavior, keeping it at 4.

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?

Two sentences, front-loaded with the outcome (what you get back), followed by the polling instruction. The first sentence is long and clause-stacked ('with its limits, where the report is and, if an earlier measurement was given, how it compares'), which costs some readability but no sentence is wasted.

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?

No output schema exists, so the description must describe returns — and it does, listing status, observations, limits, report location, and comparison. Combined with the 100%-covered input schema and readOnly annotations, an agent has what it needs. Minor gap: no mention of error/not-found behavior for a bad id.

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 already 100%, so the schema carries parameter meaning; the description's added value is the polling/wait semantics ('each call waits up to 25 seconds by default'), which explains why `esperar_segundos` exists. It does not touch the `idioma` parameter, but the schema covers that fully.

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 states a specific verb ('Tells where a measurement stands') and resource (a measurement), and enumerates what is returned at each lifecycle stage — status, observations, limits, report location, comparison. That distinguishes it from the sibling `medir` (which starts a measurement, as the id parameter description implies), though the description itself never names the alternatives.

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?

It gives an explicit operational rule: 'While it is queued or running, call it again until it has finished,' plus the 25-second blocking default. That tells the agent how to poll correctly. It stops short of stating when-not to use it (e.g. after completion, or versus `memoria`), so not 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
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources