Skip to main content
Glama

query_notes

Select Markdown notes by frontmatter fields such as project, tags, or folder, alone or combined; returns each note path with its frontmatter. Use no filter to list notes that have frontmatter.

Instructions

Select notes by their frontmatter: project, tags, folder, or any mix of them. Each result is a note path with its frontmatter. With no filter it returns the notes that have any frontmatter at all.

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

Input Schema

NameRequiredDescriptionDefault
tagsNo
limitNo
folderNo
projectNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose two useful behaviors: results are note paths with frontmatter, and an empty filter returns only notes that have any frontmatter. It does not state that it is read-only, whether results are ordered, or how limit truncates the set.

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?

Two sentences, both load-bearing, with the filterable fields front-loaded and the default behavior stated last. No filler or redundant restatement of the tool name.

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?

An output schema exists, so return values need not be fully explained, and the description still gives the essential shape. The main residual gap for a 4-parameter, zero-annotation tool is limit semantics and tag-matching logic.

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?

Schema coverage is 0%, so the description must compensate; it explicitly maps three of the four parameters (project, tags, folder) to filter roles. It leaves limit undocumented and does not clarify whether tags are ANDed or ORed, or whether project/folder match exactly or by prefix.

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 (select notes) and enumerates the filter dimensions (project, tags, folder), plus how results are shaped. It is clear on its own, though it does not name a sibling such as search_brain or related_notes to distinguish itself from other note-retrieval tools.

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 implied rather than stated: the agent can infer this is for frontmatter-attribute queries, and the no-filter case is explained. However, there is no explicit when-to-use versus when-not, and no pointer to alternatives for full-text or link-based note lookup.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.