Skip to main content
Glama
Sign In
Fast Browser MCP

Fast Browser MCP

by kqlio67
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_wait_for_download

Waits for a file download to finish in a specified directory by confirming the .crdownload extension is gone. Use it to synchronize automation with completed downloads.

Instructions

Wait for a file download to complete in the download directory without .crdownload extension.

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": {
      "directory": "<directory>"
    },
    "name": "browser_wait_for_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNoMaximum seconds to wait
directoryYesDirectory to watch for completed download
filename_patternNoOptional substring to match filename

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.12.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the completion criterion (no .crdownload extension) but omits what happens on timeout, whether the call blocks, whether it returns file metadata, and any permission or download-path prerequisites.

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?

A single front-loaded sentence with no filler. It is efficient, though the phrasing 'in the download directory without .crdownload extension' is slightly compressed and could be clearer.

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?

The tool is simple and has full schema coverage, but with no annotations and no output schema the description should at least state timeout failure behavior and whether a path must first be configured. Those gaps matter for correct invocation.

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 all three parameters are already documented. The description only reinforces the directory concept and says nothing extra about timeout or filename_pattern behavior, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Wait') and resource ('file download to complete') plus the completion mechanism (absence of .crdownload extension), which is clear. It does not explicitly distinguish itself from the closely related browser_wait_for_network_idle or browser_set_download_path siblings.

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

Usage Guidelines3/5

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

Usage is implied: call this after initiating a download and before consuming the file. However, there is no explicit when-to-use, when-not-to-use, or named alternative, and no guidance on the prerequisite of configuring the download path via browser_set_download_path.

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