Skip to main content
Glama

Upload an image file

get_upload_url

Provides instructions for passing local image file paths to generate_image in images: [{ path }], so no upload is needed.

Instructions

Answers how to give this server an image file: it runs on the user's machine and reads files directly, so pass the file's path in images: [{ path }] to generate_image. No upload is needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_upload_url"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and delivers the key behavioral fact: the server runs on the user's machine and reads files directly, so no transfer is required. It does not disclose what a call actually returns or that the tool is effectively informational/side-effect free, leaving a modest gap.

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 compact sentence (wrapped in a colon clause) with no padding, and the actionable instruction comes before the closing reassurance. The opening framing ("Answers how to give this server an image file") is slightly indirect compared with simply stating the conclusion first.

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?

For a zero-parameter tool this covers the practical question of how to supply images, but with no annotations and no output schema the description should also say what invoking it yields (presumably guidance text) and whether it has any effect. As written, an agent knows the answer but not the result of calling.

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?

The tool takes zero parameters, and the schema confirms an empty object, so baseline is 4. The description is correct that no argument needs to be supplied here; the `images: [{ path }]` notation it mentions pertains to a sibling tool, not this one.

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 frames the tool as answering "how to give this server an image file" and immediately redirects to generate_image, so an agent learns the intent. However, it never states what calling get_upload_url actually does or returns, and it works against the name/title ("leads to 'get_upload_url' / 'Upload an image file'" versus "No upload is needed"), which could confuse an agent that searched for an upload utility.

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?

It clearly states the positive path (pass `images: [{ path }]` to generate_image) and the exclusion (no upload is needed), which resolves the agent's likely question. It stops short of an explicit "call this tool when X / do not call it when Y" formulation, but the routing is unambiguous.

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