Skip to main content
Glama
markdown-memory-mcp

markdown-memory-mcp

by amercans

lint_vault

Check a Markdown memory vault for broken links, missing frontmatter, duplicate names, orphan notes, and an oversized index, returning structured findings for repair.

Instructions

Check the vault for broken links, missing frontmatter, duplicate names, orphans and an oversized index. Takes no arguments.

Returns {findings: [{code, level, path, line, message}]}. Codes VR001-VR010.

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": "lint_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Check' implies a read-only inspection and the enumerated findings imply nothing is repaired, but the description never states that the vault is not modified, nor does it mention cost or scanning scale for a whole-vault operation. The return shape and code range are useful additions that annotations would not have covered.

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?

Three short sentences: what it checks, that it needs no input, and the exact return shape with code range. The definition leads with the check list and contains no padding.

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?

With no output schema, describing the findings array and VR001-VR010 codes is exactly the missing information an agent needs to interpret results, and the no-argument statement resolves the empty schema. The only gap is the absence of any statement that the operation is non-mutating and how expensive a full-vault scan is.

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?

Zero parameters means the baseline is 4, and 'Takes no arguments' reinforces that the schema's empty object is intentional rather than an omission. No further parameter meaning is needed.

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 (check) plus resource (the vault) and enumerates the exact checks: broken links, missing frontmatter, duplicate names, orphans, oversized index. That list clearly separates it from backlinks, read_note, and search_notes, none of which perform validation.

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?

Usage is only implied: 'Check the vault' suggests running it to validate vault health, and 'Takes no arguments' signals it is a whole-vault sweep rather than a targeted query. There is no explicit statement of when to prefer it over the sibling lookup tools or after which operations it should run.

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