Skip to main content
Glama

var2_get_dialog_result

Read-only

Status check for a VOICE-OVER / narration / dialog / spoken TTS clip. "Is it ready / done yet?" / "check on it" / "where is my …" + placeholder_id or var2 link, media word = a VOICE-OVER / narration / dialog / spoken TTS clip → 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_create_dialog. 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). "Is the voice-over done?" → THIS tool, never var2_get_video_result or var2_get_audio_result.

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_get_dialog_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
inline_mediaNoDefault true. Pass false to skip the inline base64 payload and rely on the resource_link + structured URL only. ALWAYS pass false when the user already saw this asset (repeat status checks, chaining into another tool) — never re-render the same media twice.
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.4/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=true and a title, so the description carries real weight and delivers: one immediate snapshot, no looping, inline base64 payload suppressed with inline_media=false to avoid re-rendering, and a single bounded wait via wait_seconds. It stops short of describing the return payload shape or what happens when the job is still pending after waiting, but the operational traits an agent needs are disclosed.

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?

The purpose is front-loaded and the routing logic is useful, but the text is written in a keyword-salad register with quote fragments and repeats the anti-loop rule three separate times ("never loop", "never check in a loop", "One waiting call - never check in a loop"). Substantial trimming would preserve all the guidance.

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 three-parameter read tool with no output schema, the definition covers identification, exclusions, the create/status pairing, the waiting behavior, and the inline-payload tradeoff. Only the semantics of a not-yet-ready return and the meaning of the resource_link/structured URL fields are left implicit.

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 67% and placeholder_id has no schema description at all, yet the description fills that gap by saying it may be a placeholder_id or a var2 link. The other two parameters are already well documented in the schema (defaults, maximums, ranges), and the description reinforces the "one waiting call, never loop" intent behind wait_seconds.

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+resource ("Status check for a VOICE-OVER / narration / dialog / spoken TTS clip") and explicitly disambiguates from siblings by naming var2_get_video_result and var2_get_audio_result as wrong answers for "Is the voice-over done?". The routing rule "status question with an id/link: pick by MEDIA WORD" lets an agent choose this tool without opening any 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 (user asks, or finished URL is needed for a next step), explicit when-not (routine progress checks, since the inline preview self-updates), and explicit alternatives (create/modify tools for action verbs like "animate it" or "upscale"). It also names the paired creation tool var2_create_dialog, so the create/follow-up workflow is unambiguous.

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