Skip to main content
Glama
Sign In
umami-mcp

umami-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_my_password

Change the signed-in user's Umami password by supplying the current and new password; works only on self-hosted Umami, not Cloud API-key routes.

Instructions

Update the current user's password (self-hosted Umami only; Cloud API keys cannot call this route)

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": {
      "currentPassword": "<currentPassword>",
      "newPassword": "<newPassword>"
    },
    "name": "update_my_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
newPasswordYesNew password (minimum 8 characters)
currentPasswordYesCurrent password

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.1
    • changedInput schema / properties / newPassword / description
      Previous value: -"New password"New value: +"New password (minimum 8 characters)"
    • addedInput schema / properties / newPassword / minLength
      Added value: +8
  2. First observedv1.2.1

TDQS

A3.8/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 behavioral burden. It usefully discloses the platform/credential restriction, but does not say whether the mutation invalidates existing sessions/tokens, whether the current password is verified server-side, or what a successful response looks like. Meaningful but incomplete for a mutation tool.

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?

A single, front-loaded sentence with zero filler. The platform restriction is presented immediately after the core action, so the agent gets the key constraint without scanning.

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 two-parameter password update with full schema coverage, the description covers the critical availability constraint. Remaining gaps, such as session invalidation and auth prerequisites, are modest given the tool's simplicity.

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 100%, so both parameters (currentPassword, newPassword with minLength 8) are already documented in the schema. The description adds no parameter-level meaning beyond what the structured schema provides, so baseline 3 applies.

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 ('Update the current user's password') with a self-scoped qualifier that distinguishes it from admin-oriented siblings like update_user. It does not explicitly name an alternative tool, but the 'my/current user' framing makes the audience clear.

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?

Provides an explicit usage constraint: self-hosted Umami only, and Cloud API keys cannot call this route. That is a genuine when-not condition. It stops short of stating preconditions such as authentication requirements or alternatives for cloud users.

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

Deploy Server

Other Tools