Skip to main content
Glama
ipp-bridge-mcp

ipp-bridge-mcp

Upload File

upload_file

Stages a text or base64-encoded file through the upload bridge and returns a file_id and local_path for print validation or printing.

Instructions

Stage a text or base64-encoded binary file through the upload bridge.

Returns file_id and local_path that can be passed to validate_print_job or print_file.

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": {
      "filename": "<filename>"
    },
    "name": "upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
ttl_secondsNo
content_textNo
content_typeNo
content_base64No

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It partially meets it by disclosing the staging model and the two return handles needed to chain into validate_print_job or print_file, but it says nothing about size limits, authentication, whether staging is ephemeral or how ttl_seconds affects retention, or what happens if the same filename already exists.

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 short sentences, zero filler, with the staging behavior stated first and the returned handles second. Every clause earns its place and the return contract is front-loaded before the caller needs it.

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?

An output schema exists, so the description does not need to enumerate return fields — though it helpfully names the two important ones. For a five-parameter, zero-coverage staging tool with no annotations, however, the definition leaves the ttl and content-type semantics and the upload constraints unaddressed.

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 description coverage is 0% across five parameters, so the description must compensate. It does add real meaning by mapping 'text or base64-encoded binary' onto the content_text vs content_base64 choice, but ttl_seconds and content_type are never explained in either place, leaving the agent to guess at units, defaults, and MIME behavior.

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 gives a specific verb and resource ('Stage a text or base64-encoded binary file through the upload bridge') and names the downstream consumers, which lets an agent place it relative to print_file and validate_print_job. It stops short of distinguishing it from the sibling upload-management tools (get_uploaded_file, delete_uploaded_file), but the purpose itself is unambiguous.

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 only implied by naming the tools that consume the returned file_id/local_path; there is no explicit 'use this before printing, use get_uploaded_file to retrieve an existing one' routing. Nothing tells the agent when not to upload (e.g. re-uploading an already staged file), so the agent must infer the workflow.

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