Skip to main content
Glama
Sign In
Axis MCP

Axis MCP

by hemla-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

update_user

Idempotent

Update an existing user's password or role on an Axis camera. Modify user permissions or authentication.

Instructions

Update an existing user's password or role.

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": {
      "user": "<user>"
    },
    "name": "update_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
ptzNoGrant/revoke PTZ control
roleNoNew role
userYesUsername to update
passwordNoNew password

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already indicate non-destructive and idempotent behavior. The description adds nothing beyond 'update', and fails to mention the 'ptz' parameter or disclose side effects like password validation.

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, front-loaded with the key action. However, it omits the 'ptz' parameter, reducing efficiency.

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?

With four parameters, no output schema, and annotations present, the description is too brief. It does not explain the boolean 'ptz' or the impact of updating multiple fields, leaving gaps.

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%, so parameters are documented. The description repeats 'password or role' but adds no new meaning; 'ptz' is ignored, reducing its value.

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?

The description clearly states the tool updates an existing user's password or role, distinguishing it from create_user and remove_user. However, it omits the 'ptz' parameter from the schema, making it incomplete.

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 versus siblings (e.g., create_user for new users, remove_user for deletion). No prerequisites or exclusions mentioned.

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