Skip to main content
Glama
Sign In
ragflow-kb-mcp

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_link_files_to_datasets

Destructive

Links file-manager files or folders to RAGFlow datasets as documents in the background without parsing, letting you organize files into knowledge bases for later processing.

Instructions

Turn file-manager files into documents of datasets. Runs in the background and does not parse.

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": {
      "file_ids": "<file_ids>",
      "dataset_ids": "<dataset_ids>"
    },
    "name": "ragflow_link_files_to_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoadd keeps existing links; replace also removes the documents these files have in datasets not listed (an empty dataset_ids list removes all)add
file_idsYesFiles to link; a folder links every file inside it
dataset_idsYesTarget datasets

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds useful behavioral context that this runs asynchronously in the background and does not parse the linked files, but it does not clarify what replace mode removes or how background completion is observed.

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 core action and followed by the most operationally important behavioral caveat. There is no redundant or filler text.

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?

The description is adequate for a tool whose schema is fully documented, annotations carry destructiveness, and an output schema exists. However, it leaves gaps around when to prefer this over related document/dataset tools and how to track the background operation, which are relevant for correct invocation.

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 fully documents file_ids, dataset_ids, and the add/replace mode semantics. The description adds no parameter-level detail beyond what the schema provides, which is the baseline case for fully covered schemas.

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 states a specific action and resource: 'Turn file-manager files into documents of datasets,' which clearly identifies the linking operation. It does not explicitly differentiate from siblings such as ragflow_upload_document or ragflow_ingest_documents, 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 Guidelines2/5

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

The description gives no guidance on when to use this tool instead of alternatives like ragflow_upload_document, ragflow_move_files, or dataset/document ingestion tools. 'Runs in the background and does not parse' is behavioral context, not a usage condition or exclusion.

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