Skip to main content
Glama

Confirm an image upload

design_confirm_image_upload

Step 2 of attaching a user image: register the uploaded image.

Call after PUTting the bytes to the presigned URL. upload_url is that presigned url (the query string is dropped automatically). Attaches the image's public URL to the session, so a following design_chat embeds it.

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": {
      "session_id": "<session_id>",
      "design_id": "<design_id>",
      "filename": "<filename>",
      "upload_url": "<upload_url>"
    },
    "name": "design_confirm_image_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
design_idYes
session_idYes
upload_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the description's added value is the side effect it discloses: the image's public URL is attached to the session and surfaces in later `design_chat` calls. It also explains the query-string normalization of `upload_url`, which is real behavioral detail beyond the annotations; it stops short of saying what happens on a duplicate or failed confirmation.

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 paragraphs, front-loaded with the step position and the key precondition. Every sentence carries information an agent needs, with no restatement of the title or schema.

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?

An output schema exists, so return values need no explanation, and the annotations cover the safety profile. For a four-parameter mutation in a multi-step flow, the description covers ordering, the critical parameter's format, and the downstream effect; only the meaning of the remaining identifiers and failure/retry behavior are 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 0% across four required parameters, so the description must compensate. It does well for `upload_url` (clarifying it is the presigned URL and that the query string is dropped automatically) but leaves `filename`, `design_id`, and `session_id` entirely unexplained beyond their names.

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 ('register the uploaded image') and situates it explicitly as 'Step 2 of attaching a user image', which lets an agent place it in the upload flow without opening any schema. It also names the downstream consumer (`design_chat`), so it is distinguishable from the other design_* tools.

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?

Gives a clear precondition: call only after PUTting the bytes to the presigned URL, and notes that a subsequent `design_chat` will embed the image. It lacks explicit when-not guidance (e.g., what to do if the PUT failed or if confirmation is retried), but the sequencing context is strong.

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