flowforge-mcp

flowforge_manage_documents

Destructive

Upload, import, read, delete, link, and reindex knowledge documents for AI agents, with content extraction and embedding refresh to keep retrieval sources current.

Instructions

Upload, import, read, delete, link and reindex knowledge documents.

Typical flow: flowforge_manage_knowledge_bases create -> upload or import_url into it -> set the assistant's knowledge_base_id and enable_rag_tool=true -> verify with flowforge_search_knowledge.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 6, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the description only needs to add nuance. It does add that delete requires confirm=true and that reindex without IDs hits all documents, but it doesn't warn about irreversibility of delete, ingestion latency, or size limits.

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?

Two short sentences, front-loaded with the verb list followed by a compact arrow-style flow. No filler text.

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 the multi-action surface and the surrounding tool chain well, and an output schema exists so return values don't need explaining. Missing are preconditions such as file-size or URL-crawl limits and what happens on partial failure during bulk reindex.

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?

The schema's coverage metric is low for the wrapper, but the nested ManageDocumentsInput documents every field with per-action tags (url for import_url, file_path for upload, document_ids required for link_to_agent), so the description doesn't need to repeat them. Its only added meaning is the typical action flow.

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 specific verbs (upload, import, read, delete, link, reindex) plus the resource (knowledge documents), and distinguishes itself from flowforge_list_documents and flowforge_manage_knowledge_bases by naming the knowledge base tool as a separate step.

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?

Provides an explicit end-to-end flow: create a knowledge base, upload or import_url, set knowledge_base_id with enable_rag_tool=true, then verify with flowforge_search_knowledge. It names the alternative tools and the order in which to use them, which is exactly what an agent needs.

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

Deploy Server