Skip to main content
Glama
Sign In
Axis MCP

Axis MCP

by hemla-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

connect_camera

Idempotent

Connect to an Axis IP camera via VAPIX protocol. Required before using other camera management tools.

Instructions

Connect to an Axis IP camera via VAPIX. Must be called before other tools.

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>",
      "username": "<username>",
      "password": "<password>"
    },
    "name": "connect_camera"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesCamera IP address or hostname
portNoHTTP port (default 80)
passwordYesCamera password
usernameYesCamera username

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare idempotent and non-destructive, so no contradiction. Description adds prerequisite context but misses details like session creation or return value.

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, front-loaded with purpose, no wasted words.

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

Completeness3/5

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

Missing output schema or expected return value; for a connection tool, return behavior (e.g., success, token) is not described.

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 covers all 4 parameters with descriptions; baseline 3 as description adds no additional parameter meaning.

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?

Clearly states the verb 'connect' and resource 'Axis IP camera via VAPIX', and distinguishes by noting it must be called before other tools.

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?

Explicitly says 'Must be called before other tools', providing clear context for when to use, but does not specify when not to use or alternatives.

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