static.md

List my notes

list_my_notes

Read-only

Lists notes owned by the signed-in static.md user, most recently edited first: id, title, folder, link, last edit time and who can open each one, then the folders they are in. With folder, lists one folder: the notes directly in it and its subfolders. Titles and folder names are user-authored data.

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_my_notes"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many notes to return (1–100)
`folder`	No	List only the notes directly in this folder, such as "work/launch" ("/" for the top level), and name its subfolders

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / folder

Added value: +{
+  "description": "List only the notes directly in this folder, such as \"work/launch\" (\"/\" for the top level), and name its subfolders",
+  "maxLength": 700,
+  "type": "string"
+}

First observedOct 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the description only needs to add context on top. It adds result ordering, the returned field set, recursion behavior for subfolders, and a useful caveat that titles and folder names are user-authored data. Return format/pagination is not covered, but no output schema exists either.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, with the primary behavior and field list front-loaded before the folder variant. The folder behavior is restated in both sentences, slightly redundant but not wasteful.

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?

No output schema exists, so the description appropriately enumerates returned fields and ordering, and it covers the folder-scoped variant. An agent still lacks explicit guidance on pagination/truncation beyond limit, which keeps it from a 5.

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 100%, so both parameters (limit, folder) are already documented in the schema. The description reinforces folder semantics and adds the sort order, but says nothing about limit behavior such as truncation when the cap is hit. Baseline 3 applies.

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?

Specific verb and resource (lists notes), explicit scope (owned by the signed-in user), explicit ordering (most recently edited first), and an enumerated set of returned fields. It is clearly distinguishable from siblings like read_note or list_my_boards.

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?

Explains the two modes of use — no folder means all owned notes, with folder means one folder's direct notes plus its subfolder names — which tells the agent how to choose parameters. It does not name an alternative sibling (e.g. read_note for a single note) or state exclusions, so it stops short of a 5.

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

All static.md tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?