Skip to main content
Glama

Upload Media

neuron_upload_media

Upload a media file (image, video, audio, or document) from a local file path (local server only) or base64 content. Returns a URL for use in messages and broadcasts, plus the sha256 and size of the bytes sent so the upload can be checked.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / base64
      Removed value: -{
      -  "description": "Base64-encoded file content (without data URI prefix)",
      -  "type": "string"
      -}
    • removedInput schema / properties / filename
      Removed value: -{
      -  "description": "Original filename including extension (e.g., 'photo.jpg', 'report.pdf')",
      -  "type": "string"
      -}
    • removedInput schema / properties / mimetype
      Removed value: -{
      -  "description": "MIME type of the file (e.g., 'image/jpeg', 'image/png', 'application/pdf', 'video/mp4')",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "base64",
      -  "filename",
      -  "mimetype"
      -]
  2. First observed

TDQS

A3.9/5.0
Behavior4/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, closed-world write, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the return payload (URL, sha256, size) and the deployment constraint that local file paths only work on a local server. It does not cover error behavior or type/size limits, which keeps it at 4.

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?

Two sentences, no filler. The core action and accepted input modes come first, and the return-value information is placed last where it belongs. Every clause contributes something an agent needs.

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?

With no output schema, the description correctly explains what comes back (URL, sha256, size), and with an empty input schema it explains the input modes, so the major gaps are closed. Remaining omissions are secondary: no size or format limits, no failure/error description, and no guidance on which upload mode to prefer.

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 input schema declares zero properties, so the description is carrying the entire burden of input semantics and does so: it names the two mutually exclusive sources (local file path vs base64 content) and the constraint on the path mode. Baseline for a zero-parameter schema is 4, and here the description genuinely compensates for an empty schema rather than merely repeating it.

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 opens with a specific verb and resource ("Upload a media file") and immediately narrows the scope by enumerating accepted media kinds (image, video, audio, document) and the two accepted sources. An agent can tell this is the file-ingestion tool rather than a messaging or contact tool. It stops short of naming a sibling or stating what it is not, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: "Returns a URL for use in messages and broadcasts" signals the downstream purpose, and "(local server only)" flags a real constraint on the file-path mode. However, there is no explicit when-to-use/when-not guidance, no stated preference between the path and base64 modes, and no prerequisites (e.g. auth or size limits).

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