Skip to main content
Glama
shaqmughal

seekstone

by shaqmughal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

query_notes

Read-only

Filter notes by frontmatter properties, tags, folders, modified time, or size, returning compact rows like path and title. Use this instead of text search when querying metadata rather than content.

Instructions

Structured metadata query — filter notes by frontmatter key/value predicates, tag, folder, modified time, and size. Returns compact rows (path + title by default; opt into more via select), not note content. Use this instead of search when filtering by properties rather than text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoRestrict to notes with this tag. # optional, case-insensitive; nested child tags match ("project" matches project/alpha).
sortNoSort field (default path).
limitNoMax results (1–500, default 100).
orderNoSort order (default asc).
whereNoFrontmatter predicates — all must match (AND).
folderNoRestrict to a vault-relative folder prefix.
selectNoExtra fields per hit: frontmatter keys, or "mtime", "size", "tags". Default returns only path + title.
maxSizeBytesNoOnly notes at most this many bytes.
minSizeBytesNoOnly notes at least this many bytes.
modifiedAfterNoOnly notes modified at or after this ISO 8601 date/time.
modifiedBeforeNoOnly notes modified before this ISO 8601 date/time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.26
    • changedInput schema / properties / tag / description
      Previous value: -"Restrict to notes with this tag (# optional)."New value: +"Restrict to notes with this tag. # optional, case-insensitive; nested child tags match (\"project\" matches project/alpha)."
  2. Changed1 schema field changedv0.3.25
    • addedInput schema / properties / where / items / properties / value / type
      Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
  3. Addedv0.3.13

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is already covered. The description adds real context beyond them: the return shape (compact rows, path + title by default, more only via select) and the negative statement that note content is not returned. It does not discuss pagination or result-count limits beyond what the schema's limit already says.

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 sentences, zero padding, front-loaded with what it queries and immediately followed by what it returns and when to prefer it. Every clause earns its place.

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?

No output schema exists, so the description must explain return values, and it does precisely: compact path+title rows by default, expanded via select, no note content. Combined with 100% schema coverage and read-only annotations, nothing needed to call this correctly is missing.

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 description coverage is 100%, with per-parameter docs including operator semantics and tag nesting, so the schema carries the load and the baseline is 3. The description only restates the filter categories and hints at select, adding no format or syntax detail beyond the schema.

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?

States a specific verb and resource (structured metadata query over notes) and enumerates the filter axes: frontmatter predicates, tag, folder, modified time, size. It also names the sibling it is not (search) and the axis that separates them, so an agent can disambiguate without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says "Use this instead of search when filtering by properties rather than text," naming both the alternative and the selecting condition. That is exactly the when-to-use/when-not guidance a routing decision needs.

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