Skip to main content
Glama

Attach an uploaded reference to Playground

playground_media_upload_complete
Idempotent

Verify the signed upload by server-owned path, actual byte size and media signature, then add one editable file node at the current canvas revision. Repeating the same upload ID returns the original node receipt. Returns the created node ID, canvas revision and replay status.

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": {
      "projectId": "<projectId>",
      "uploadId": "<uploadId>",
      "expectedRevision": "<expectedRevision>"
    },
    "name": "playground_media_upload_complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
uploadIdYesUpload ID returned by media_upload_begin after the bytes have been uploaded.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
expectedRevisionYesCurrent canvas revision from canvas_read; on revision_conflict, read again and rebuild the change.

Output Schema

NameRequiredDescriptionDefault
nodeIdYes
replayedYes
revisionYes
uploadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing what verification actually occurs (server-owned path, actual byte size, media signature) and how idempotent replay behaves, which the annotations only assert as a boolean. It does not describe failure modes when verification fails, which keeps it at a 4.

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

Conciseness4/5

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

Three tightly packed sentences, front-loaded with the verification-then-mutation sequence, with no filler. The final sentence enumerating return values is mildly redundant given an output schema exists, but it is short and orients the agent before the call.

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 three-parameter, fully documented mutation with an output schema and idempotency annotations, the description covers the essential unknowns: what is verified, what node is created, and how replay behaves. Only the verification-failure path is left implicit, which is a minor gap given the schema already flags revision_conflict handling.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: expectedRevision is framed as 'the current canvas revision' the node is added at, and uploadId is framed as a replay key whose reuse returns the original receipt. That is genuine semantic enrichment rather than restatement of the UUID descriptions.

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 opens with a specific verb chain and resource: verify the signed upload (by server-owned path, byte size and media signature) and then add one editable file node at the current canvas revision. That is clearly distinct from the sibling upload_begin step, so an agent can tell which stage of the upload lifecycle this tool owns without opening the schema.

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?

Usage context is clear: this is the completion step that follows byte upload, and 'Repeating the same upload ID returns the original node receipt' tells the agent that retries are safe and need no special handling. It stops short of explicit exclusions or naming a sibling to use instead (e.g. when to abandon an upload and start over), so it falls just short of the top band.

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.