Skip to main content
Glama
Sign In
meraki-dashboard-api

meraki-dashboard-api

by Flagler-County-BoCC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

devices-list-managementinterface

Get read-only management interface settings for a device, including DDNS hostnames and WAN configurations.

Instructions

Return the management interface settings for a device. (read-only)

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": {
      "serial": "<serial>"
    },
    "name": "devices-list-managementinterface"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYesSerial
fieldsNoReturn only these top-level fields; omit for all. Available: ddnsHostnames, wan1, wan2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The description explicitly marks the operation as read-only. With no annotations provided, this disclosure is helpful. It could mention that no changes are made to the device, but it is sufficient.

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 sentence, front-loaded with the action and resource, with no extraneous information.

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 read tool with two parameters and no output schema, the description is adequate. It covers the core purpose. However, it could be more specific about the return format or what fields are included beyond the optional fields list.

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%, so the schema describes both parameters. The description does not add any extra meaning beyond what the schema provides, such as what 'management interface settings' entails.

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 it returns management interface settings for a device and notes it is read-only. However, it does not differentiate from sibling tools that also deal with device settings, such as devices-list-clients or switch-list-ports.

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?

No explicit guidance on when to use this tool versus alternatives. The purpose is implied, but there are no conditions, prerequisites, or exclusions stated.

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