Skip to main content
Glama

var2_get_audio_result

Read-only

Status check for AUDIO: a song / music / track / tune. "Is it ready / done yet?" / "check on it" / "where is my …" + placeholder_id or var2 link, media word = AUDIO: a song / music / track / tune → 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_audio. 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_audio_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.7/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses real behavior: exactly one var2_get_*_result matches any given id so a null answer is never correct, the call returns a single immediate snapshot, and waiting should be done via one call with wait_seconds rather than polling. That anti-loop guidance is exactly the operational context annotations cannot express.

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?

Purpose and routing are front-loaded, but the prose is bloated by repeated ALL-CAPS fragments and redundancies — 'never check in a loop' appears twice in the description and again inside the wait_seconds schema. Tightening would improve signal without losing any guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, non-destructive status tool with no output schema, everything an agent needs is present: routing rule, media-word disambiguation, the paired create tool, the single-snapshot/anti-polling contract, and the waiting escape hatch. Nothing material is missing.

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%, so the schema carries most of the load, but the description adds meaning: placeholder_id may be a placeholder id or a var2 link, and wait_seconds should be passed when the finished URL is needed for a chained step. It does not explain inline_media beyond what the schema already documents, which keeps it below a 5.

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 states a specific verb and resource ('Status check for AUDIO: a song / music / track / tune') and distinguishes itself from the sibling status tools by media word (audio vs image/video/3D/dialog). An agent can route between var2_get_audio_result and var2_get_video_result without opening either 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?

Explicit when-to-use ('status question with an id/link', "is it ready yet"), when-not-to-use (action verbs like 'animate it' or 'upscale' belong to the matching create/modify tool), and it names the paired tool var2_create_audio. It also carves out an exclusion the sibling does not need — routine progress checks are unnecessary because the inline chat preview self-updates.

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