Skip to main content
Glama

var2_get_3d_result

Read-only

Status check for a 3D MODEL / mesh / glb. "Is it ready / done yet?" / "check on it" / "where is my …" + placeholder_id or var2 link, media word = a 3D MODEL / mesh / glb → 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_3d. 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 3d model ready? placeholder " → THIS tool with that placeholder_id.

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

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?

Beyond the readOnlyHint annotation, it discloses that the call is a one-shot snapshot rather than a poll ("One immediate snapshot, never loop"), that wait_seconds turns it into a single blocking wait, and that a null answer is never acceptable because a matching status tool exists. These are behavioral facts an agent cannot derive from the annotation or schema.

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 routing rule and the exclusion for action verbs are front-loaded, which is good, but the text is padded with keyword-matching fragments in scare quotes and repeats the same warnings twice ("never loop" / "never check in a loop", plus a restated example for the 3D placeholder case). A tighter version would say the same thing in half the words.

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 and only two parameters, the description supplies what an agent needs: what a result represents (a finished asset URL / readiness state), that the call is non-polling, and how to make it wait. It does not describe what a not-yet-ready response looks like, but that is a minor residual gap for a status tool.

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% — wait_seconds is documented, but placeholder_id is a bare string. The description fills that gap by stating placeholder_id accepts either a placeholder id or a var2 link, and it clarifies when wait_seconds is appropriate. That is real added meaning, though it stops short of format details for either input.

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?

The description names a specific verb and resource ("Status check for a 3D MODEL / mesh / glb") and explicitly routes other media words to sibling tools ("one var2_get_*_result always matches; pick by MEDIA WORD"). An agent can distinguish this from var2_get_image_result, var2_get_video_result, etc. 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?

It gives positive triggers (status question with placeholder_id or var2 link), negative triggers ("Action verbs ... → the matching create/modify tool ... NOT a status tool"), and grade-level exclusions ("NOT for routine progress checks: the inline preview ... updates itself"). It also names the creation counterpart ("Pair: var2_create_3d"), so the when/when-not/alternative triad is complete.

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