Skip to main content
Glama

Forgot the password

request_password_reset

Emails a code to reset the password of an account (the answer is the same whether or not the account exists). Then reset_password. [REST: POST /api/auth/password/forgot]

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

Input Schema

NameRequiredDescriptionDefault
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

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

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, non-idempotent), the description discloses a key behavioral trait: the response is identical whether or not the account exists, which signals an anti-enumeration design and tells the agent not to interpret the answer as account existence. It also makes clear an external email side effect occurs. Missing: code expiry or rate-limit behavior.

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 plus a compact REST endpoint tag; nothing is padded or repeated. The most important facts (action, anti-enumeration behavior, next step) come first.

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 two-parameter, no-output-schema tool, the description covers the purpose, the follow-up call, and the response-uniformity behavior an agent needs. It stops short of explaining code lifetime or delivery failure modes, which would round it out.

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 50%: the lang enum is fully documented in the schema, while email has no schema description. The description only implies that email is the destination address via "Emails a code ... to an account", adding little beyond the field name. Baseline 3 is appropriate given the schema carries the enum detail.

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?

"Emails a code to reset the password of an account" names a concrete action and resource, and the follow-up "Then reset_password" positions it in a two-step flow relative to the closest sibling. An agent can tell exactly what this call accomplishes without opening the 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?

The phrase "Then reset_password" gives explicit sequencing: call this first to obtain the code, then use the sibling to complete the reset. It does not spell out when-not conditions (e.g., if the user already has a valid code), but the intended context is clear.

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