Skip to main content
Glama
Sign In
stashcat-api-mcp

stashcat-api-mcp

by dclausen01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

download_file

Download a file from Stashcat by file ID and receive its contents base64-encoded for further processing.

Instructions

Downloads a file and returns it as base64.

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": {
      "file_id": "<file_id>"
    },
    "name": "download_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
e2e_ivNoEncryption IV if encrypted
file_idYesFile ID to download
encryptedNoWhether the file is encrypted

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the return format (base64) but does not mention encryption handling (despite e2e_iv and encrypted parameters), required permissions, or behavior on missing files. This is a significant gap for a tool with encryption-related parameters.

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 a single, efficient sentence that front-loads the core purpose and return format. Every word adds value, with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple download tool, the description is minimally viable. It covers the primary action and return type, and the schema documents all parameters. However, it lacks usage guidance and behavioral context, especially regarding encryption, which is important given the tool's parameter set and absence of an output schema.

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 baseline is 3. The description adds no extra meaning beyond what the schema already provides for parameters like file_id, e2e_iv, and encrypted. It does not clarify how encryption parameters affect the download behavior.

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 uses a specific verb 'downloads' and a clear resource 'file', explicitly stating the return format as base64. This distinguishes it from sibling tools like get_file_info (metadata) and upload_file (opposite direction).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or scenarios where another tool would be more appropriate (e.g., get_file_info for metadata only).

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

Deploy Server

Other Tools