omada-mcp

by falehsub

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Diff site configuration snapshots

diff_config_snapshots

Read-onlyIdempotent

Deterministically compare two get_config_snapshot payloads…

Instructions

Deterministically compare two get_config_snapshot payloads…

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": {
      "baseline": "<baseline>"
    },
    "name": "diff_config_snapshots"
  }
}

Input Schema

Name	Required	Description	Default
`site`	No
`current`	No
`objects`	No
`baseline`	Yes

Output Schema

Name	Required	Description	Default
`summary`	Yes
`sections`	Yes
`crossSite`	Yes
`hasChanges`	Yes
`comparedSource`	Yes
`sectionsCompared`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.0Nov 15, 2026

TDQS

C2.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only the word "deterministically," which hints at stable, reproducible diff output, but says nothing about ordering, size limits, or how differences are represented.

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

Conciseness2/5

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

The single sentence is front-loaded but ends mid-thought with an ellipsis, so it is under-specified rather than concise. Brevity here costs information rather than eliminating waste.

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?

An output schema exists, so return values need not be explained, but for a four-parameter tool with nested payloads and a filter list, the description leaves the site scoping and objects filtering entirely undocumented. It is not complete enough for an agent to call this confidently without reading the schema closely.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, including two nested object payloads, so the description carries the full burden. It clarifies that baseline/current are get_config_snapshot payloads, which is real value, but says nothing about the site parameter or the objects filter enum list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("compare two get_config_snapshot payloads") and ties the inputs to a sibling tool, which is genuinely useful. However, it is truncated with an ellipsis, so the statement of what the tool actually produces or how the comparison is scoped is never completed.

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?

There is no guidance on when to use this versus get_config_snapshot or any other sibling, and no prerequisites (e.g., that both payloads must come from the same site). The agent must infer the workflow entirely.

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