Skip to main content
Glama

var2_check_join_status

Read-only

Status check for a join / stitch render. "Is it ready / done yet?" / "check on it" / "where is my …" + placeholder_id or var2 link, media word = a join / stitch render → THIS tool. Status question with an id/link: NEVER answer null — one var2_get_*result always matches; pick by MEDIA WORD. Action verbs ("animate it", "upscale", "extend it", "make a 3d model from it") → the matching create/modify tool with that url/id, NOT a status tool. Pair: var2_join_videos. One immediate snapshot, never loop. NOT for routine progress checks: the inline preview in the chat updates itself when the job finishes — call this only when the user asks, or when you need the finished URL for a next step (then pass wait_seconds so ONE call waits for it - never check in a loop). Plain video renders → var2_get_video_result. A jp… id is a PLAN, not a render — it STARTS rendering via var2_join_videos({plan_id}); this tool takes only the plain-UUID placeholder_id of an already-queued render (from var2_join_videos or var2_render_timeline).

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": {
      "placeholder_id": "<placeholder_id>"
    },
    "name": "var2_check_join_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
wait_secondsNoOnly when you need the finished file URL for a next step: the call waits up to this many seconds and returns as soon as the asset is ready (images ~90, video / audio / 3D ~240). One waiting call - never check in a loop.
placeholder_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / wait_seconds
      Added value: +{
      +  "description": "Only when you need the finished file URL for a next step: the call waits up to this many seconds and returns as soon as the asset is ready (images ~90, video / audio / 3D ~240). One waiting call - never check in a loop.",
      +  "maximum": 240,
      +  "minimum": 0,
      +  "type": "number"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, so the description carries the rest and does: one immediate snapshot, never loop, the chat preview auto-updates, and wait_seconds exists solely to get the finished URL for a next step. It also discloses the input precondition (plain-UUID of an already-queued render, not a plan id) and names the two tools that produce such an id.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core rule, but bloated: multiple quoted user phrasings, the never-loop warning stated twice, and anti-pattern reminders that could be tightened. The information is valuable but the packaging is heavier than needed.

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?

Covers routing, preconditions, rate/polling etiquette, and the wait_seconds escalation path, which is the full decision surface for this tool. It stops short of describing the shape of the snapshot returned (status values, URL field), and with no output schema that is the one remaining gap.

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 50% and the undocumented placeholder_id is fully explained (plain-UUID from var2_join_videos or var2_render_timeline, not a jp_ plan id), which is real added meaning. wait_seconds is largely restated from the schema, including the 240 cap guidance, so it adds less beyond structured data.

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?

States a specific verb and resource — a status check for a join/stitch render keyed by placeholder_id — and explicitly separates itself from var2_get_video_result (plain video renders), var2_join_videos (starts the render from a plan), and var2_render_timeline. An agent can route to it without opening another schema.

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?

Gives explicit when-to-use triggers ("is it ready", "check on it", "where is my …" + id/link) and explicit when-not-to-use rules: action verbs go to the matching create/modify tool, routine progress is handled by the self-updating inline preview, plain video renders go to var2_get_video_result, and a jp_… plan id must be started via var2_join_videos instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources