Skip to main content
Glama

get-sdwan-config-status

Retrieve the current status of an SD-WAN configuration using its ID to verify operational state.

Instructions

Get the status of a specific SD-WAN configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSD-WAN config ID

Implementation Reference

  • The handler function that executes the tool logic. It accepts an 'id' parameter, calls the UniFi API endpoint /sd-wan-configs/{id}/status, and returns the response data.
    export async function getSdwanConfigStatus(params: z.infer<typeof getSdwanConfigStatusSchema>) {
      const response = await unifiClient.get<{ data: unknown }>(`/sd-wan-configs/${params.id}/status`);
      return response.data;
    }
  • Zod schema for the tool input: requires a single 'id' field (string) describing the SD-WAN config ID.
    export const getSdwanConfigStatusSchema = z.object({
      id: z.string().describe("SD-WAN config ID"),
    });
  • src/index.ts:141-143 (registration)
    Registration of the tool with the MCP server using the name 'get-sdwan-config-status', its schema, and wrapped handler.
    tool("get-sdwan-config-status",
      "Get the status of a specific SD-WAN configuration",
      getSdwanConfigStatusSchema.shape, wrapToolHandler(getSdwanConfigStatus));
  • src/index.ts:25-29 (registration)
    Import of getSdwanConfigStatusSchema and getSdwanConfigStatus from the sdwan tools module.
    import {
      listSdwanConfigsSchema, listSdwanConfigs,
      getSdwanConfigSchema, getSdwanConfig,
      getSdwanConfigStatusSchema, getSdwanConfigStatus,
    } from "./tools/sdwan.js";
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only restates the tool name without adding details about side effects, permissions, or error handling. The verb 'Get' implies a read-only operation, but this is not explicitly stated, and there is no mention of what happens if the ID is invalid.

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 a single concise sentence. It is front-loaded and contains no superfluous information. However, it could be structured better with additional clarity on the output or usage scope.

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?

For a simple tool with one required parameter and no output schema, the description is minimal. It does not explain the return value (status details) or any prerequisites. Siblings like 'get-sdwan-config' likely have more detailed descriptions, making this one feel incomplete in context.

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% (one parameter 'id' with description 'SD-WAN config ID'). The description adds no extra meaning beyond the schema; it does not clarify the ID format, source, or constraints. Baseline 3 is appropriate as the schema already documents the parameter adequately.

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 tool's purpose: 'Get the status of a specific SD-WAN configuration'. It uses a specific verb ('Get') and resource ('status of a specific SD-WAN configuration'). This distinguishes it from siblings like 'get-sdwan-config' (which likely retrieves the config itself) and 'list-sdwan-configs' (which lists configs).

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get-sdwan-config', 'list-sdwan-configs', and 'list-sites', the agent would benefit from explicit conditions or exclusions. The description lacks any context about prerequisites or use cases.

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/us-all/unifi-mcp-server'

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