Gravity

Add to a note

append_to_note

Add a paragraph to the end of an existing note, e.g. another item on a shopping list. The rest of the note stays as it is, and so does its place in the list. If the note should also go back to the top, call rescue_note after. For a separate thought, use add_note; to change text already there, edit_note. A note in Deleted Notes returns an error.

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": {
      "note_id": "<note_id>",
      "text": "<text>"
    },
    "name": "append_to_note"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	The paragraph to add.
`note_id`	Yes	The note's ID (a UUID) from search, list_notes or fetch.

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

Behavior5/5

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

Annotations cover the safety profile (not read-only, not destructive), and the description adds behavior they do not carry: the remainder of the note and its position in the list are preserved, a post-call to rescue_note is needed for reordering, and deleted notes cause an error. That preservation guarantee and the error case are the details an agent would otherwise get wrong.

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?

Four tight sentences: what it does first, then preservation guarantees, then the rescue_note follow-up, then sibling routing and the error case. Every sentence carries distinct information and nothing is repeated from 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 explained, and the two required parameters are fully described in the schema. What remains — side effects, ordering, follow-up calls, and the deleted-note failure mode — is all covered, leaving nothing an agent needs to call this correctly.

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%, so both parameters are fully documented in the schema and this is the baseline case. The description adds only mild meaning — that the text is a paragraph appended at the end and that the note must already exist — without format or length constraints beyond the schema's minLength.

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?

The description states a specific verb and resource — 'Add a paragraph to the end of an existing note' — plus a concrete example ('another item on a shopping list'). It explicitly distinguishes itself from add_note (separate thought) and edit_note (changing existing text), so an agent can separate it from its closest siblings without reading schemas.

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?

It gives explicit routing: use add_note for a separate thought, edit_note to change existing text, and call rescue_note afterwards if the note should return to the top of the list. It also states an exclusion condition (notes in Deleted Notes error out). This is when-to-use, when-not-to-use, and follow-up chaining in one place.

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?