Axis MCP

by hemla-com

Overview Schema Source Related Servers Discussions Admin

TypeScript

set_network_config

Idempotent

Update device network settings including hostname, IPv4 address, subnet mask, and gateway.

Instructions

Update network settings (hostname, IP, subnet, gateway).

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

Input Schema

Name	Required	Description
`hostname`	No	Device hostname
`ipv4Address`	No	IPv4 address
`ipv4Gateway`	No	IPv4 default gateway
`ipv4SubnetMask`	No	IPv4 subnet mask

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Jul 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already provide safety profile (idempotent, non-destructive). The description adds 'update' which is consistent but does not elaborate on behaviors beyond what annotations and schema convey.

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, efficient sentence that conveys the tool's purpose without extraneous words.

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 update tool with comprehensive annotations and schema, the description is sufficient. It could mention idempotency or lack of side effects, but this is partially covered by annotations.

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 each parameter having a description. The description lists the parameter categories but adds no additional semantic detail beyond the schema.

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 'Update network settings' with specific fields (hostname, IP, subnet, gateway), making the purpose explicit and distinguishing it from read-only siblings like get_network_config.

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?

No guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description lacks context for selection among network-related sibling tools.

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