Skip to main content
Glama
Sign In
Wiro MCP Server

Wiro MCP Server

Official
by wiroai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Upload a file to Wiro

upload_file

Copies a single file from a public HTTP(S) URL into Wiro, up to about 100 MB, and returns a Wiro link for reuse across multiple model runs. Does not support .zip archives.

Instructions

Copy a file from a public http(s) URL to Wiro, up to about 100 MB, and get a Wiro link back. Model file fields take public URLs directly, so use this only when the same file feeds several runs. Single files only, not .zip archives. A file that is only attached in the chat has no URL: ask the user for a public link.

Input Schema

NameRequiredDescriptionDefault
urlYesURL of the file to upload (image, audio, video, or document).
file_nameNoOptional filename. Defaults to the URL filename.

Output Schema

NameRequiredDescriptionDefault
fileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.1
    • removedOutput schema / properties / file / properties / url / format
      Removed value: -"uri"
  2. Changed2 schema fields changedv1.2.3
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed3 schema fields changedv1.2.1
    • changedInput schema / properties / file_name / description
      Previous value: -"Custom filename for the upload. If not provided, derived from the URL."New value: +"Optional filename. Defaults to the URL filename."
    • changedInput schema / properties / url / description
      Previous value: -"URL of the file to upload (image, audio, video, document)"New value: +"URL of the file to upload (image, audio, video, or document)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "file": {
+      "additionalProperties": false,
+      "properties": {
+        "id": {
+          "type": "string"
+        },
+        "mimeType": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "sizeBytes": {
+          "anyOf": [
+            {
+              "minimum": 0,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "url": {
+          "format": "uri",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name",
+        "mimeType",
+        "sizeBytes",
+        "url"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "file"
+  ],
+  "type": "object"
+}
  4. First observedv1.1.4

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive operation. The description adds useful behavior beyond that: about 100 MB size limit, public http(s) URL requirement, no .zip archives, and a returned Wiro link. It does not discuss duplicate uploads or overwrite behavior, keeping it below a 5.

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?

The description is four tight sentences and front-loads the core operation before usage constraints. Every sentence adds relevant guidance about alternatives, size, file type, or URL availability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The annotations cover safety traits and an output schema exists, so return values need not be fully documented. The description still supplies the key operational context: size limit, public URL requirement, no .zip files, single-file scope, and when to prefer direct model file fields.

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 100%, so the schema already documents both url and file_name. The description still adds meaningful semantics for url, specifying that it must be public http(s), up to about 100 MB, and not a .zip archive; it does not add further meaning for file_name, but the schema covers it.

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?

The description uses a specific verb and resource: copy/upload a file from a public http(s) URL to Wiro and return a Wiro link. It also clearly distinguishes this operation from passing a public URL directly to model file fields, so the agent can tell when this tool's purpose applies.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance: only when the same file feeds several runs, because model file fields accept public URLs directly. It also states exclusions and edge cases: single files only, not .zip archives, and chat-attached files have no URL so the user must provide a public link.

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