Skip to main content
Glama
heindewilde

Yungle

by heindewilde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Prepare a transfer

create_transfer

Prepare a draft file transfer for files on a shell machine and get one upload command per file. Commands carry tokens valid for two hours, resume if interrupted, and share nothing until finalized.

Instructions

Prepare a draft transfer for files that live on a machine with a shell, and return one upload command per file. Each command (npx -y yungle-cli put …) needs no Yungle key: it carries a token that can write only that file, for two hours, and it resumes if interrupted. Nothing is shared and nobody is emailed until the transfer is finalized.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYes
titleNoLabel for the dashboard; never shown to recipients.
expiresInDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / files / items / properties / localPath
      Added value: +{
+  "description": "Where the file is on the machine that will run the command.",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false; the description goes well beyond them. It discloses that the token is write-scoped to a single file, expires in two hours, resumes if interrupted, requires no Yungle key, and that nothing is shared or emailed until the transfer is finalized. That is rich, non-obvious behavioral context consistent with the annotations.

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?

Three front-loaded sentences: what it does and returns first, then the mechanics of the command, then the safety guarantee. Every sentence carries distinct information with no padding or repetition of the schema.

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?

With no output schema, the description usefully explains the return value (one command per file), and annotations cover the mutation safety profile. It mentions finalization but does not name the tool or step that performs it, leaving a small gap in the workflow for an agent that must complete the transfer.

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?

Schema description coverage is only 33%, and the description adds no meaning for the parameters: 'expiresInDays' and the item-level 'name' are undocumented in both places, and 'title'/'path'/'size'/'localPath' explanations come only from the schema. A 2 is warranted because the description does not compensate for the coverage gap on a tool where the draft's lifetime parameter in particular matters.

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 a precise verb+resource ('Prepare a draft transfer') and states exactly what is returned ('one upload command per file'). It also scopes the tool ('files that live on a machine with a shell'), which distinguishes it cleanly from the download-oriented siblings like download_files and get_download_links.

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 a genuine precondition for use ('files that live on a machine with a shell') and clarifies that nothing is shared until finalization, which tells the agent this is a preparatory step. However, it never names an alternative tool or an explicit when-not-to-use condition, so routing is left partly to inference.

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