Axis MCP

by hemla-com

Overview Schema Source Related Servers Discussions Admin

TypeScript

get_snapshot

Read-onlyIdempotent

Capture a JPEG snapshot from an Axis IP camera with adjustable resolution, width, compression, and channel selection.

Instructions

Capture a JPEG snapshot from the camera.

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": "get_snapshot"
  }
}

Input Schema

Name	Required	Description
`camera`	No	Video source/channel (default 1)
`maxWidth`	No	Max width in pixels for resizing (default 1280)
`resolution`	No	Resolution (e.g. 1920x1080)
`compression`	No	JPEG compression 0-100

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jul 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds that it captures a JPEG from the camera, but does not elaborate on further behavioral details such as file storage, size limits, or side effects, which are not disclosed by 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?

The description is a single, front-loaded sentence that effectively communicates the purpose with no wasted words. It is appropriately sized for the tool's simplicity.

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?

While the tool is simple and annotations are informative, the description lacks information about the output format (e.g., binary JPEG data or URL) since there is no output schema. For a capture tool, specifying what the agent receives is helpful, but the current description is minimally adequate.

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?

All four parameters are documented in the input schema with descriptions (100% coverage). The description does not add any additional meaning beyond the schema, so a baseline score of 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 action (capture), the resource (JPEG snapshot), and the source (camera), making the tool's purpose immediately understandable. It is distinct from sibling tools like get_capture_mode, which returns a mode string, not an image.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. Siblings like get_capture_mode or get_image_settings exist but no differentiation is given.

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