Skip to main content
Glama
srgplus

srgplus-mcp

Official
by srgplus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_image_asset

Creates an image asset record for a hub profile and returns a signed upload URL. Deprecated: use upload_asset to create and upload in one step.

Instructions

Create an image asset record in a hub profile.

DEPRECATED: registers a record only and does not upload bytes; the
current backend requires a multipart upload init, so this call fails.
Use `upload_asset` to create and upload in one step.

workspace_id: target workspace ID — get available IDs from list_workspaces()
extension: without dot, e.g. "png"
Returns a signed URL for uploading the actual image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
widthYes
heightYes
extensionYes
workspace_idYes
hub_profile_idYes
memory_size_in_bytesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.18

TDQS

A4.4/5.0
Behavior5/5

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

Discloses that it only registers a record, does not upload bytes, and currently fails due to backend requirements, going well beyond the sparse annotations.

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?

The description is concise and well-structured with deprecation, alternative, and parameter notes, with no redundant content.

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?

Effectively communicates deprecation, failure mode, and the preferred replacement. Minor gaps remain around unspecified parameter meanings, but these are less critical for a deprecated failing stub.

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?

Only workspace_id and extension are explained; hub_profile_id, name, width, height, and memory_size_in_bytes receive no semantic description, leaving most parameters under-documented.

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?

Clearly states it creates an image asset record in a hub profile, and explicitly distinguishes itself from upload_asset by marking itself deprecated and directing users to the preferred alternative.

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 says the call fails on the current backend and tells users to use upload_asset instead, giving unambiguous when-not-to-use guidance.

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