Skip to main content
Glama

Data Cleaner

Open an upload slot

upload_request

Get a FILE FROM THE USER -- a file on their computer or phone, or one they attached to this chat. You cannot send a file's bytes yourself: an attachment lives in a sandbox that has no connection to this service, and a file must never be retyped or base64'd into a tool call. Instead the user sends it from their own browser:

  1. call upload_request -- you get an upload_page link and an upload_id

  2. give the user the upload_page link, exactly as returned, and ask them to open it, choose the file there, and tell you when it is done

  3. when they say so, call upload_confirm(upload_id=...) -- it cleans the file and returns the table The link is for one file and is private to this conversation; it takes CSV, Excel, JSON, XML, Parquet or a zip of one, of any size. If the data is at a URL, use fetch instead -- no upload needed.

With a shell (a coding agent), the same slot takes the file directly, no page: curl -X PUT --data-binary @/path/to/file '<put_url>' The shell alternative needs a shell that reaches data-cleaner.com directly: one on the user's machine does; the assistant's own sandbox (where chat attachments live, under /mnt/user-data/) does NOT -- its proxy answers 403 host_not_allowed. From a chat, use the upload page.

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_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameNooriginal filename, for format inference at confirm

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the generic safety profile (readOnlyHint=false, destructiveHint=false), so the description carries the real burden and does: the link is single-file, private to the conversation, format-limited (CSV, Excel, JSON, XML, Parquet, or a zip), and size-unlimited. It also discloses the critical failure mode for the shell path — the assistant's own sandbox gets 403 host_not_allowed through its proxy — which is behavior no annotation or schema could convey.

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?

The core instruction and the numbered flow are front-loaded and waste no words. The shell/curl section is long relative to the rest and repeats the 'use the upload page from a chat' point already made implicitly, but that redundancy targets a real agent failure mode, so it mostly earns its place.

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?

An output schema exists, so return values needn't be explained, and the description still names the key returned fields (`upload_page`, `upload_id`, and `put_url` for the shell path). For a tool whose real complexity is the multi-step handoff and environment constraints, nothing an agent needs 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?

The single `filename` parameter has 100% schema description coverage ("original filename, for format inference at confirm"), so the schema does the work here. The description never mentions the filename argument or how it affects format inference, adding no meaning beyond the schema. Baseline 3 is appropriate when schema coverage is complete.

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 opens with a concrete verb+resource framing ("Get a FILE FROM THE USER") and states exactly what the tool produces: an `upload_page` link and an `upload_id`. It distinguishes itself from `upload_confirm` (the next step) and from `fetch` (for data already at a URL), so an agent can route correctly without opening any 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?

It gives an explicit when-to-use (user has a file on their computer/phone or attached to chat), an explicit when-not ("If the data is at a URL, use `fetch` instead -- no upload needed"), and a named alternative path for shell-capable agents. The three-step flow tells the agent precisely what to do after calling, including waiting for the user's confirmation before calling `upload_confirm`.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources