Skip to main content
Glama
Sign In
knowledge-to-action-mcp

knowledge-to-action-mcp

by tac0de
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vault.list_notes

Read-only

List notes from the vault using optional folder, glob, and limit parameters for deterministic ordering.

Instructions

List notes in the vault using deterministic ordering.

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": "vault.list_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderNo
globNo
limitNo

Output Schema

NameRequiredDescriptionDefault
notesYes
totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true (safe read) and openWorldHint=false. The description adds 'deterministic ordering', a useful behavioral trait beyond annotations, but lacks details on default behavior, pagination, or effect of optional parameters.

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?

Single short sentence, no redundant words, front-loaded with action and key differentiator.

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?

Despite having an output schema, the description is too minimal for a listing tool with three optional filters. It omits default behavior, ordering details, and whether filters are required.

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 0%, so the description must compensate for three parameters (folder, glob, limit). It does not mention any parameter or explain how they affect the result, leaving the agent to guess.

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?

Description clearly specifies the action (list), the resource (notes in the vault), and a distinctive ordering property (deterministic ordering). This differentiates it from sibling tools like vault.search_notes and vault.read_note.

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?

The description implies when to use this tool (listing notes with deterministic order for pagination or comparison) but does not explicitly state when not to use it or provide alternatives.

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