Skip to main content
Glama
Sign In
UnifiyMe

UnifiyMe

by lobsterclause
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_network_topology

View a simplified network topology showing uplink connections between UniFi devices, enabling quick identification of network structure and device hierarchy.

Instructions

Get network topology (simplified view of uplinks)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_network_topology"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It mentions that the output is a 'simplified view of uplinks,' which gives a hint about scope, but it does not explicitly state that the operation is read-only, describe the return format, or note any rate limits or prerequisites.

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, tightly packed phrase with no filler or redundant words. It front-loads the action and object and is appropriately sized for such a simple, parameterless tool.

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

Completeness3/5

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

For a parameterless tool with no output schema and no annotations, the description is minimally viable: it tells the agent that the result is a simplified uplinks view. However, it lacks any details about the response shape or how this differs from related topology/status/config tools, so an agent might still be unsure when to invoke it.

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

Parameters4/5

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

The input schema is empty with zero parameters, so there is nothing to explain beyond the schema itself. With zero parameters, the baseline of 4 is appropriate, and the description adds no parameter semantics because none are needed.

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 uses the specific verb 'Get' with the resource 'network topology' and the clarifier 'simplified view of uplinks,' which clearly states what the tool returns. It is distinct enough from siblings like get_network_status or list_devices, but it does not explicitly name or differentiate itself from those alternatives.

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 the many sibling tools. There are no scenarios, prerequisites, or exclusions mentioned, leaving the agent to infer usage solely from the name and one-line description.

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