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

meraki-dashboard-api

by Flagler-County-BoCC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

switch-list-stp

Retrieves Spanning Tree Protocol (STP) settings for a specified network, including RSTP status and bridge priority. Read-only access to STP configuration.

Instructions

Returns STP settings. (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": {
      "networkId": "<networkId>"
    },
    "name": "switch-list-stp"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkIdYesNetwork ID
fieldsNoReturn only these top-level fields; omit for all. Available: rstpEnabled, stpBridgePriority.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description only mentions read-only. It lacks details on behavior for invalid networkId, rate limits, or call side effects. Insufficient transparency.

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?

Two sentences, zero wasted words, front-loaded with action. Ideal length for a simple read-only tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, and description doesn't describe return format or structure. For a tool returning STP settings, more context is needed. Siblings are not referenced.

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 covers 100% of parameters with descriptions. The description adds nothing beyond the schema, so baseline of 3 is appropriate.

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?

Description clearly states it returns STP settings, which is specific and distinct from sibling tools like switch-list-ports or switch-list-statuses. However, the title is null, and the description doesn't elaborate on the scope.

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 on when to use this tool vs alternatives. The '(read-only)' hint implies safe invocation but no explicit context or exclusions.

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