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

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_get_uncommitted_changes

Read-only

Lists files in a workspace that changed since the last commit, helping you review uncommitted edits before syncing or committing.

Instructions

Show files in a workspace that changed since its last commit (like git status).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
dataset_idNoDataset ID; resolves to the dataset's folder. Use instead of workspace_id.
workspace_idNoWorkspace = a folder in the file manager; pass its folder ID. Use dataset_id instead to address the folder that holds a dataset's files.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the safety bar is covered. The description adds the useful semantic that results are relative to the last commit, but says nothing about behavior when no commit exists yet or about pagination/volume of results.

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?

One short sentence, scoped condition and resource front-loaded, with the git-status analogy doing a lot of work in three words. Nothing is wasted.

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?

An output schema exists, so return shape needn't be explained. However both parameters are optional with null defaults and the description never says what happens if neither is supplied, nor what counts as a 'change' (content vs metadata vs rename) — relevant ambiguities for a diff-style tool in a workspace with branching commit history.

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%: both optional parameters are documented in-schema, including the 'use dataset_id instead of workspace_id' disambiguation. The description itself contributes no parameter guidance, so the baseline 3 applies.

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?

States a specific verb and resource (show files that changed since the last commit) and scopes it to a workspace. The 'like git status' analogy sharply distinguishes it from ragflow_list_files and ragflow_list_commits, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

The 'changed since its last commit' condition implies when to reach for it over a plain file listing, but there is no explicit when-not guidance or pointer to the obvious alternatives (ragflow_diff_commits, ragflow_list_commit_files). Usage must be inferred from the git analogy.

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