Skip to main content
Glama
Sign In
spoofzy

spoofzy

by spoofzy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Download Spoofzy results

spoofzy_download

Downloads results from a finished Spoofzy run to a local folder without overwriting files. Use it for runs started without download, in the cloud app, by workflow, or earlier before links expire.

Instructions

Save the results of a finished Spoofzy run into a local folder (never overwrites files). Use it for runs started with download=false, in the Spoofzy Cloud app, by a workflow or in an earlier session. Result links expire after a few days, so download promptly.

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": {
      "run_id": "<run_id>"
    },
    "name": "spoofzy_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesA run id from an earlier result (mjob_…, cc_…, api_… or batch_…).
output_dirNoFolder for the results (created if needed). Default: a spoofzy-output folder next to each source file, or the configured SPOOFZY_OUTPUT_DIR.
workflow_idNoA workflow id (wa_…).
wait_secondsNoSeconds to wait for processing before returning (default from SPOOFZY_WAIT_SECONDS, normally 50). Unfinished runs keep processing and are saved when ready while this server runs; check them with spoofzy_get_run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that files are never overwritten, that result links expire after a few days (a real urgency constraint), and that unfinished runs keep processing and are saved later while the server runs. These are non-obvious behavioral traits an agent could not infer from destructiveHint=false or openWorldHint=true alone.

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?

Two tight sentences: the action and non-overwrite guarantee come first, followed by the applicability list and the expiry warning. No redundant restatement of the title or name.

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

Completeness4/5

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

Covers prerequisites, safety behavior, and background-processing semantics for a write-to-disk tool with no output schema. The only gap is that it never says what the call returns (e.g., saved file paths), which matters more here since no output schema exists to fill that in.

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 100%, so run_id formats, output_dir defaults, and wait_seconds behavior are already documented in the schema. The description adds only the general context of which run sources produce downloadable results; it adds no new syntax or semantics beyond the structured fields.

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 and resource ('Save the results of a finished Spoofzy run into a local folder') with the scope qualifier 'finished' that separates it from status-checking siblings like spoofzy_get_run. An agent can tell what this does without opening the schema.

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 concrete when-to-use conditions: runs started with download=false, in the Spoofzy Cloud app, by a workflow, or in an earlier session. It also points to spoofzy_get_run for still-unfinished runs, though it does not explicitly state when NOT to use it (e.g., versus spoofzy_list_saved_originals).

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