Skip to main content
Glama
Sign In
Spronta MCP Server

Spronta MCP Server

by spronta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_image

Modify an image's alt text and tags to improve accessibility and organization within the Spronta Image CDN.

Instructions

Update an image's alt text and/or tags.

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": {
      "imageId": "<imageId>"
    },
    "name": "update_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdNoProject ID (UUID). If omitted, uses SPRONTA_PROJECT_ID env var.
imageIdYesImage ID (UUID)
altTextNoAlt text (max 1000 chars), or null to remove
tagsNoTags (max 50, each max 100 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is an update operation but doesn't mention required permissions, whether changes are reversible, rate limits, error conditions, or what happens when only some fields are provided. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and immediately specifies what can be updated. Every word earns its place in conveying the essential purpose.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns, error conditions, side effects, or authentication requirements. The agent must rely entirely on the input schema and trial-and-error for behavioral understanding.

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 100%, so the schema already documents all 4 parameters thoroughly. The description adds minimal value beyond what's in the schema - it mentions 'alt text and/or tags' which aligns with two parameters but doesn't provide additional context about projectId fallback behavior or tag/altText constraints beyond schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Update') and target resource ('an image's alt text and/or tags'), making the purpose immediately understandable. It distinguishes from siblings like delete_image or upload_image by focusing on metadata modification rather than creation/deletion. However, it doesn't explicitly differentiate from update_preset or update_project which also modify resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing an existing image), when not to use it (e.g., for bulk updates), or how it differs from similar tools like update_project. The agent must infer usage from the tool name and parameter schema alone.

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