Skip to main content
Glama

Upload an image

heystack_upload_image

Upload an image. Requires MCP 2026-07-28.

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": "heystack_upload_image"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write. The description adds only "Requires MCP 2026-07-28," which is an unexplained version prerequisite, and says nothing about what gets created, where the image is stored, or failure modes. With the write semantics already in annotations, this adds little beyond a cryptic gate condition.

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?

Two short sentences with no filler, so it is concise, but the brevity comes from omission rather than efficiency. The version requirement is front-loaded without explanation of its consequence.

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 write tool with no output schema and an empty parameter object, the description should explain the input mechanism (inline data, reference, prior context) and the result. Neither is covered, leaving an agent unable to invoke it correctly from the definition alone.

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?

The schema declares zero parameters, so by baseline this would be a 4, but an upload tool that takes no declared input leaves the critical question—how image data is supplied—unanswered in both schema and description. The description does nothing to compensate for that gap.

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?

"Upload an image" states a verb and resource but is essentially a restatement of the name and title, adding no scope detail. It does not clarify what kind of image, where it lands, or how it relates to sibling artifact-creation tools like heystack_create_markdown.

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?

There is no when-to-use guidance, no prerequisites beyond an obscure protocol version string, and no alternatives named. An agent cannot tell from the description when uploading is appropriate versus using a contribution or edit tool.

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