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

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_update_agent

Update an RAGFlow agent's title, description, permissions, or graph and publish it by setting release=true; include release=true on every update to keep a published agent published.

Instructions

Change an agent's title, description, permission or graph, and publish it with release=true.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "ragflow_update_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
dslNoReplacement graph (DSL); saved as a new version
titleNo
releaseNoPublish the agent. RAGFlow writes this flag on every update, so an update without release=true unpublishes a published agent
agent_idYesAgent ID
permissionNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive write; the description adds the key behavioral fact that this mutation can publish (or, per the release parameter, unpublish) an agent, which is not derivable from the annotations. It stops short of stating that omitted fields are left unchanged or that the DSL is versioned.

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?

A single sentence with no filler, front-loading the verb and resource before the field list and the publish note. Every clause carries information an agent needs.

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 and annotations cover return values and safety, so the description need not explain those. However, for a six-parameter partial-update mutation it never clarifies whether unspecified fields are reset or preserved, which is the main ambiguity an agent would face.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 50% schema coverage, the description must compensate, and it does by naming the four settable fields (title, description, permission, graph) and pointing at release=true. It still leaves null-vs-omitted semantics and the 'new version' behavior of dsl unexplained in the description.

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?

Names a specific verb (change/update) plus the resource (agent) and enumerates the affected fields (title, description, permission, graph). It is clearly distinguishable from ragflow_create_agent, ragflow_get_agent and ragflow_delete_agent by the verb, though the description never explicitly contrasts with them.

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 clause 'publish it with release=true' implies when the flag should be supplied, but there is no explicit when-to-use/when-not guidance and no mention of siblings such as create_agent versus update_agent. Usage context is implied rather than stated.

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