FileForge

Overview Schema Source Related Servers Discussions Admin

fileforge_sql_action

Query FileForge stored results with SELECT-only SQL: list tables, inspect schemas, read rows, and export query output to CSV, JSON, or Markdown.

Instructions

Query FileForge's stored results with SELECT-only SQL. Use list_tables and describe_table to see the schema, query to read rows, and export_query to write rows to a file. Covers saved results and scraped pages, links and tables, not the live browser. Use fileforge_result_action to fetch a single known ref. Works without the extension.

Input Schema

Name	Required	Description	Default
`ref`	No	Optional result ref to scope the query
`limit`	No	Maximum items to return.
`query`	No	SQL SELECT statement
`table`	No	SQL table name.
`action`	Yes	What to do. Required parameters are in brackets. list_tables: List all available SQL tables. describe_table (table): Describe the columns and schema of a table. query (query): Run a SQL SELECT query against stored data. export_query (query): Run a SQL query and export the results to a file.
`format`	No	Output format.	csv
`offset`	No	Items to skip, for paging.
`filename`	No	Output filename.

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: list_tables: List all available SQL tables. describe_table: Describe the columns and schema of a table. query: Run a SQL SELECT query against stored data. export_query: Run a SQL query and export the results to a file."New value: +"What to do. Required parameters are in brackets. list_tables: List all available SQL tables. describe_table (table): Describe the columns and schema of a table. query (query): Run a SQL SELECT query against stored data. export_query (query): Run a SQL query and export the results to a file."

addedInput schema / properties / filename / description
```
Added value: +"Output filename."
```
addedInput schema / properties / format / description
```
Added value: +"Output format."
```
addedInput schema / properties / limit / description
```
Added value: +"Maximum items to return."
```
addedInput schema / properties / offset / description
```
Added value: +"Items to skip, for paging."
```
addedInput schema / properties / table / description
```
Added value: +"SQL table name."
```

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

Behavior4/5

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

Adds real context beyond the annotations: data is SELECT-only, scoped to stored results rather than live pages, and the tool works without the browser extension. It doesn't describe export side effects (file location, overwrite behavior) or result-size behavior, which matters given readOnlyHint=false and an export action that writes to disk.

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?

Five short sentences, front-loaded with the core verb and scope, then workflow, then exclusions and prerequisites. No filler or restatement of the title.

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?

Covers scope, workflow, sibling routing, and the extension dependency, which is ample for an 8-parameter tool with an output schema that carries return-value detail. Minor gap: nothing on paging limits or what export_query produces on disk.

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% and the action enum already documents what each action requires in brackets, so the description adds little parameter-level detail. It reinforces the action workflow but says nothing about ref scoping, limit/offset paging, or format/filename pairing beyond what the schema states.

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 ('Query FileForge's stored results with SELECT-only SQL') and bounds the data domain to saved results and scraped pages, links, and tables. It explicitly rules out the live browser and names fileforge_result_action as the sibling for a single known ref, so an agent can separate it from browser/scrape tools without opening a schema.

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

Usage Guidelines5/5

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

Gives a concrete workflow: list_tables and describe_table for schema discovery, query to read rows, export_query to write to a file. It also states the exclusion ('not the live browser') and the alternative for single-ref retrieval, which is exactly the when-to-use/when-not guidance an agent needs.

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