Skip to main content
Glama

osirAgentResetPassword

osirAgentResetPassword: Set a new dashboard password for the user's AI agent (e.g. Hermes) - 'I lost the password'. The old one stops working. The new password is in this result only: show it to the user once, in that reply. This is the ONLY way to change the agent's login. Requires authentication.

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

Input Schema

NameRequiredDescriptionDefault
agentIdYesAgent id from osirAgentList or osirAgentDeploy.
sessionKeyNoSession key (osk_...) returned by checkDeviceLoginStatus. Pass it on every call when logged in via the in-chat device flow; omit when connected via OAuth.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the old password stops working, that the new secret is returned only in this response, that it must be surfaced to the user exactly once, and that authentication is required. These are the operative behavioral facts for a credential-rotation tool and are not derivable from readOnlyHint/destructiveHint/idempotentHint. Minor tension exists between 'the old one stops working' and destructiveHint=false, but that hint refers to data destruction, not credential invalidation, so it is not a contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the action and followed by consequences, output handling, and prerequisites in priority order. The only waste is the leading restatement of the tool name, which the caller already has.

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

Completeness5/5

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

For a two-parameter mutation with no output schema, the description covers everything an agent needs: what changes, that the old credential is invalidated, that the returned secret is one-time and must be shown to the user, and that auth is required. Nothing material is missing.

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% and both parameters already carry their own documentation, including provenance for agentId and the OAuth-vs-device-flow rule for sessionKey. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource: 'Set a new dashboard password for the user's AI agent', with a concrete example (Hermes) and a user-intent trigger ('I lost the password'). It also distinguishes itself from the credential-adjacent sibling setMailboxPassword by naming the resource as the agent's dashboard login and asserting it is 'the ONLY way to change the agent's login'.

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 a clear triggering situation (user reports a lost password) and an exclusivity claim that implicitly rules out other paths to the same outcome. It stops short of naming an explicit alternative or a when-not condition, so it is clear context rather than full routing guidance.

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.