Skip to main content
Glama
Sign In
tie-mcp-server

tie-mcp-server

by taherkaraki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

change_password

Update a user password by validating the old password and enforcing new password rules (minimum 12 characters, including uppercase, lowercase, number, special character).

Instructions

Update a user's password

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

Input Schema

NameRequiredDescriptionDefault
bodyYesValidates the PUT /users/password request

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided. Description implies a write operation but does not disclose side effects (e.g., session invalidation) or authentication requirements beyond the schema. The schema reveals both old and new password, but the description adds no behavioral context.

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?

Single sentence efficiently conveys the tool's purpose. No redundant information. Could include more context but remains concise.

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

Completeness2/5

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

Given no annotations and no output schema, the description should provide more context about the behavior, such as whether it affects active sessions, any restrictions, or result format. The current description is insufficient for a password change operation.

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 100% with detailed descriptions for both oldPassword and newPassword, including pattern. The tool description adds no additional parameter meaning beyond what the schema already provides, earning a baseline of 3.

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?

Description clearly states 'Update a user's password', specifying the verb and resource. It distinguishes from siblings like update_user, which updates general user details. However, it does not clarify if it changes own password or another user's.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives like update_user. No context about prerequisites or scenarios where this is appropriate.

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