FileForge

Overview Schema Source Related Servers Discussions Admin

fileforge_runtime_action

Read-onlyIdempotent

Check FileForge server and extension connectivity, versions, available tools, and recent RPC requests; use status to diagnose bridge or connection errors without touching page content.

Instructions

Check FileForge itself: whether the server and extension are connected, their versions, which tools are available, and recent requests. Use status when other tools report a bridge or connection error. It doesn't touch page content.

Input Schema

Name	Required	Description
`limit`	No	Max entries to return
`action`	Yes	What to do. Required parameters are in brackets. ping: Check that the MCP server is alive. status: Get the current status of the MCP bridge and extension connection. capabilities: List all registered tools and their availability. request_log: Get recent RPC request log entries.
`failuresOnly`	No	Return failed requests only.
`includeDetails`	No	Include extra detail for each entry.

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.

Changed4 schema fields changedv0.3.0Nov 5, 2026

changedInput schema / properties / action / description

Previous value: -"The action to perform. Available actions: ping: Check that the MCP server is alive. status: Get the current status of the MCP bridge and extension connection. capabilities: List all registered tools and their availability. request_log: Get recent RPC request log entries."New value: +"What to do. Required parameters are in brackets. ping: Check that the MCP server is alive. status: Get the current status of the MCP bridge and extension connection. capabilities: List all registered tools and their availability. request_log: Get recent RPC request log entries."

addedInput schema / properties / failuresOnly / description
```
Added value: +"Return failed requests only."
```
addedInput schema / properties / includeDetails / description
```
Added value: +"Include extra detail for each entry."
```

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.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine context beyond them: this is the diagnostic when a bridge/connection fails, and it has no effect on page content.

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?

Three short sentences, front-loaded with the core purpose, then the usage trigger, then the scope exclusion. Nothing is redundant and no sentence is filler.

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?

An output schema exists, so return values need not be explained, and all four parameters are documented. For a simple diagnostic tool this covers what an agent needs; the only small gap is guidance on distinguishing the four actions beyond the enum text.

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 coverage is 100% and the enum already spells out all four actions with bracketed required parameters, so the schema does the heavy lifting. The description's prose summary ('whether the server and extension are connected, their versions...') mirrors the enum rather than adding new semantics such as default or filtering behavior.

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?

States a specific verb and resource ('Check FileForge itself') and enumerates the four things it reports: connection state, versions, available tools, and recent requests. The clause 'It doesn't touch page content' explicitly separates it from the long list of page/content siblings.

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?

Gives a concrete trigger: 'Use status when other tools report a bridge or connection error.' That is clear diagnostic routing, though it names one action rather than mapping when to choose ping vs capabilities vs request_log.

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