Skip to main content
Glama

var2_get_image_result

Read-only

Status check for an IMAGE (picture / photo). "Is it ready / done yet?" / "check on it" / "where is my …" + placeholder_id or var2 link, media word = an IMAGE (picture / photo) → 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_image / var2_modify_image. 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).

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_image_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.3/5.0
Behavior4/5

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

Beyond readOnlyHint=true, it discloses that this is a single immediate snapshot, that the inline preview updates itself so polling is unnecessary, and that the call should not be looped. Some of this duplicates the wait_seconds and inline_media schema descriptions, which keeps it from a 5, but the self-updating-preview behavior is genuinely new context.

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?

Front-loaded with the purpose, then routing rules, then behavior — a sensible order with no filler sentences. The quoted-phrase style, slashes and a stray unbalanced quote make it denser and harder to scan than necessary.

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?

With no output schema, the description plus inline_media text convey what comes back (resource_link + structured URL, optional base64 payload) and how waiting behaves. The only real gap is exact return fields on failure versus success, which is minor for a status-check tool whose safety profile is already declared by annotations.

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 67%, and the description adds meaning mainly for the undocumented required placeholder_id by noting it accepts a placeholder id or a var2 link. The wait_seconds guidance largely restates the schema text ("one waiting call - never check in a loop"), and inline_media is already fully documented there.

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 an IMAGE (picture / photo)") and explicitly disambiguates from siblings: media-word routing among the var2_get_*_result family, and action verbs routed to var2_create_image / var2_modify_image. An agent can pick 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 status, or the finished URL is needed for a next step), explicit when-not-to-use (routine progress checks — the inline chat preview self-updates; action verbs go to create/modify tools), and names the paired alternatives. It even prescribes the wait_seconds pattern instead of looping.

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