Skip to main content
Glama
Sign In
pironjulien

nexus-browser

by pironjulien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_download_status

Read-onlyIdempotent

Lists recent Chrome downloads with name, state, bytes received, and danger status so you can track a file's download progress and safety.

Instructions

Lists recent Chrome downloads (name, state, bytes received, danger) to track a downloaded file.

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
dataYes
statusYes
warningNoEmergency stop hotkey not held, or similar notice
untrusted_noteNoPage text that looks like instructions aimed at an AI

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv2.31.6
    • addedOutput schema / $defs
      Added value: +{
+  "Download": {
+    "additionalProperties": true,
+    "properties": {
+      "bytesReceived": {
+        "type": "number"
+      },
+      "danger": {
+        "type": "string"
+      },
+      "endTime": {
+        "type": "string"
+      },
+      "filename": {
+        "type": "string"
+      },
+      "id": {
+        "type": "integer"
+      },
+      "mime": {
+        "type": "string"
+      },
+      "startTime": {
+        "type": "string"
+      },
+      "state": {
+        "type": "string"
+      },
+      "totalBytes": {
+        "type": "number"
+      }
+    },
+    "title": "Download",
+    "type": "object"
+  }
+}
    • addedOutput schema / additionalProperties
      Added value: +true
    • addedOutput schema / description
      Added value: +"Recent Chrome downloads."
    • addedOutput schema / properties / data
      Added value: +{
+  "items": {
+    "$ref": "#/$defs/Download"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • addedOutput schema / properties / status
      Added value: +{
+  "const": "success",
+  "type": "string"
+}
    • addedOutput schema / properties / untrusted_note
      Added value: +{
+  "description": "Page text that looks like instructions aimed at an AI",
+  "type": "string"
+}
    • addedOutput schema / properties / warning
      Added value: +{
+  "description": "Emergency stop hotkey not held, or similar notice",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "status",
+  "data"
+]
    • changedOutput schema / title
      Previous value: -"browser_download_statusOutput"New value: +"DownloadsAnswer"
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds the list of return fields (name, state, bytes received, danger), which is useful context, but it omits behavior like the default limit or whether results are paginated.

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?

A single sentence with no wasted words, front-loading the core action and following with useful return-field detail.

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?

With an output schema present, the description need not explain return values, and annotations cover safety. However, the undocumented 'limit' parameter and the lack of routing guidance versus browser_wait_download leave gaps for an agent trying to invoke it correctly.

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

Parameters2/5

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

The sole parameter 'limit' has 0% schema description coverage, and the description does not mention it at all. The schema supplies only a type and default, leaving the meaning and effect of 'limit' entirely unexplained.

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?

The description gives a specific verb and resource ('Lists recent Chrome downloads') and enumerates the returned fields, making the tool's function immediately clear. It does not explicitly differentiate itself from the closely related sibling browser_wait_download, so it falls short of a 5.

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?

The phrase 'to track a downloaded file' implies the use case, but there is no explicit guidance on when to choose this tool over browser_wait_download or browser_upload. The agent must infer the appropriate context.

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