Skip to main content
Glama

Image Upload Set

image_upload_set
Destructive

Upload a local PNG, JPEG, GIF, SVG, or WebP image (under 25 MB) into an existing Data Studio image component using a checked fingerprint, journaled write, and read-back verification.

Instructions

Upload a local image file (png/jpeg/gif/svg/webp, < 25 MB) into an image component (create one with components_create type image-component). Uses the panel's own upload; one journalled page write, read back, restorable. page_get fingerprint.

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": {
      "page_id": "<page_id>",
      "component_id": "<component_id>",
      "path": "<path>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "image_upload_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
dry_runNo
page_idYes
report_idNo
component_idYes
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A3.8/5.0
Behavior4/5

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

With destructiveHint=true already declared, the description adds real context: the call performs exactly one journalled page write, is read back, and is restorable — which materially softens the destructive hint. It does not disclose that dry_run defaults to true, a significant behavioral fact for a write tool, so it falls short of full transparency.

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?

Front-loaded and compact, but the compression degrades clarity — the closing fragment 'page_get fingerprint.' has no verb and forces guessing at the intended action. Most sentences earn their place; the terseness is where it loses points.

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

Completeness3/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 needn't be explained, and the write/restore story is covered. However, for a destructive six-parameter tool with zero schema descriptions, omitting the dry-run default and report_id semantics is a meaningful gap in what an agent needs before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description must compensate and only partially does: it clarifies that path is a local file with a format/size constraint and that expected_fingerprint comes from page_get. It says nothing about dry_run (which defaults to true), report_id, or page_id, leaving half the parameters semantically empty.

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 concrete verb and resource ('Upload a local image file ... into an image component') and narrows scope with accepted formats and a size ceiling. It also tells the agent the target must be an image component, pointing at components_create type image-component for prerequisites, so the tool is distinguishable from generic component 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 the precondition path explicitly (create the component first with components_create) and implies fingerprint retrieval via page_get. It stops short of naming when NOT to use it — e.g. how it differs from image_export or a generic page write — so an agent still has to infer exclusions, but the operational context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools