Skip to main content
Glama
Sign In
grepnotes

grepnotes

by LuthfiMirza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_notes

Lists every indexed note with its headings, helping you orient before searching local notes.

Instructions

List every indexed document with its headings. Useful for orienting before searching.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. 'List every indexed document' does disclose scope (unfiltered, complete inventory) and the zero-param schema means no filtering or pagination is possible, which the word 'every' conveys. It doesn't state read-only safety, expected output size, or whether results are truncated for large corpora.

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 short sentences, zero waste, with the scope stated first and the usage hint second. Nothing redundant.

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?

For a zero-param list tool with no output schema and simple complexity, this covers purpose, scope, and use case adequately. A note on output volume or ordering would make it fully complete.

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 takes zero parameters, so the baseline is 4. The description correctly implies no filtering is available by saying it lists 'every' document, consistent with the empty schema.

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?

The description gives a specific verb ('List') and resource ('every indexed document with its headings'), so the agent knows exactly what comes back. It doesn't explicitly name search_notes or read_note, but 'orienting before searching' implicitly separates it from the search sibling.

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?

'Useful for orienting before searching' establishes a clear usage context and implicitly routes searching to search_notes. There is no explicit exclusion or named alternative, so it stops short of a full when/when-not statement.

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