Skip to main content
Glama
Sign In

Moatless

by store.moatless
OverviewDiscussionsAdmin

Get a release asset upload URL

release_asset_upload_url

A URL to upload files to a published release, valid for an hour, for a listing that isn't built from GitHub. PUT each file to it as the request body: curl -T <file> <url>, with the URL ending in / so curl adds the file's name, which buyers see. If the listing sells npm packages, upload the .tgz that npm pack makes for each package, and list_releases shows them in the release's npm_packages once they're read.

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": {
      "input": "<input>",
      "context": "<context>"
    },
    "name": "release_asset_upload_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as "the user" or "a buyer".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as \"the user\" or \"a buyer\".",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "input"
-]New value: +[
+  "input",
+  "context"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / input / properties / plan
      Added value: +{
+  "description": "The slug of the listing's plan the files are for, if they're not for its base plan: only\nbuyers of that plan, or one above it, can download them.\n",
+  "type": "string"
+}
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Adds runtime facts that annotations cannot express: the URL expires after one hour, the file must be sent as a PUT body, the URL must end in `/` for curl to attach the filename, and filenames are buyer-visible. It does not state whether the URL is single-use, whether prior assets are replaced, or what auth/permissions the caller needs to mint it.

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?

Front-loads the answer (it returns a URL) and then the operational recipe, with no filler sentences. Loses a little to run-on construction and stray line breaks that interrupt the flow of the npm paragraph.

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?

For a two-parameter tool with no output schema, it covers the whole job: what you get, how long it lasts, how to transmit files, and how to verify (list_releases `npm_packages`). Nothing an agent needs in order to call it correctly is missing.

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 50% and the description adds little parameter-level meaning: release_id is never explained, and plan scoping is only implied by 'buyers see it' rather than by clarifying the plan-tier rule (already in the schema). The npm guidance adds domain context for what to upload, but not for what the parameters mean.

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?

Names the concrete resource (an upload URL for release assets), the target (a published release on a listing not built from GitHub), and the downstream effect (file names visible to buyers). An agent can distinguish it from logo_upload_url, screenshot_upload_url, and remove_release_asset without opening schemas.

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?

Gives a real precondition — the listing must not be built from GitHub — plus a concrete invocation recipe (`curl -T <file> <url>` with a trailing slash, one PUT per file). It stops short of naming what to do instead when the listing IS GitHub-built, and does not contrast with the other *_upload_url siblings.

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

All Moatless toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources