Skip to main content
Glama
hail

hail

Official

Create a file upload link

create_file_upload

Generate a one-time upload link to transfer a local file to Hail by curl for email attachments or verification documents, returning the upload ID and ready-to-use curl command.

Instructions

Create a one-time link that uploads one file from a shell with curl.

    The bytes go from the local disk to Hail directly, not through the tool call,
    so any file that is not tiny goes this way.
    An email attachment can be up to 25 MB. A verification document must be
    JPG, PNG or PDF, up to 10 MB, and is usable for 1 hour after the upload.
    Returns ``id``, ``upload_url``, ``expires_at`` (15 minutes), ``max_bytes``
    and a ready ``curl`` line with a ``'FILE_PATH'`` placeholder for the
    file's absolute path.
    The link needs no key and works once. The upload response holds
    ``size_bytes`` and ``sha256`` to compare with the local 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": {
      "purpose": "<purpose>",
      "filename": "<filename>",
      "content_type": "<content_type>"
    },
    "name": "create_file_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeYesWhat the file is for. ``email_attachment``: its ``id`` goes in ``send_email``'s ``attachment_ids``. ``verification_document``: its ``id`` goes in the ``files`` of ``check_verification`` and ``submit_verification`` as ``{slot, upload_id}``.
filenameYesFile name, such as ``passport.pdf``.
content_typeYesThe file's MIME type, such as ``application/pdf``.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.32.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say this is a non-idempotent, non-destructive write; the description adds far more — the link is unauthenticated and single-use, expires in 15 minutes, the resulting upload stays usable for 1 hour, and the upload response carries size_bytes and sha256 for verification. It also discloses the out-of-band transfer model, which is the key behavioral surprise.

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 action and the transfer model, then constraints, then return shape — a sensible order with almost no filler. The return-value sentence is long and partly duplicates the output schema, which keeps it from a 5.

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?

Covers the full lifecycle an agent needs: how to create the link, how the file travels, size/format limits per purpose, validity windows, one-time semantics, and how to verify the resulting upload. For a three-parameter tool with an output schema this leaves no operational gap.

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 baseline is 3, but the description adds constraints not present in the schema: 25 MB ceiling for email attachments and JPG/PNG/PDF-only, 10 MB ceiling for verification documents. It does not restate per-parameter syntax, which the schema already handles.

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 and resource ('Create a one-time link that uploads one file') and immediately clarifies the mechanism — bytes go from local disk to Hail directly rather than through the tool call. An agent can distinguish this from an in-band upload without opening the schema.

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 a clear routing rule ('any file that is not tiny goes this way') that implicitly selects this tool over an inline upload alternative, and the purpose enum explains downstream consumers. It stops short of naming the alternative tool or stating a hard size threshold at which the other path should be used.

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