FileForge

Overview Schema Source Related Servers Discussions Admin

fileforge_report_action

Generate bug report, PR evidence, or debug bundles from the active browser tab to share screenshots, QA results, and diagnostics.

Instructions

Generate evidence bundles from the active tab: a bug report, PR evidence with screenshots and QA results, or a full debug bundle. Use this when you need something to share or attach. Use fileforge_coding_action for context while working. Bundles are saved locally and can contain page data, so review them before sharing. Needs the extension.

Input Schema

Name	Required	Description	Default
`urls`	No	URLs to process.
`tabId`	No	Tab ID, or "active" for the active tab.	active
`title`	No	Report title.
`action`	Yes	What to do. Required parameters are in brackets. bug (title): Generate a bug report bundle from the active tab. pr_evidence (title): Generate a PR evidence bundle (screenshots, QA results, diff). debug_bundle (title): Create a debug bundle with full diagnostics.
`format`	No	Output format.	zip
`include`	No	Evidence to include in the bundle.

Output Schema

Name	Required	Description
`ok`	Yes	False if the action failed or a check did not pass.
`ref`	No	Stored result ID, for fileforge_result_action.
`data`	No	The result. Its shape depends on the action.
`meta`	No	Tool, action and context.
`error`	No	Failure code and message.
`warnings`	No	Notes about a call that still ran.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.3.0Nov 5, 2026

changedInput schema / properties / action / description

Previous value: -"The action to perform. Available actions: bug: Generate a bug report bundle from the active tab. pr_evidence: Generate a PR evidence bundle (screenshots, QA results, diff). debug_bundle: Create a debug bundle with full diagnostics."New value: +"What to do. Required parameters are in brackets. bug (title): Generate a bug report bundle from the active tab. pr_evidence (title): Generate a PR evidence bundle (screenshots, QA results, diff). debug_bundle (title): Create a debug bundle with full diagnostics."

addedInput schema / properties / format / description
```
Added value: +"Output format."
```
addedInput schema / properties / include / description
```
Added value: +"Evidence to include in the bundle."
```

addedInput schema / properties / tabId / description

Added value: +"Tab ID, or \"active\" for the active tab."

addedInput schema / properties / title / description
```
Added value: +"Report title."
```
addedInput schema / properties / urls / description
```
Added value: +"URLs to process."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "query_* actions return their modules as extra top-level fields.",
+  "properties": {
+    "data": {
+      "description": "The result. Its shape depends on the action."
+    },
+    "error": {
+      "description": "Failure code and message."
+    },
+    "meta": {
+      "description": "Tool, action and context."
+    },
+    "ok": {
+      "description": "False if the action failed or a check did not pass.",
+      "type": "boolean"
+    },
+    "ref": {
+      "description": "Stored result ID, for fileforge_result_action."
+    },
+    "warnings": {
+      "description": "Notes about a call that still ran."
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedv0.2.1Nov 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive behavior, so the bar is lower. The description adds genuinely useful context beyond that: bundles are saved locally, may contain page data, should be reviewed before sharing, and require the extension to be installed. It does not describe failure modes or where files land, which keeps it from a 5.

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?

Four short sentences, front-loaded with the core purpose and followed by usage, caveats, and prerequisite. Every sentence carries information; the only mild redundancy is repeating the bundle variants already listed in the action enum.

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?

With an output schema present, return values need not be explained, and the description covers the key non-schema facts an agent needs: the extension prerequisite, local persistence, and the privacy caution about page data. It is complete enough for a six-parameter, single-required-field tool.

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 the schema already documents all six parameters including the action enum variants and their required fields. The description restates the three action types but adds no syntax, defaults, or interaction detail (e.g., how 'include' or 'urls' behave) beyond what the schema provides, so baseline 3 applies.

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 a specific verb and resource ('Generate evidence bundles from the active tab') and enumerates the three concrete variants (bug report, PR evidence, debug bundle). It also names the sibling fileforge_coding_action as the contrasting tool, so an agent can distinguish it 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?

It gives a clear use condition ('when you need something to share or attach') and explicitly routes the agent to fileforge_coding_action for in-progress context. It stops short of stating when not to use it or how it relates to other bundle-producing siblings like fileforge_export_action, but the primary alternative is covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.