Skip to main content
Glama
AIops-tools

fabric-aiops

bind_network_to_template

Bind a Meraki network to a configuration template, preserving prior binding for safe rollback. Includes dry-run preview and refusal when the network has local VLANs that would be overwritten.

Instructions

[WRITE][risk=high] Bind a network to a config template, capturing prior binding.

REFUSES when the network is unbound and carries local VLANs: the bind
overwrites them with the template's, unbinding does not put them back, and
this tool has no VLAN-create operation — so the undo would report success
having restored nothing.

Undo, precisely: rebind to the prior template when there was one (a faithful
restore — the configuration was template-derived either way); unbind when
the network was unbound with a VERIFIED empty VLAN set (restores the binding
state only, NOT firewall rules / group policies / static routes); and NO
undo at all when the prior VLAN set could not be read.

Pass dry_run=True to preview. The preview runs the same refusal check
(reads only), so it never previews green a bind the real call would refuse.

Args:
    network_id: Meraki network id to bind.
    template_id: Config template id to bind to.
    auto_bind: Auto-bind switch/AP profiles (Meraki autoBind flag).
    dry_run: If True, preview without binding.
    target: Target name from config; omit for the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
dry_runNo
auto_bindNo
network_idYes
template_idYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it is a write operation with high risk, it may refuse under specific conditions, and it details the precise undo behavior (faithful restore, unbind only if verified empty VLAN set, no undo if prior VLAN set unreadable). Dry_run behavior is also explained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear header, sections for refusal, undo, and dry_run, then parameter descriptions. It is slightly lengthy but every sentence adds value. It is front-loaded with the core action.

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

Completeness5/5

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

Given the complexity of binding a network to a template, the absence of annotations, and no output schema, the description covers all necessary aspects: action, refusal conditions, undo behavior, dry_run, and parameter meanings. It is very complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description specifies all parameters: network_id and template_id as required, auto_bind and dry_run with their meanings (Meraki autoBind flag, preview), and target as optional. This adds significant meaning 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 the action: 'Bind a network to a config template', and specifies the high-risk nature. It also mentions capturing prior binding for undo, making the purpose very specific and distinct from sibling tools like 'unbind_network_from_template'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides extensive guidance on when the tool will refuse (unbound network with local VLANs) and explains undo behavior in detail. It also describes the dry_run option for preview. While it doesn't explicitly compare with alternatives, the context is sufficient for an agent to decide when to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIops-tools/Fabric-AIops'

If you have feedback or need assistance with the MCP directory API, please join our Discord server