Skip to main content
Glama
Sign In
mcp-vault-reader

mcp-vault-reader

by LucasRocha179
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

memory_status

Check the persistent memory vault status: enabled/disabled, note count, tag count, and disk path. Get insights into memory usage for cross-session context.

Instructions

Returns the status and statistics of the persistent memory vault (enabled/disabled, note count, tag count, disk path).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "memory_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly discloses that the tool returns status/statistics and lists specific data points (enabled/disabled, note count, tag count, disk path). This is transparent for a read-only status operation; no side effects are implied or expected.

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, well-structured sentence that packs all essential information. No wasted words, and the parenthetical list of returned fields improves clarity without verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, no-output-schema tool, the description fully specifies what the tool returns and the key data categories. The complexity is low, and the description is complete enough for an agent to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the baseline for no parameters is 4. The description adds no parameter-specific information because none exist, but also doesn't need to. Schema coverage is trivially 100% as there are no properties.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Returns') and clearly identifies the resource ('status and statistics of the persistent memory vault'), while listing concrete output fields. It distinguishes itself from sibling tools by focusing on vault health/statistics rather than search, read, write, or delete operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for checking vault status/statistics, which is clear context. It doesn't explicitly state when to use this tool instead of alternatives, but there is no direct alternative among siblings for purely status information, so this is sufficient.

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