Skip to main content
Glama
Sign In
Aktar

Aktar

Official
by getaktar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Upload the clipboard

upload_clipboard

Upload the file or image on the clipboard to cloud storage and get a shareable link anyone can open. Optionally set an expiry or request a short link.

Instructions

Upload the file or image on the user's clipboard and return its link. The file becomes reachable by anyone with the link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upload_clipboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
shortNotrue makes a short link with the destination's link shortener (even if its rules would skip this one), false makes none. Leave out to let the destination's setting decide.
expiresNoDelete after this many days. 0 or left out keeps the file.
destinationNoDestination name or ID from list_destinations. Leave out to let Aktar choose.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations declare this is not read-only and is open-world, but they don't say anything about visibility. The description fills that important gap by stating the file becomes reachable by anyone with the link, and it also states the return value even though no output schema exists. It says nothing about authentication, permanence, or what happens on repeat calls (idempotentHint=false).

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?

Two tight sentences with no wasted words; the action is front-loaded and the visibility caveat follows immediately. Slightly more detail on public exposure timing (at upload vs. link use) could have been added without bloat.

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?

For a zero-required-param upload tool with no output schema, the description covers the essential points: source (clipboard), result (a link), and the public-exposure consequence. Gaps around auth or overwrite behavior are minor given the annotations and the complete schema.

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 all three parameters (short, expires, destination) are fully documented in the schema, including enum values and defaults. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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+resource: it uploads whatever file or image currently sits on the user's clipboard, and it says it returns the link. The 'clipboard' scoping makes it clearly distinct from upload_file in practice, though the description never explicitly contrasts with it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no reference to alternatives such as upload_file or create_short_link. The only implicit steer is that it operates on whatever is on the clipboard, which the agent must infer.

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

Deploy Server

Other Tools