Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Verify Encryption Password

verify_encryption_password
Read-onlyIdempotent

Verifies whether a supplied password matches a stored encryption password before a restore, without changing any data.

Instructions

Check whether password matches a stored encryption password (e.g. before a restore). Changes nothing.

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": {
      "encryption_password_id": "<encryption_password_id>",
      "password": "<password>"
    },
    "name": "verify_encryption_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
passwordYes
encryption_password_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Changes nothing' largely restates structured data. The description does add the useful semantic that this is a comparison against stored state rather than a decryption operation, but it says nothing about how a mismatch is surfaced or whether repeated attempts are limited.

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?

One sentence, front-loaded with the action, followed by a short usage cue and a reassurance clause. No wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read-only tool with full annotations this is nearly sufficient, but as a verification tool the ambiguity that matters is the result shape: whether a mismatch returns false or raises an error. With no output schema, the description should resolve that and does not.

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 0%, so the description must carry the burden, and it does clarify the roles: `password` is the candidate value being checked and the stored record is identified by `encryption_password_id`. It does not explain what the ID references or how to obtain it, leaving a gap for the required UUID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: checks whether the supplied password matches a stored encryption password, with the example context of a pre-restore check. An agent can tell this apart from change_encryption_password because the description says it changes nothing, though it does not name the sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical '(e.g. before a restore)' gives one concrete usage scenario, which is real guidance. However, there is no explicit when-not guidance and no named alternative for related tasks such as setting or changing a password.

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