Skip to main content
Glama

Kariaa Agents

Get a link to upload samples from a phone

get_upload_link

Use when you cannot send file bytes yourself. A one-tap link to this task's upload page on kariaa.com, already signed in, where the person picks their photos, voice notes or videos from their phone or computer. Use it whenever you cannot send the file bytes yourself (chat apps). The link works once, for 15 minutes; give it to the person as is.

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>"
    },
    "name": "get_upload_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
submission_idYes

Output Schema

NameRequiredDescriptionDefault
urlNoOne-tap upload page link
signed_inNoWhether the link signs the person in
expires_in_minutesNoLink lifetime

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With only generic annotations (readOnlyHint=false, openWorldHint=false, destructiveHint=false), the description carries real behavioral weight: the link is single-use, expires after 15 minutes, comes pre-signed-in so the recipient needs no auth, and must be handed over unmodified. Single-use and expiry are operational constraints an agent would otherwise get wrong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The opening trigger condition is front-loaded well, but the same idea is restated mid-description ('Use it whenever you cannot send the file bytes yourself (chat apps)'), making the sentence redundant. The useful constraints (single use, 15 minutes, signed in) are packed at the end rather than emphasized.

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

Completeness4/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 described, and the description covers the aspects an agent must know to hand the link off correctly: expiry, single use, and pre-authentication. The remaining gap is the unexplained submission_id, which is the one thing the agent must supply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter, submission_id, has 0% schema description coverage, so the description must compensate — and it does not explain the parameter at all. Worse, it refers to 'this task's upload page' while the schema takes a submission_id, leaving the agent to guess whether the identifier scopes a task or a submission.

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 names the concrete artifact (a one-tap, pre-authenticated upload link to this task's page on kariaa.com) and what the recipient does with it (picks photos, voice notes or videos from phone or computer). That is a specific verb-plus-resource, and it is clearly distinct from siblings like submit_samples, which send bytes directly.

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 an explicit trigger condition — 'use when you cannot send file bytes yourself' — and a concrete example context ('chat apps'), which implicitly tells the agent not to use it when it can send bytes itself. It stops short of naming the preferred alternative tool for the direct-send case, so the routing is implied rather than spelled out.

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.