Skip to main content
Glama

Kariaa Agents

Request a sample upload URL

request_upload

Use when you upload a sample file yourself. A one-time signed URL for ONE sample file of a task the person joined. PUT the raw bytes to upload_url with the returned headers, then call confirm_upload with the path. Kind must match the task; up to 100 MB; up to 10 files per task.

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": {
      "submission_id": "<submission_id>",
      "filename": "<filename>",
      "mime_type": "<mime_type>",
      "size_bytes": "<size_bytes>"
    },
    "name": "request_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
mime_typeYes
size_bytesYes
submission_idYes

Output Schema

NameRequiredDescriptionDefault
pathNoPass to confirm_upload
headersNoHeaders for the PUT
upload_urlNoSigned URL to PUT the bytes to
expires_in_secondsNoURL lifetime

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations, it discloses important behavior: a one-time signed URL, raw-byte PUT with returned headers, the required confirm_upload follow-up, MIME/kind matching, 100 MB size cap, and 10-file-per-task limit. It does not cover authentication needs, URL expiry, or failure behavior, but it is substantially more informative than the annotations alone.

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 short, front-loaded sentences with no wasted wording. Workflow, constraints, and the follow-up action are all easy to scan.

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 format need not be explained. The description covers the upload mechanics, the follow-up call, the size limit, and the per-task file limit, which is complete enough for this 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 coverage is 0%, so the description must carry parameter meaning. It adds useful constraints such as the 100 MB cap, kind matching, and one-file scope, but it never explains submission_id or filename, leaving clear gaps for two of the four required parameters.

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 states a specific verb and resource: request a one-time signed URL for a sample upload. It clearly distinguishes this from confirm_upload by explaining that PUT happens first and confirm_upload is called afterward.

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?

It gives clear context for when to use it: when the person uploads a sample file themselves, followed by a confirm_upload call. It does not explicitly name alternative upload paths or when not to use this tool, so it falls short of full sibling routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.