Axis MCP

Overview Schema Source Related Servers Discussions Admin

setup_initial_user

Idempotent

Configure the first admin account on a new Axis camera. Connects directly without prior authentication to set username and password.

Instructions

Set up the initial admin user on a factory-fresh Axis camera. Does NOT require connect_camera — connects directly without 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": {
      "host": "<host>",
      "password": "<password>"
    },
    "name": "setup_initial_user"
  }
}

Input Schema

Name	Required	Description	Default
`host`	Yes	Camera IP address or hostname
`port`	No	HTTP port (default 80)
`password`	Yes	Password for the initial admin account
`username`	No	Username (default 'root')	root

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jul 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already provide openWorldHint, idempotentHint, destructiveHint false. The description adds that it connects directly without authentication, complementing openWorldHint. It does not contradict annotations.

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?

Two concise sentences with no wasted words. The critical detail about no authentication is front-loaded in the second sentence.

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?

Given the tool's simplicity, description covers purpose and key behavioral nuance (no auth needed). It doesn't specify return values or errors, but no output schema is defined. Could mention that this is a one-time setup, but factory-fresh implies that.

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 descriptions for all parameters. The tool description adds no additional parameter details beyond what the schema provides, so baseline 3 is appropriate.

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?

The description clearly states the tool sets up the initial admin user on a factory-fresh Axis camera. It distinguishes from siblings by explicitly noting it does not require connect_camera and connects directly without authentication.

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 description indicates when to use (on factory-fresh camera) and that it bypasses the usual connect_camera step. It implies not to use for post-setup user management, but doesn't explicitly mention alternatives like create_user.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.