Gravity

Add a note

add_note

Save a new note at the top of the user's Gravity list. Use it for "save this to Gravity", "note that…" or "add a todo". Keep it the user's words; Markdown works (- [ ] for checklists). To add to a note that already exists, use append_to_note; to change one, edit_note. Returns the saved note with its id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "add_note"
  }
}

Input Schema

Name	Required	Description
`tag`	No	Adds a tag prefix, e.g. "todo" saves "todo: <text>". Leave out for no tag.
`text`	Yes	The note. Its first line is its title.
`request_id`	No	A UUID you make for this note. If you send the same request_id again, for example after a timeout, Gravity returns the note it already saved instead of adding a copy.

Output Schema

Name	Required	Description	Default
`note`	Yes
`outcome`	Yes	unchanged: the note was already like that, so nothing was written.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing where the note lands (top of the list), that content is preserved in the user's own words, that Markdown/checklists are supported, and that the saved note with its id is returned. It does not mention auth scope or any failure modes, but with destructiveHint=false and openWorldHint=false already declaring a safe, contained create, the added context is solid if not exhaustive.

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?

Front-loads the core action and placement, then the trigger phrases, then the sibling routing, then the return value — a clean priority order. Every clause carries distinct information, with no restatement of the title or annotations.

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 output schema exists, so return values need not be detailed, yet the description still notes the saved note and id come back. For a single-required-parameter create tool with full schema coverage and safety annotations, nothing an agent needs to call it correctly is absent.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by adding meaning to the text payload itself — keep the user's wording and Markdown works, including "- [ ]" for checklists — which the schema's terse "The note. Its first line is its title." does not convey. The tag and request_id parameters are left entirely to the schema, which documents them adequately.

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 ("Save a new note") plus the placement ("at the top of the user's Gravity list"), which an agent cannot infer from the schema. It also explicitly contrasts itself with append_to_note and edit_note, so the tool is distinguishable from its closest siblings without opening any 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 invocation triggers ("save this to Gravity", "note that…", "add a todo") as well as explicit routing: use append_to_note to add to an existing note and edit_note to change one. Both the when and the when-not are stated, leaving nothing to inference.

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?