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

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_create_agent_session

Start a named conversation session with an agent, then pass the returned session ID to the agent chat tool to continue that conversation.

Instructions

Start a named conversation with an agent; pass its id as session_id to ragflow_agent_chat.

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_create_agent_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSession name
agent_idYesAgent ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the result is an id to be reused later, but says nothing about session persistence, lifetime, duplication rules, or side effects on the agent.

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 front-loaded clause pair with zero filler: the action first, the downstream wiring second. Nothing to trim.

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?

With an output schema, full parameter coverage, and explicit annotations, most of the burden is already handled elsewhere. The only meaningful gap is the lack of differentiation from ragflow_create_chat_session and any note about session scoping or reuse.

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% with only two parameters, so the schema already documents name and agent_id adequately. The description hints that name is optional-by-nature ('named') but adds no syntax, constraints, or default behavior beyond the schema.

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: 'Start a named conversation with an agent' — clearly a session-creation operation. It ties itself to ragflow_agent_chat, which separates it from generic chat-session siblings, though it never explicitly contrasts with ragflow_create_chat_session or ragflow_create_agent.

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?

Implies usage through the workflow hint 'pass its id as session_id to ragflow_agent_chat', which tells the agent this is a prerequisite step. However, no when-not conditions, prerequisites (e.g. must the agent exist?), or named alternatives are given.

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