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

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_list_agent_sessions

Read-only

Lists an agent's conversation sessions and messages, filtered by date, user, keywords, or session ID, so you can review and audit interactions.

Instructions

List an agent's conversation sessions with their messages.

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

Input Schema

NameRequiredDescriptionDefault
descNo
pageNoPage number, starting at 1
orderbyNoupdate_time
to_dateNoUpdated on or before this date, YYYY-MM-DD
user_idNoOnly sessions of this end-user ID
agent_idYesAgent ID
keywordsNoMatch session names
from_dateNoUpdated on or after this date, YYYY-MM-DD
page_sizeNoItems per page
session_idNoReturn only this session
include_messagesNoInclude each session's messages

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds that messages are returned with each session, but says nothing about pagination limits, sort behavior, or auth requirements beyond what the schema implies.

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 short sentence with no wasted words. It is front-loaded and readable, though it could be slightly more informative without becoming verbose.

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 and the input schema is rich, so much of the contract is structured elsewhere. However, for an 11-parameter list tool with filtering and pagination, the description leaves the agent without guidance on session filtering, date semantics, or relationship to sibling session tools.

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 82%, so the schema already documents most parameters including page, page_size, date filters, user_id, keywords, session_id, and include_messages. The description references messages but adds no syntax or semantics beyond what the schema provides; baseline 3 is appropriate.

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 (List) and resource (an agent's conversation sessions with messages), which is clear and actionable. It does not explicitly differentiate itself from ragflow_list_chat_sessions or ragflow_get_chat_session in the sibling set, so an agent must infer the distinction.

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 indication of when to use this tool versus alternatives like ragflow_get_agent, ragflow_list_chat_sessions, or ragflow_create_agent_session. There are no exclusions or prerequisites offered.

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