Nimo

Read a Check

get_check

Read-onlyIdempotent

Read the status and result of a check_website call. Does not start work or spend another check. Pending means wait 5 seconds. A completed result includes measurements, suggested fixes and a free save link.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`jobId`	Yes	jobId returned by check_website.
`accessToken`	Yes	Private accessToken returned by check_website. Keep it out of logs and public posts.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	Checked page URL; present when a result is available.
`error`	No	Public failure message when the job failed.
`jobId`	Yes	Private check identifier. Pair with accessToken when polling.
`device`	No	Lab device, when recorded for the completed job.
`report`	No	Measured report summary, present only when a result is available.
`status`	Yes
`saveUrl`	Yes	Private save link carrying the check handle in its URL fragment.
`nextStep`	Yes
`retention`	Yes
`measuredAt`	No	Measurement timestamp, when recorded for the completed job.
`accessToken`	Yes	Bearer secret for this check only. Keep private; never log or publish.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 14, 2026

addedOutput schema / properties / report / properties / pageMetadata

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "issueCount": {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "status": {
+          "enum": [
+            "complete",
+            "issues",
+            "unavailable"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "issueCount"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / report / required

Previous value: -[
-  "metrics",
-  "metricProvenance",
-  "primaryFinding",
-  "lcpEvidence",
-  "actions",
-  "dismissedFindings",
-  "runConditions",
-  "recommendations",
-  "sectionCounts",
-  "truncatedSections",
-  "warnings",
-  "limitations",
-  "nextDiagnosticStep"
-]New value: +[
+  "metrics",
+  "metricProvenance",
+  "primaryFinding",
+  "lcpEvidence",
+  "actions",
+  "dismissedFindings",
+  "runConditions",
+  "recommendations",
+  "sectionCounts",
+  "truncatedSections",
+  "warnings",
+  "pageMetadata",
+  "limitations",
+  "nextDiagnosticStep"
+]

AddedSep 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds meaningful behavior beyond the annotations: it will not consume additional checks, pending requires a 5-second wait, and completed results include measurements, suggested fixes, and a save link. This is helpful operational context that annotations alone do not provide.

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 no filler. The core read behavior is front-loaded, followed by a key behavioral note and expected result contents. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers invocation context, polling behavior, and result contents. Combined with a complete input schema, a detailed output schema, and informative annotations, nothing essential is missing for an agent to call this tool correctly.

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 parameters are already fully documented with value patterns and security guidance for accessToken. The description does not add parameter-level detail beyond what the schema provides, so the baseline of 3 is appropriate.

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?

The description uses a specific verb and resource: 'Read the status and result of a check_website call.' It clearly differentiates itself from check_website by stating it does not start work, so an agent can distinguish this polling/read tool from its sibling.

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?

The description tells the agent to use this tool after a check_website call, provides the pending polling cadence ('wait 5 seconds'), and states that it does not trigger new work. It does not explicitly contrast with compare_checks, but the context is clear enough for selecting this tool.

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

All Nimo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?