Loading ToolBench
1Password MCP Server for secure note management. Maintains note names across conversations for consistency. Use descriptive note names and reference them by the same name throughout the session.
Server has 7 tools with basic descriptions and Zod-based input schemas. Naming follows verb_noun convention (list-, get-, create-, append-, update-, archive-). However, descriptions lack depth on WHEN to use each tool and lack dependency hints. Parameter descriptions are present but generic. No output schema documentation. Error handling returns custom response objects but lacks actionable recovery guidance. Missing tool annotations (readOnlyHint, destructiveHint). Schemas are present but minimal, no constraints, ranges, or format specifications beyond type declarations.
Append content to an existing secure note in a 1Password vault. The new content will be added to the end of the existing content.
Archive a secure note in a 1Password vault
Create a new secure note in a 1Password vault. IMPORTANT: Remember the note name used here for future references in this conversation.
Get a secure note from a 1Password vault. IMPORTANT: Remember the note name used here and reference it consistently throughout the conversation.
List secure notes in a 1Password vault
List version of `op`
Update the content of an existing secure note in a 1Password vault. This will replace all existing content with the new content.
No output schema documentation. Tools return custom response objects (success(), errorResponse()) but LLMs cannot see the structure of returned fields. This forces LLMs to parse unstructured text and risks context loss.
Missing tool annotations. Destructive tools (archive-secure-note) and write tools (create-, update-, append-) lack destructiveHint and readOnlyHint annotations. LLMs cannot distinguish safe from risky operations without explicit hints.
Parameter descriptions lack format/constraint details. 'noteName' accepts any string but should specify: max length, allowed characters, case sensitivity, uniqueness requirement. No enum constraints or regex patterns.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | 2026-07-28+ | v2 |
Error handling lacks recovery guidance. errorResponse() returns generic error messages without actionable next steps. E.g., 'Note not found' should suggest 'Call list-secure-notes to see available notes.'
No confirmation/dry-run for destructive operations. archive-secure-note irreversibly deletes notes. Should support a dry-run or require explicit confirmation to prevent accidental data loss.