Skip to main content
Glama
Sign In
Re:portFlow

Re:portFlow

Official
by re-port-flow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

download_zip

Idempotent

Download a ZIP file of generated PDF reports by providing the request ID. The file is saved to your workspace or a specified output directory.

Instructions

generate_pdfs_asyncで生成したZIPファイルをダウンロードします。requestIdを指定し、ローカルのZIPファイルパスを返します。outputDir を指定するとそのディレクトリに、未指定の場合は現在の作業ディレクトリに保存します。

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": {
      "requestId": "<requestId>"
    },
    "name": "download_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestIdYesgenerate_pdfs_asyncで返されたrequestId（UUID）
fileNameNo保存ファイル名（省略時はrequestId.zip）
outputDirNo出力先ディレクトリ (相対/絶対)。未指定時はクライアントのワークスペース (Roots) または現在の作業ディレクトリに保存。ユーザーが場所を指定した場合のみセットすること。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already provide idempotentHint=true and non-destructive nature. The description adds that it saves to a directory and returns a local path, which is useful but not extensive. 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?

Two sentences, front-loaded with the action, no unnecessary words. Every sentence adds value.

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?

For a simple download tool, the description covers how to use it, what to specify, and what it returns. No output schema, but the return is implied. Could mention that it overwrites existing files, but not essential.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds context beyond schema: it explains the behavior of outputDir (saves to current directory if unspecified). This adds value, though fileName is not mentioned.

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 ZIP file generated by generate_pdfs_async, specifies requestId, and returns a local path. This distinguishes it from siblings like download_file.

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?

The description ties the tool to a specific prior tool (generate_pdfs_async), giving clear context. However, it does not explicitly mention when not to use or list alternatives beyond that association.

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