Skip to main content
Glama
Sign In
axis-cam-mcp

axis-cam-mcp

by jilavsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_cameras

Retrieve configured Axis cameras with name, description, address, and credential environment variable names. Use to enumerate available cameras without exposing credentials.

Instructions

List the configured cameras: name, description and address.

Never returns credentials - only the names of the environment variables they are read from.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cameras"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses a valuable behavioral detail—'Never returns credentials—only the names of the environment variables they are read from'—which goes beyond the schema. The verb also implies a read-only operation, though it does not elaborate on other side effects or permissions.

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?

The description is two sentences with zero filler. The primary purpose and the key security caveat are front-loaded, making it easy for an agent to parse quickly.

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?

For a simple parameterless list operation with an output schema present, the description covers all essential call-time information: what is returned, and the credential-safety behavior. It does not address error conditions or cross-tool routing, but these are not critical for correct invocation.

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

Parameters4/5

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

The tool takes zero parameters, so the parameter-semantics burden is minimal. The baseline of 4 applies because there are no parameters to document, and the description sensibly focuses on result content rather than parameter details.

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 a specific action and resource: 'List the configured cameras' with the returned fields (name, description, address). It does not explicitly compare against sibling tools like camera_info or grab_frame, but the verb and resource are unambiguous.

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

Usage Guidelines3/5

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

Usage context is implied by the verb 'List' and the subject 'configured cameras', but there is no explicit guidance on when to prefer this over sibling tools such as camera_info or camera_capabilities, nor any exclusion criteria.

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