Skip to main content
Glama

Enter a new database password

update_password
Destructive

Prompts the user to enter a new password for a database source when it changed or is missing, keeping the old password active until the new one works.

Instructions

Have the user enter a new password for a database source (when it changed, or test_source says it's missing or wrong). Never takes the password: the user types it where you can't see it. The old password stays until the new one works.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=false, but the description adds context the annotations cannot: it never accepts the password as input, the user types it out-of-band, and the old password remains valid until the new one works. This tells the agent it must prompt interactively instead of passing a secret. It does not describe failure/cancel behavior or how success is confirmed.

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?

Three short sentences, each carrying distinct information, with the core action and condition front-loaded and the security constraint adjacent. Nothing is wasted or repeated from the title.

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 one-parameter, interactive, no-output-schema tool, the definition covers the action, the trigger, and the input constraint well. The only gap is what the agent should do after the user enters the password (e.g., re-run test_source) and how cancellation surfaces.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single property 'name' is undocumented, but the description implicitly identifies it as the database source identifier. It also implicitly rules out a password parameter, which prevents an agent from trying to supply one. That is meaningful added meaning for a one-parameter tool.

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 uses a concrete verb+resource: 'Have the user enter a new password for a database source.' It also names the sibling that triggers this flow ('test_source'), so an agent can distinguish this tool from account_sign_in or add_source without opening a schema.

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?

It gives explicit triggering conditions: use when the password changed, or when test_source reports it missing or wrong. That routes the agent from a diagnostic tool to this one. It stops short of stating when-not to use it or what to do if the user declines, so it is a strong 4 rather than a 5.

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