Skip to main content
Glama

Show Sequencer image

render_image
Read-onlyIdempotent

Use this after get_media reports that a Sequencer image is completed. It displays completed image media inline in the conversation.

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": {
      "workspaceId": "<workspaceId>",
      "mediaId": "<mediaId>"
    },
    "name": "render_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaIdYesCompleted image media ID returned by generate_image or get_media
workspaceIdYesWorkspace containing the completed image

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior the annotations cannot express: the result is displayed inline in the conversation, and the tool is only meaningful once the asset reaches a completed state. It stops short of describing failure behavior for unready media.

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

Conciseness5/5

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

Two short sentences with the precondition front-loaded and no redundant restatement of the title, parameters, or annotations. Every clause carries information.

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 two-parameter presentation tool with an output schema and full annotation coverage, the description supplies the one thing that is genuinely non-obvious — the required completed-media precondition and the inline rendering effect. Only edge-case handling for unfinished media is missing.

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 description coverage is 100% and both parameters already document their origin (mediaId from generate_image or get_media, workspaceId as the containing workspace). The description adds no format or constraint detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action (displays image media inline) on a specific resource (a completed Sequencer image), so an agent knows this is a presentation/rendering step rather than a generation step. It doesn't contrast itself against the similarly named sibling render_media, so the differentiation is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit precondition: call this only after get_media reports the Sequencer image is completed, which is a real gating signal for an agent. It does not state what to do if the media is not yet completed, nor does it name render_media as the alternative for non-Sequencer media.

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.