Nova Cast

Get Operation

get_operation

Read-onlyIdempotent

Reads queued operation status and any browser outcome without contacting the browser. Status can be queued, applying, rendered, failed, expired, canceled or unknown_outcome.

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": {
      "operationID": "<operationID>",
      "controlToken": "<controlToken>"
    },
    "name": "get_operation"
  }
}

Input Schema

Name	Required	Description	Default
`operationID`	Yes
`controlToken`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 29, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds real value on top: the call does not touch the browser, and the full status vocabulary (queued, applying, rendered, failed, expired, canceled, unknown_outcome) is disclosed, including the ambiguous 'unknown_outcome'. It stops short of describing the 'browser outcome' payload structure.

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?

Two sentences, front-loaded with the core behavior, second sentence delivering the status vocabulary. No padding or restatement of the name.

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

Completeness3/5

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

No output schema, so the description is the only source for return shape, and 'any browser outcome' is left undefined while both required params go unexplained. It's enough to know what the tool does but not enough to call it confidently or interpret the result.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for two required parameters, yet it never mentions operationID or controlToken. An agent gets no hint that controlToken is a credential (minLength 20) nor what operationID refers to, leaving the schema's bare types as the only guidance.

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?

States a specific verb (reads) and resource (queued operation status), plus the scope limit 'without contacting the browser'. It doesn't explicitly name a sibling alternative, but the enumerated status values make the outcome shape unambiguous.

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?

The phrase 'without contacting the browser' implies a cheap polling call, and the status list implies a poll-until-terminal pattern, but the agent is never told when to use this instead of, say, get_canvas or inspect. Usage is inferred rather than stated.

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

All Nova Cast 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?