bardo_note_undelete
Restore a deleted note within its grace period by providing the note ID.
Instructions
Restore a note that's still within its post-delete grace period.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note_id | Yes | ||
| session_token | No |
Restore a deleted note within its grace period by providing the note ID.
Restore a note that's still within its post-delete grace period.
| Name | Required | Description | Default |
|---|---|---|---|
| note_id | Yes | ||
| session_token | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate write operation (readOnlyHint=false) but not destructive (destructiveHint=false), and not idempotent. Description adds the critical constraint of 'post-delete grace period', providing context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single, efficient sentence front-loading the key action and constraint. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Describes core behavior and constraint (grace period) for a simple tool with 2 parameters. Lacks details on error conditions or return values, but acceptable given tool simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, with two parameters (note_id and session_token) lacking descriptions. The tool description does not explain their roles or format, failing to compensate for the missing schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description uses specific verb 'Restore' and resource 'note', explaining the action and a key condition (grace period). It clearly distinguishes from siblings like bardo_note_delete and bardo_note_get.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implied usage for undeleting a recently deleted note, but no explicit guidance on when not to use or comparison with alternatives like bardo_note_get or bardo_note_delete.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/calebe/bardo'
If you have feedback or need assistance with the MCP directory API, please join our Discord server