Gravity

List notes

list_notes

Read-onlyIdempotent

Browse the list the way the Gravity app shows it: newest or most recently rescued first. Filter by tag, by when notes were created, by state (the list, Archive or Deleted Notes), and optionally by words. Use it for questions like "what did I note last week" or "my idea: notes from September". To find a note by its words alone, search is quicker; list_notes is for filters, dates and more text per note. Each note shows its first 500 characters; call fetch for the rest. Returns 20 notes per page (up to 50 with limit); pass next_cursor as cursor for the next page, until it is null.

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

Name	Required	Description
`tag`	No	Only notes with this tag, e.g. todo or idea.
`limit`	No	Notes per page, 1–50. Default 20.
`order`	No	list: as the app shows it (default). created: newest first. relevance: needs a query.
`query`	No	Words to match, as in search. With a query, results are ordered by relevance.
`state`	No	active: the list. archived: Archive. deleted: Deleted Notes. Default: the list, plus Archive when there's a query.
`cursor`	No	next_cursor from the previous page.
`created_after`	No	Only notes created on or after this date (ISO 8601).
`created_before`	No	Only notes created before this date (ISO 8601).

Output Schema

Name	Required	Description	Default
`notes`	Yes
`next_cursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), yet the description still adds substantive behavior: default page size of 20, a 50 max, cursor/next_cursor pagination loop, and the 500-character truncation per note with a redirect to fetch. That is real operational context an agent cannot get from the annotations alone.

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?

Front-loaded with the ordering and filter set, then alternatives, then pagination — a sensible order with little waste. A few clauses ("the way the Gravity app shows it") are flavor rather than information, but overall it is dense and readable.

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?

An 8-parameter, zero-required, read-only listing tool with an output schema: the description covers the filter dimensions, ordering, default state behavior, page size, cursor loop and truncation. Nothing an agent needs to invoke or paginate it 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% and every parameter carries its own docstring, including the enum meanings and the state default behavior with a query, so the description adds little parameter-level syntax beyond what is structured. Its filter summary (tag, created dates, state, words) mirrors the schema rather than extending it; 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?

States a specific action (browse/list notes) plus the ordering, filters and page size, and explicitly contrasts itself with search ("To find a note by its words alone, search is quicker"). An agent can distinguish this from search and fetch without reading the 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?

Gives concrete when-to-use triggers ("what did I note last week", "notes from September"), an explicit alternative (search) with the condition selecting it, and a pointer to fetch for full note bodies. When-to-use and when-to-use-something-else are both covered.

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

All Gravity 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?