Skip to main content
Glama

Prepare an image upload

prepare_image_upload

Used by the image picker to authorize a new file upload for this site.

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": {
      "siteId": "<siteId>",
      "contentType": "<contentType>",
      "size": "<size>"
    },
    "name": "prepare_image_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes
siteIdYes
contentTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the agent knows this is a non-destructive, non-idempotent write. The description adds the context that it issues an authorization scoped to the site, but says nothing about whether the authorization expires, what permissions are required, or whether repeat calls create multiple authorizations.

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?

One front-loaded sentence with no padding; it is efficiently written. The brevity tips into under-specification rather than verbosity, but no wording is wasted.

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 three-parameter, non-idempotent mutation with no output schema and no parameter documentation, the description is too thin. An agent cannot know what the call returns, how to feed that result into upload_images, or what content types and sizes are acceptable.

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% for all three required parameters (siteId, contentType, size). The phrase "for this site" faintly signals siteId, but contentType and size — including any allowed MIME values or size ceiling tied to the schema's maximum — are entirely undocumented in both schema and description.

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

Purpose3/5

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

The description names a specific action (authorize a new file upload) and its scope (for this site), which is more informative than the title alone. However, it does not explain what "prepare" actually produces (an upload URL, token, or session) or how it differs from the sibling upload_images, so the boundary between the two steps stays ambiguous.

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?

"Used by the image picker" hints at the calling context but gives no instruction on when an agent should call this versus upload_images, nor that it must precede the upload. There are no exclusions, prerequisites, or workflow ordering stated.

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