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

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_list_memory_messages

Read-only

Lists stored dialogue messages for a memory, the memories extracted from each message, and extraction progress so you can inspect and track memory processing.

Instructions

List a memory's stored dialogue messages, the memories extracted from each, and extraction progress.

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": {
      "memory_id": "<memory_id>"
    },
    "name": "ragflow_list_memory_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
agent_idsNoOnly messages from these agents
memory_idYesMemory ID
page_sizeNoItems per page (max 100)
session_idNoOnly messages of this session

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds that each message carries its extracted memories and extraction progress, but says nothing about pagination behavior or ordering despite the page/page_size parameters.

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 well-formed sentence with no filler, and the key content is front-loaded. Slightly terse given the tool's filtering capabilities, but nothing is wasted.

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?

An output schema exists, so return values need not be spelled out, and the description still sketches the payload shape. Combined with complete schema coverage and read-only annotations, an agent has enough to call this correctly; only the relationship to sibling listing tools is missing.

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%, so all five parameters, including agent_ids, session_id, page and page_size, are documented in the schema itself. The description adds no filtering or paging semantics beyond that, so 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 (list) and resource (a memory's stored dialogue messages), and adds that the response also contains the memories extracted per message plus extraction progress. That is clear and distinguishable from ragflow_get_memory_message, but it never names the sibling listing tools it differs from.

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?

No when-to-use or when-not-to-use guidance, and no mention of alternatives such as ragflow_search_memory_messages or ragflow_recent_memory_messages, which an agent could easily confuse with this tool. The use case is only implied by the word 'List'.

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