Skip to main content
Glama
clawborrator

clawborrator-mcp

by clawborrator
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

download_to_path

Download a binary file from the hub by fileId to a local path for processing. Returns the absolute path of the written file, which must be used in follow-up commands.

Instructions

Download a hub-stored file by fileId to a local path. Use this for BINARY files (PDFs, images, archives, video, etc.) that read_file can't return inline, or whenever you need the bytes on local disk for processing (e.g. running Bash pdftoppm, Read on an image, unzip). The parent directory is created if missing; the target must NOT already exist (remove it first if you need to refetch). Returns the ABSOLUTE path the file was written to — always use that exact path verbatim in your follow-up Read/Bash, do not reconstruct it from the path you passed. (The path arg is resolved against the MCP subprocess's working directory, which is not guaranteed to match claude's own cwd; the returned absolute path is the source of truth.) Same ACL as read_file: row must live in this agent's session (i.e. the file was forward-cloned here by the hub, or you uploaded it here yourself).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesRelative path for the download, e.g. "tmp/doc.pdf". Parent dirs are auto-created. Target must not already exist. NOTE: resolved against the MCP process cwd — read the absolute path back from the tool result rather than assuming where it landed.
fileIdYesThe fileId to download (typically from a routed prompt mentioning fileId=N).

Tool Definition Quality

A5/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: parent directory creation, non-existence requirement, return of absolute path, ACL constraints, and resolution quirks. No contradictions.

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?

The description is slightly long but every sentence adds necessary information, starting with the main purpose, then use cases, then behavioral details, then return value. No redundancy.

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?

Given the tool's simplicity (2 params, no output schema), the description covers all needed context: purpose, usage, behavior, return value, and access control. It is fully sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds important context: for 'path' it explains auto-creation, existence check, and resolution; for 'fileId' it gives usage hints. This significantly supplements the schema.

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 downloads a hub-stored file by fileId to a local path, and explicitly distinguishes it from read_file for binary files. This qualifies as a specific verb+resource with sibling differentiation.

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?

The description explicitly says to use for binary files and when bytes on disk are needed, and contrasts with read_file for text, providing clear when and when-not guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/clawborrator/channel_v1'

If you have feedback or need assistance with the MCP directory API, please join our Discord server