Skip to main content
Glama
Sign In
Axis MCP

Axis MCP

by hemla-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_device_info

Read-onlyIdempotent

Retrieve detailed information about an Axis IP camera, including model, serial number, and firmware version.

Instructions

Get detailed device information (model, serial, firmware, etc.).

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_device_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the tool as readOnlyHint, idempotentHint, and non-destructive, so the description doesn't need to repeat safety traits. It adds value by listing typical returned fields (model, serial, firmware), giving the agent a concrete sense of output. No contradictions with 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?

A single sentence of 9 words efficiently communicates the tool's purpose. Every word contributes meaning, with no fluff or redundancy.

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 description provides essential purpose and example fields, it lacks details on return structure or format. Given no output schema, the description could be more comprehensive about what 'device information' encompasses to fully inform an agent, especially among many similar sibling tools.

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?

There are no parameters, so the schema baseline is 4. The description adds no parameter info, which is acceptable because there are none to explain. It fulfills the need without overcomplication.

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 specifies the action ('get detailed device information') and provides concrete examples of data returned (model, serial, firmware, etc.). It effectively distinguishes this tool from siblings like get_storage_info or get_network_info by focusing on general device identity details.

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?

The description does not explicitly state when to use this tool versus alternatives. It relies on implicit differentiation based on the mentioned data fields, but lacks guidance on exclusions or context-specific recommendations.

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