Skip to main content
Glama
Sign In
@kognar/nginx-manager-mcp-server

@kognar/nginx-manager-mcp-server

by kognar-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update user

npm_update_user

Update a Nginx Proxy Manager user's details by ID, including name, email, roles, and disabled status.

Instructions

Update a user.

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": {
      "id": "<id>"
    },
    "name": "npm_update_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
emailNo
rolesNo
nicknameNo
is_disabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

D1.1/5.0
Behavior1/5

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

With no annotations, the description must carry full behavioral transparency, but it provides no information about mutation behavior, idempotency, partial vs full update, or any other traits beyond the verb 'Update'.

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

Conciseness2/5

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

While extremely concise (2 words), the description is under-specified to the point of uselessness. Conciseness is not valuable when it omits critical information.

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

Completeness1/5

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

Given 6 parameters, no annotations, and no output schema, the description is woefully incomplete. It fails to explain required fields, update semantics, or expected outcomes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage on its 6 parameters. The description adds no semantic meaning to fields like 'is_disabled' or 'roles', leaving the agent to infer from names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update a user' is a tautology, merely restating the tool name and title without specifying what aspects of a user can be updated or how it differs from similar tools.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus siblings like npm_create_user or npm_set_user_password. The description lacks any context for selection.

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