big-brain

by jzhao234

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Archive a note

archive_note

Move a note to the archive folder instead of deleting it, hiding archived notes from search and listings by default.

Instructions

Move a note into the archive folder (the non-destructive alternative to deletion). Archived notes are excluded from search and listings by default.

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": {
      "ref": "<ref>"
    },
    "name": "archive_note"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes	Note path, title, or alias

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 14, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the operation is non-destructive and that archived notes are excluded from search and listings by default. However, it omits reversibility (how to unarchive), permission requirements, and error behavior.

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 tightly written sentences: the first front-loads the action and its role, the second adds a key behavioral effect. No wasted words, and structure is logical.

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 simple one-parameter tool with no output schema or annotations, the description covers purpose, effect on search/listings, and non-destructive nature. It could still mention reversibility or failure conditions, but it is largely complete.

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 the 'ref' parameter is fully documented in the schema. The description adds no parameter-specific meaning beyond what the schema provides, so the 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 verb ('Move') and resource ('a note') with destination ('into the archive folder'), and clarifies its role as 'the non-destructive alternative to deletion'. This distinguishes it clearly from other note operations like replace_note_body or append_note.

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?

Implies usage context by calling it 'the non-destructive alternative to deletion', which tells the agent when to prefer this over deleting. No explicit when-not or named alternative tool, but the context is clear enough.

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