Skip to main content
Glama
Sign In
HiggsHole

HiggsHole

by szk1234
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

upload_asset

Upload a local file to a project's media library and receive an asset ID for use as an image or video frame.

Instructions

Ingest a local file into a project's uploads directory and return an asset ID usable as an image reference or a video frame.

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": {
      "path": "<path>"
    },
    "name": "upload_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute or user-relative path to a local file on this host.
projectNoProject slug. Defaults to 'unsorted', which always exists.unsorted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided. Description mentions the return value (asset ID) but does not disclose behavior on overwrite, file size limits, or permissions needed. Adequate but could be more transparent.

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?

Single sentence that is clear and to the point. No unnecessary words or redundancy. Perfectly concise.

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 simple params and no output schema, the description covers the main action and return value. Could mention error cases or file handling details, but sufficient for a straightforward tool.

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 coverage is 100% with descriptions for both parameters. The tool description adds minimal extra value, only restating that path is absolute or relative and project defaults to 'unsorted'. Baseline 3 is appropriate.

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

Purpose5/5

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

Clearly states the action (ingest), resource (local file to project uploads), and output (asset ID for image/video). Distinct from sibling tools like generate_image which create rather than upload.

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?

No explicit guidance on when to use this tool vs alternatives like generate_image or list_media. The purpose is clear but lacks context on when to prefer upload_asset over sibling tools.

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