Skip to main content
Glama
Sign In
Ruflo GPT

Ruflo GPT

by furkanhos16
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

memory_stats

Read-only

Retrieves memory storage statistics and HNSW index status to monitor project-scoped persistent memory usage, with data isolated by project path.

Instructions

Get memory storage statistics including HNSW index status Use for project-scoped persistent memory. Never import personal memory automatically. Data is isolated by project_path; runtime reports actual embedding and storage backend.

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": {
      "project_path": "<project_path>"
    },
    "name": "memory_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathYesAbsolute path to the existing project directory. Always use the current task workspace. Each canonical path has its own isolated Ruflo store.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 useful behavioral context that data is isolated by project_path and that runtime reports the actual embedding/storage backend, but the phrasing is terse and it does not describe the shape of the statistics returned.

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

Conciseness3/5

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

The content is short, but the sentences run together without punctuation ('...HNSW index status Use for...'), which hurts front-loading and readability. The final sentence mixes two ideas (isolation and runtime backend reporting) in one clause.

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?

For a read-only stats tool with no output schema, the description covers the essential points: what is measured (storage stats, HNSW index status) and the isolation/backend caveats. An agent has enough to call it correctly, though the return shape is only loosely implied.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already explains project_path in detail (absolute path, isolated Ruflo store). The description reinforces isolation by project_path but adds no syntax or format beyond the schema, making 3 the baseline.

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+resource: 'Get memory storage statistics including HNSW index status'. This is clearly distinguishable from siblings like memory_store, memory_search, and memory_list. It does not, however, explicitly name a sibling it is not, so it falls short of a 5.

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?

'Use for project-scoped persistent memory' hints at the scenario but never says when to pick this over memory_list or memory_search. 'Never import personal memory automatically' is a constraint rather than usage guidance, and no when-not conditions 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