Skip to main content
Glama

Refine a photo frame design

refine_frame

Ask for a changed version of a frame in an existing design thread — 'darker', 'less ornament', 'make the flowers smaller', 'more gold'. Call it with the threadId that check_generation returned for start_frame, and ONLY when the operator asks for a change: every call spends part of the account's free daily allowance, so never iterate on your own initiative. It returns immediately with a job id; call check_generation for the new preview. Earlier versions in the thread stay available to save_frame, so a change the operator dislikes loses nothing.

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": {
      "threadId": "<threadId>",
      "prompt": "<prompt>"
    },
    "name": "refine_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesWhat to change. It is read with the whole thread as context, so 'the same but darker' works. State the change and nothing else, starting from the operator's own words: what changes, to what, and what to keep if that matters ('background to deep green #1F3B2D, keep the motifs where they are'). Turn a vague word into a concrete change ('more festive' → which colour, motif or density moves). Do not restate the original design or add mood or praise words.
threadIdYesThe design thread, from check_generation's result for start_frame.

Output Schema

NameRequiredDescriptionDefault
kindYes
noteNo
whatYes
errorNo
jobIdYes
stateYes
threadIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / prompt / description
      Previous value: -"What to change. It is read with the whole thread as context, so 'the same but darker' works. State the change and nothing else: what changes, to what, and what to keep if that matters ('background to deep green #1F3B2D, keep the motifs where they are'). Turn a vague word into a concrete change ('more festive' → which colour, motif or density moves). Do not restate the original design or add mood or praise words."New value: +"What to change. It is read with the whole thread as context, so 'the same but darker' works. State the change and nothing else, starting from the operator's own words: what changes, to what, and what to keep if that matters ('background to deep green #1F3B2D, keep the motifs where they are'). Turn a vague word into a concrete change ('more festive' → which colour, motif or density moves). Do not restate the original design or add mood or praise words."
  2. Changed1 schema field changed
    • changedInput schema / properties / prompt / description
      Previous value: -"What to change, in the operator's words. It is read with the whole thread as context, so 'the same but darker' works; there is no need to repeat the original description."New value: +"What to change. It is read with the whole thread as context, so 'the same but darker' works. State the change and nothing else: what changes, to what, and what to keep if that matters ('background to deep green #1F3B2D, keep the motifs where they are'). Turn a vague word into a concrete change ('more festive' → which colour, motif or density moves). Do not restate the original design or add mood or praise words."
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the cost model (each call spends part of the account's free daily allowance), the asynchronous contract (returns immediately with a job id), and the non-destructive versioning guarantee (earlier versions stay available to save_frame). The annotations only say readOnlyHint=false and idempotentHint=false; the description supplies the operational and financial consequences the agent actually needs.

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?

Three dense sentences with zero filler: what it does, the hard precondition, then the async/versioning behavior. The gating rule is front-loaded before the mechanics, and every clause carries distinct information.

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?

With an output schema present, return values need not be explained, yet the description still tells the agent that the immediate response is a job id to be resolved via check_generation. For a costly, non-idempotent, open-world generation call, all decision-relevant facts are present.

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 100% and the prompt property's schema description is already extensive, so the description's contribution here is mainly restating the threadId provenance. The change examples ('darker', 'more gold') loosely illustrate the prompt parameter but add no new syntax or constraint beyond the schema. A 3 is the baseline when the schema carries the parameter burden.

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 and resource ('Ask for a changed version of a frame in an existing design thread') and immediately grounds it with concrete change examples ('darker', 'make the flowers smaller'). The frame/thread framing distinguishes it from start_frame (new design) and implicitly from refine_booth (booth assets) without ambiguity.

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?

Explicitly gates invocation: 'ONLY when the operator asks for a change' and 'never iterate on your own initiative', with the reason (daily allowance cost) supplied. It also names the preceding step (threadId from check_generation for start_frame) and the follow-up (call check_generation for the new preview), so the agent knows its place in the workflow.

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.