BetaFinds

request_asset_upload

Get a one-time link to upload a release file (Windows/Mac/Android/Linux, up to 1 GB). Then upload the file: curl -T ''. After uploading, call complete_asset_upload.

Input Schema

TableJSON Schema

Name	Required	Description
`size`	Yes	File size in bytes (exact)
`sha256`	No	File SHA-256 (hex, optional)
`filename`	Yes	File name, e.g. MyApp-1.4.0.dmg
`platform`	Yes	File platform
`release_id`	Yes	Release ID from create_release

Output Schema

TableJSON Schema

Name	Required	Description	Default
`assetId`	No
`uploadUrl`	No
`downloadUrl`	No
`instructions`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 8, 2026

addedInput schema / properties / platform / description
```
Added value: +"File platform"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "assetId": {
+      "type": "string"
+    },
+    "downloadUrl": {
+      "type": "string"
+    },
+    "instructions": {
+      "type": "string"
+    },
+    "uploadUrl": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description discloses that the link is one-time and includes a practical curl command. Annotations (readOnlyHint false, destructiveHint false) are consistent. The description adds useful context beyond annotations, such as the file size limit and the recommended upload method.

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?

Two concise sentences: first states purpose and scope, second gives actionable steps. No redundant information; every sentence earns its place.

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?

Given the presence of an output schema, the description adequately covers the tool's role without explaining return values. It mentions the follow-up step (complete_asset_upload) and file size limits. Could briefly mention error scenarios, but overall sufficient for a straightforward multipart upload process.

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 baseline is 3. The description does not add significant detail about individual parameters beyond the schema (e.g., size, sha256), but it provides overall context that ties parameters to the upload process.

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 clearly states the tool's purpose: 'Get a one-time link to upload a release file' with explicit platform and size limits. It distinguishes from siblings like 'complete_asset_upload' and 'upload_image' by describing its role in a two-step process.

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?

The description provides explicit steps: get a link, upload via curl, then call complete_asset_upload. This guides the agent on when to use and what to do next, though it does not explicitly state when not to use this tool (e.g., for images).

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

All BetaFinds tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.