NexDoc Design

Check run

check_run

Read-only

Fetch current status for a run (status, charge_usd, viewer_url, error). Pass THIS run's run_id after update_design — do not look up the previous run. viewer_url is only present when status is completed and includes ?run= for this generation. Never reuse a viewer_url from an earlier run. If concurrency_notice is present, show it to the user.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes
`run_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`error`	No
`job_id`	No
`run_id`	Yes
`status`	Yes
`log_tail`	No
`next_step`	No
`charge_usd`	No
`created_at`	No
`viewer_url`	No
`commit_hash`	No
`completed_at`	No
`notify_email`	No
`summary_diff`	No
`still_running`	No
`concurrency_notice`	No
`previous_preview_stale`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 17, 2026

changedOutput schema / properties / commit_hash / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / error / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / log_tail / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedOutput schema / properties / summary_diff

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedSep 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false. The description adds behavioral context: viewer_url is only present when completed and includes ?run= for this generation; never reuse from earlier runs. It also mentions concurrency_notice. No contradiction.

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?

The description is concise and front-loaded with the main purpose. Important usage notes are placed early, and each sentence adds critical information without fluff.

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 read-only fetch tool with an output schema that likely documents fields, the description covers key usage constraints (run_id, viewer_url handling). It omits specifics like response format or error cases, but the output schema mitigates that. Overall adequate.

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 coverage is 0% and parameters are just job_id and run_id with no descriptions. The description explains that run_id is the THIS run's run_id, but job_id is not explained beyond being required. It adds some value by clarifying run_id's role but does not fully compensate for the schema gap.

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 clearly states it fetches current status for a run with specific fields returned (status, charge_usd, viewer_url, error). It distinguishes itself from siblings like 'wait_for_run' and 'list_runs' by focusing on a single run's current status after an update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit instructions: pass THIS run's run_id after update_design, do not look up the previous run, never reuse a viewer_url from an earlier run. Also specifies handling of concurrency_notice. This is clear guidance on when and how to use.

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

All NexDoc Design 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?