Skip to main content
Glama

NudgeHost

by com.nudgehost
OverviewDiscussionsAdmin

create_upload_url

Start an upload for a file this server does not hold, and get back a URL to send the bytes to. Two steps are needed: PUT the bytes to the returned URL with exactly the headers it gives you, then call complete_upload with the id it returns. The link does not work until both have happened. The upload URL is valid for five minutes. If it lapses before the bytes land, call this again for a fresh one rather than reusing the id. size_bytes has to be the exact number of bytes you are about to upload, because it is signed into the URL and storage refuses a body of any other length. Use share_text instead when you already hold the text and want it published in a single call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYesThe name to store the file under, including its extension. Up to 200 characters.
size_bytesYesThe exact number of bytes you are about to upload, as a whole number. This is signed into the upload URL, so a PUT whose body is even one byte longer or shorter is refused by storage. Measure the file rather than estimating.
content_typeYesThe MIME type of the bytes you are about to upload, such as application/pdf or image/png. Send this exact value as the Content-Type header on the PUT. Storage does not check it, so nothing will refuse a PUT that sends a different one. Send it anyway. This value is stored as the file's type and decides how the link serves the file, and a file stored as something its bytes are not is served wrongly.
desired_slugNoOptional. A preferred short name for the public link. It is cleaned up and checked on the server, and one that is taken or unusable is replaced with a random one rather than failing the call. The reply always names the slug that was actually assigned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so richly: a two-step contract, a five-minute expiry, the re-call-on-lapse rule, and that size_bytes is signed into the URL so storage refuses any other length. This is exactly the lifecycle and failure-mode context an agent needs for a multi-step upload.

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?

Front-loads the purpose, then sequences the contract, expiry rule, parameter constraint, and the sibling alternative. Every sentence carries distinct information with no filler, despite the length.

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?

There is no output schema and no annotations, yet the description covers the return shape ('a URL' and 'the id it returns'), the multi-step flow, the expiry window, and the fallback. Nothing an agent needs in order to invoke 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 description coverage is 100%, so the schema already documents all four parameters thoroughly. The description only reinforces the size_bytes signing constraint (already in the schema) and does not add syntax or meaning for filename, content_type, or desired_slug beyond what the schema states, making the baseline 3 appropriate.

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?

States a specific verb+resource ('Start an upload for a file this server does not hold') and the immediate payoff ('get back a URL to send the bytes to'). It distinguishes itself from the sibling share_text explicitly, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use steps (PUT the bytes, then call complete_upload) and names the condition that selects the alternative: 'Use share_text instead when you already hold the text and want it published in a single call.' It also tells the agent what to do if the URL lapses (call again for a fresh one rather than reusing the id).

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

All NudgeHost toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources