Skip to main content
Glama

Modellix Media Generation

modellix_upload_file

Upload a public URL or base64_content with filename, at most 16 MiB (16777216 bytes). No local filesystem paths. Reuse returned URLs in model input. Default team limits: 10 files, 2 concurrent uploads, 7-day retention; configuration may vary. On 429, list files and explicitly delete only unneeded IDs; no automatic cleanup.

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

Input Schema

NameRequiredDescriptionDefault
urlNo
filenameNo
base64_contentNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false) by disclosing the size cap in bytes, team quotas (10 files, 2 concurrent uploads), 7-day retention/expiry, concurrency limits, and the 429 rate-limit behavior with a warning against automatic cleanup. These are exactly the operational traits an agent needs and cannot get from structured fields.

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?

Front-loads the two accepted input forms and the size limit, then layers constraints, quota/retention facts, and error recovery in short clauses. Every sentence carries information; no filler.

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 an output schema present, the description needn't explain return values, and it still usefully says to reuse the returned URL. The main remaining gap is the 0-required-parameter schema: the description implies url or base64_content plus filename but never states which combination is valid.

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?

Schema coverage is 0%, so the description must compensate and largely does: it clarifies that 'url' must be a public URL (not stated in schema), that 'base64_content' pairs with a filename, and that the effective size limit is 16 MiB despite the larger base64 maxLength. It does not clarify that url/base64_content are mutually exclusive alternatives or when filename is required.

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?

States a specific verb and resource ('Upload a public URL or base64_content with filename') plus hard constraints (16 MiB). It is unambiguous what the tool does, though it never names a sibling (e.g., modellix_list_files) to contrast against, so sibling differentiation is only implied.

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?

Gives real usage context: no local filesystem paths, reuse the returned URL in model input, and an explicit recovery path on 429 (list files, delete only unneeded IDs). It stops short of stating when to choose this over alternatives, but the inclusion and exclusion guidance is clear.

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.