Skip to main content
Glama

Set a new password

reset_password

Sets a new password with the emailed code (every session of the account ends). Then sign_in with it. [REST: POST /api/auth/password/reset]

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": {
      "email": "<email>",
      "code": "<code>",
      "password": "<password>"
    },
    "name": "reset_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
langNoThe account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en.
emailYes
passwordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"The account's language (messages, the texts of its searches). Default en."New value: +"The account's language: ru, en, es (Spanish), de (German), fr (French), pt (Brazilian Portuguese) or ja (Japanese); the messages, the emails and the texts of its searches. Default en."
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "ru",
      -  "en"
      -]New value: +[
      +  "ru",
      +  "en",
      +  "es",
      +  "de",
      +  "fr",
      +  "pt",
      +  "ja"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the write profile is covered. The description adds one genuinely useful behavioral fact beyond them — 'every session of the account ends' — a side effect an agent must warn about. However, it says nothing about code expiry, error behavior, or whether the change is reversible.

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?

Two short sentences, front-loaded with the action, followed by the forced next step and a compact REST annotation. Every element carries information; nothing is padding.

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 4-parameter mutation with no output schema, the definition covers the action, the credential source, the side effect on sessions, and the follow-up call. Remaining gaps — error cases, code lifetime, and what the response contains — are secondary for a simple reset endpoint.

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 coverage is 25%: only `lang` carries a schema description, so `email`, `code` and `password` depend on the description for meaning. The description clarifies `code` as the emailed code, which is real added meaning for a bare 4-20 string, but says nothing about `password` constraints or which email to supply.

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 ('Sets a new password') plus the credential it consumes ('the emailed code'), which tells an agent this is the completion step of a reset flow rather than the request step. It stops short of naming request_password_reset explicitly, so the pairing with that sibling is only implied.

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?

Gives clear procedural guidance ('Then sign_in with it'), telling the agent what to do immediately after success, and the phrase 'with the emailed code' signals the prerequisite step. It does not explicitly exclude misuse (e.g. calling without having requested a code) or state what happens when the code is expired or wrong.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources