Skip to main content
Glama

Xorventa

by ai.xorventa
OverviewDiscussionsAdmin

Attach a file from a web address

xora_upload_from_url

Fetches a file from a public https address and stages it as a one-time upload for an action that takes a file, after the same type and size checks a direct upload meets. Private, loopback and link-local addresses, non-https addresses and every redirect to one are refused. When the state is ready, upload_reference is the value the upload action accepts as its upload_id argument; it expires after ten minutes and is used once.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesA public https address of the file. Private, loopback and link-local addresses are refused, every redirect is checked again, and the file must fit the action's type and size limits.
actionYesThe action that takes the file, e.g. upload_social_media.
filenameNoThe name to keep for the file; taken from the address when omitted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateYes
messageYesWhen reason_code is rate_limited: a plain sentence saying when to try again; null otherwise.
byte_sizeYes
mime_typeYes
upload_idYes
expires_atYes
reason_codeYesWhy nothing was fetched (not_an_upload_action, insufficient_scope, switch_off, rate_limited, ...); null otherwise.
rejection_codeYesWhy the fetched file was not staged (too_large, type_not_allowed, url_not_allowed, fetch_failed, ...); null when ready.
intended_actionYes
upload_referenceYesThe value an upload-taking action accepts as upload_id; set only when state is ready.
retry_after_secondsYesWhen reason_code is rate_limited: about how many seconds until a file can be staged again; null otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / description
      Added value: +"`xora_upload_from_url`'s answer for every client EXCEPT one served the ChatGPT per-operation\ncatalogue (under OpenAI's review, so its schema is frozen) — a held 1.1.0 client never has the\ntool at all (2026-10-19). Built from the base answer by `uploads.with_retry`."
    • addedOutput schema / properties / message
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "When reason_code is rate_limited: a plain sentence saying when to try again; null otherwise.",
+  "title": "Message"
+}
    • addedOutput schema / properties / retry_after_seconds
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "When reason_code is rate_limited: about how many seconds until a file can be staged again; null otherwise.",
+  "title": "Retry After Seconds"
+}
    • changedOutput schema / required
      Previous value: -[
-  "upload_id",
-  "state",
-  "upload_reference",
-  "intended_action",
-  "rejection_code",
-  "reason_code",
-  "expires_at",
-  "mime_type",
-  "byte_size"
-]New value: +[
+  "upload_id",
+  "state",
+  "upload_reference",
+  "intended_action",
+  "rejection_code",
+  "reason_code",
+  "expires_at",
+  "mime_type",
+  "byte_size",
+  "retry_after_seconds",
+  "message"
+]
    • changedOutput schema / title
      Previous value: -"XoraUploadFromUrlOut"New value: +"XoraUploadFromUrlOutWithRetry"
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, openWorld=true, non-idempotent, non-destructive) by disclosing SSRF protections — private, loopback and link-local addresses plus non-https addresses and every redirect to one are refused — along with type/size checks, single-use semantics, and a ten-minute expiry on the staged reference.

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?

Three dense sentences, front-loaded with the purpose before the refusal rules and the output contract. Nothing is padded; the expiry and single-use facts in the final sentence are operationally necessary.

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?

An output schema exists so return values need no explanation, and the description still supplies the one thing that matters operationally — how upload_reference is consumed and how long it lives. With rich annotations and full schema coverage, an agent has everything needed to call this correctly.

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 100%, so url, action and filename are already fully documented in the schema, which sets the baseline at 3. The description adds the useful flow detail that the returned upload_reference is passed as the upload_id argument, but contributes no additional per-parameter syntax or constraint detail.

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: fetches a file from a public https address and stages it as a one-time upload for an action that takes a file. The phrase 'after the same type and size checks a direct upload meets' implicitly contrasts it with the direct-upload siblings, but no sibling tool is named explicitly, so differentiation is inferential rather than stated.

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?

The description establishes the precondition that the target action must take a file and explains what to do once state is 'ready', which implies usage. However it never says when to choose this over xora_upload_prepare or xora_upload_request, nor names any alternative, so the routing guidance remains implied rather than explicit.

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

All Xorventa toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources