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

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_recent_memory_messages

Read-only

Retrieves the most recent messages stored in specified memories, letting agents recall prior conversation context to inform responses and avoid repeating information.

Instructions

Get the most recent messages stored in memories.

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_ids": "<memory_ids>"
    },
    "name": "ragflow_recent_memory_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
agent_idNo
memory_idsYesIDs of the memories to use
session_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, non-destructive, and closed-world, so safety is covered. The description adds only the vague hint that results are ordered toward recency, but says nothing about how many are returned by default, whether it spans sessions/agents, or how the scoping fields behave.

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. It is efficient, though its brevity is part of why the other dimensions are under-specified.

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 not be explained. But with four parameters and three effectively undocumented (limit, agent_id, session_id), and no indication of ordering or scope semantics, the description leaves an agent guessing on how to construct a correct call.

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 25% — only memory_ids is documented in the schema. The description does not explain limit, agent_id, or session_id at all, so it fails to compensate for the three undocumented parameters.

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 ("Get the most recent messages stored in memories"), which is clear on its own. However, it does not distinguish itself from the sibling ragflow_list_memory_messages or ragflow_search_memory_messages, so the agent cannot tell why 'recent' differs from 'list' without opening schemas.

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?

There is no when-to-use guidance, no exclusion of alternatives, and no mention of prerequisites. The word 'recent' implies an ordering intent, but the description never says when to prefer this over list_memory_messages or search_memory_messages.

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