Skip to main content
Glama
Sign In
wraith-mcp

wraith-mcp

by Koreahwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_downloads

Find files downloaded during a browser session, showing their saved paths. Use after triggering a download to locate the file on disk.

Instructions

List files downloaded in this session, with their paths.

Files are saved to ./downloads by default (override with BROWSER_DOWNLOADS_PATH). Call this after a click/navigate that triggers a download to find the saved file.

Args: session_id: Session to inspect (default: "default")

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_downloads"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idNodefault

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals the default save directory ('./downloads') and the BROWSER_DOWNLOADS_PATH override, which is useful operational context. It does not explicitly state that the operation is non-destructive, but the verb 'list' and inability to modify files make that apparent.

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 compact and well-structured: purpose sentence, path/override context, usage timing, and argument documentation. Every sentence 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.

Completeness5/5

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

For a simple listing tool with an output schema, the description covers the core purpose, when to use it, the parameter semantics, and an important environment variable detail. No significant gaps remain for an agent to invoke it correctly.

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?

The schema provides only a default value for session_id with no description, and schema description coverage is 0%. The description compensates by including 'Args: session_id: Session to inspect', clarifying the parameter's meaning. Though minimal, this is necessary and sufficient for a single obvious parameter.

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 opens with 'List files downloaded in this session, with their paths', using a specific verb and resource. This clearly distinguishes the tool from sibling navigation and content tools, and immediately conveys its function.

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 explicitly says 'Call this after a click/navigate that triggers a download', providing clear timing guidance. It does not name alternatives or exclusions, but no sibling tool serves a similar download-listing purpose, so the context is sufficient.

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