Skip to main content
Glama

hjarni

by com.hjarni
OverviewDiscussionsAdmin

files-create_upload_url

Generate a one-time upload link for attaching files to a note. Share the upload_url with the user so they can upload directly in their browser, which saves tokens by avoiding base64 encoding. Some clients also render this result as an inline drop-zone the user can drop files into; you cannot detect that, so always share the link either way. The link expires after 30 minutes and accepts up to max_files_per_upload files per request, each up to max_file_size_bytes; when remaining_bytes/remaining_files are present the whole batch must also fit inside those. Use files-check_upload to verify completion. Required: note_id (integer). Optional: description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYesNote ID to attach the file to (required)
descriptionNoOptional file description

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesPass to files-check_upload to confirm completion
note_idYesNote the files will attach to
expires_atYesISO 8601 expiry instant
note_titleYesTitle of that note
upload_urlYesOne-time upload URL to share with the user
remaining_bytesNoBytes left in the account's file allowance; absent when only the per-file cap applies
remaining_filesNoFiles left in the account's file allowance; absent when only the per-file cap applies
expires_in_secondsYesSeconds until the link expires, measured server-side
max_file_size_bytesYesLargest single file this upload will accept
max_files_per_uploadYesMost files one upload request may carry

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / remaining_bytes / description
      Previous value: -"Bytes left in the Free allowance; absent when only the per-file cap applies"New value: +"Bytes left in the account's file allowance; absent when only the per-file cap applies"
    • changedOutput schema / properties / remaining_files / description
      Previous value: -"Files left in the Free allowance; absent when only the per-file cap applies"New value: +"Files left in the account's file allowance; absent when only the per-file cap applies"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "The one-time upload link and the limits it will be judged against.",
+  "properties": {
+    "expires_at": {
+      "description": "ISO 8601 expiry instant",
+      "type": "string"
+    },
+    "expires_in_seconds": {
+      "description": "Seconds until the link expires, measured server-side",
+      "type": "integer"
+    },
+    "max_file_size_bytes": {
+      "description": "Largest single file this upload will accept",
+      "type": "integer"
+    },
+    "max_files_per_upload": {
+      "description": "Most files one upload request may carry",
+      "type": "integer"
+    },
+    "note_id": {
+      "description": "Note the files will attach to",
+      "type": "integer"
+    },
+    "note_title": {
+      "description": "Title of that note",
+      "type": "string"
+    },
+    "remaining_bytes": {
+      "description": "Bytes left in the Free allowance; absent when only the per-file cap applies",
+      "type": "integer"
+    },
+    "remaining_files": {
+      "description": "Files left in the Free allowance; absent when only the per-file cap applies",
+      "type": "integer"
+    },
+    "token": {
+      "description": "Pass to files-check_upload to confirm completion",
+      "type": "string"
+    },
+    "upload_url": {
+      "description": "One-time upload URL to share with the user",
+      "type": "string"
+    }
+  },
+  "required": [
+    "upload_url",
+    "token",
+    "expires_at",
+    "expires_in_seconds",
+    "note_id",
+    "note_title",
+    "max_file_size_bytes",
+    "max_files_per_upload"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / note_id / description
      Previous value: -"Note ID to attach the file to"New value: +"Note ID to attach the file to (required)"
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare the mutation/non-idempotent profile, but the description adds substantial context: 30-minute expiry, max_files_per_upload and max_file_size_bytes limits, batch constraints via remaining_bytes/remaining_files, and the rationale for token savings. This goes well beyond the 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and the share-the-link instruction before the caveats. Every sentence is functional, though it is dense and runs long; a hair more structure would help but nothing is wasted.

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 not be explained. The description covers expiry, limits, batch constraints, the drop-zone uncertainty, and the verification path, which is complete for a two-parameter 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 description coverage is 100%, so note_id and description are already documented in the schema. The description merely restates 'Required: note_id' and 'Optional: description' without adding format or semantic meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Generate a one-time upload link') and resource ('attaching files to a note'), and implicitly distinguishes itself from siblings like files-attach and files-attach_from_url by describing a browser-based upload path. An agent knows exactly what this tool produces.

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?

Explicitly instructs to share the upload_url with the user, explains why (token savings), handles the ambiguous drop-zone case, and names files-check_upload as the follow-up verification step. When-to-use and the alternative are both spelled out.

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

All hjarni toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold 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