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

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_update_chat

Updates a chat assistant's configuration, including model settings, prompt options, datasets, and retrieval parameters, while merging changed values into existing settings.

Instructions

Change some settings of a chat assistant; llm_setting and prompt_config are merged into the existing ones.

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": {
      "chat_id": "<chat_id>"
    },
    "name": "ragflow_update_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
top_kNo
top_nNo
llm_idNo
chat_idYesChat assistant ID
languageNo
rerank_idNo
dataset_idsNoDatasets the assistant retrieves from
descriptionNo
llm_settingNoKeys to change in the model settings; other keys stay
prompt_configNoKeys to change in the prompt settings; other keys stay
meta_data_filterNo
similarity_thresholdNo
keywords_similarity_weightNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations only tell the agent this is a non-destructive, non-open-world write. The description usefully adds merge semantics for llm_setting and prompt_config, which annotations can't convey. However, it doesn't state whether the other 12 parameters are overwritten or ignored when omitted, nor whether changes are reversible — a notable gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no filler — the partial-update claim comes first and the merge caveat follows. It is appropriately sized, though the terseness contributes to the documentation gaps elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 values need no explanation, but with 14 optional parameters and 29% coverage the description should clarify what happens to unspecified settings and how the nested objects merge. It covers merging for only two of the mutation fields, leaving the semantics of the rest unclear.

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

Parameters2/5

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

Schema description coverage is only 29% across 14 parameters, so the description needs to compensate and doesn't. It only discusses llm_setting and prompt_config, and that content largely repeats the schema's own notes ('Keys to change...; other keys stay'); fields like top_k, top_n, similarity_threshold and meta_data_filter remain undocumented anywhere.

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 ('Change some settings of a chat assistant'), which is clearly distinct from sibling operations like get_chat or delete_chat. The word 'some' implies a partial update, which informally distinguishes it from ragflow_replace_chat_settings, though that sibling is never named.

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 phrase 'Change some settings' implies partial-update usage and the merge note hints at when this tool is preferable to a full replace, but no explicit comparison with ragflow_replace_chat_settings is given. The agent must infer the when-to-use rule from the word 'some' rather than from a stated condition.

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