Tasvr

Poll a generate_image task

get_generation_status

Idempotent

Returns the status of one render task: processing, completed (with the image link) or failed. For an isolate job, the result carries the cutout as isolatedReference.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_generation_status"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes

Output Schema

Name	Required	Description
`error`	No
`status`	Yes
`receipt`	No	A signed receipt for the finished image.
`task_id`	Yes
`image_url`	No
`generation_id`	No
`credits_remaining`	No
`isolatedReference`	No	For an isolate_reference_item job: the cutout as a reference. Pass its ref or url to generate_image, or its generation_id or url to save_reference_to_library.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description adds real behavioral context beyond the annotations by enumerating the three status values and disclosing that an isolate job returns the cutout as isolatedReference. However, there is a mild tension with readOnlyHint=false for what reads as a pure status retrieval, and no explanation of whether polling consumes or transitions task state.

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 tight sentences with the core outcome list front-loaded and the conditional isolate-job detail appended where it is useful. No filler, though it omits higher-value guidance in the space it uses.

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?

The tool is simple and has an output schema, so return-value shape need not be spelled out, and the description already covers statuses and the isolate field. What is missing for correct invocation is the provenance of task_id and any guidance on when to stop polling.

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 coverage is 0% and the single task_id parameter is entirely undocumented — the description does not say where the id comes from (generate_image vs isolate_reference_item), its format, or whether it expires. With no schema help, the description should compensate and does not.

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 concrete verb and resource ('Returns the status of one render task') and enumerates the possible outcomes (processing, completed, failed), which lets an agent distinguish it from the generate_image sibling that creates tasks. Sibling differentiation is implicit via the title rather than stated in the description itself.

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?

Usage is only implied: an agent can infer this is the poll-after-submit tool, but the description never says so explicitly, gives no polling cadence or termination advice, and does not name generate_image or isolate_reference_item as the tools that produce the task_id.

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

All Tasvr 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?