Skip to main content
Glama
Sign In
UniFi MCP Server

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

download_innerspace_asset

Downloads an asset such as a floor plan image from InnerSpace using console, plan, and filename identifiers so you can retrieve stored plan files for local use.

Instructions

Download an asset (e.g. floor plan image) from InnerSpace.

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": {
      "console_id": "<console_id>",
      "plan_id": "<plan_id>",
      "filename": "<filename>"
    },
    "name": "download_innerspace_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesFloor plan identifier
filenameYesAsset filename on the floor plan
console_idYesCloud Connector console UUID (from ``list_hosts``)
controllerNoController to run against (see list_controllers). Defaults to the controller chosen with select_controller, then the server default.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.6.4
    • addedInput schema / properties / console_id / description
      Added value: +"Cloud Connector console UUID (from ``list_hosts``)"
    • addedInput schema / properties / filename / description
      Added value: +"Asset filename on the floor plan"
    • addedInput schema / properties / plan_id / description
      Added value: +"Floor plan identifier"
  2. Addedv0.6.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only download but does not state whether the asset must already exist, how the binary content is returned, what permissions are required, or what happens on failure. Only the bare action is described.

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?

It is a single, front-loaded sentence with no wasted words. The brevity is appropriate, though the sentence could carry slightly more context without becoming bloated.

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?

An output schema exists, so return-value details need not be repeated. However, for a download tool with no annotations, the description omits prerequisite context (e.g. that the asset is tied to a floor plan) and usage context that would help an agent invoke it confidently.

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 description coverage is 100%, so all four parameters are fully documented in the schema, including console_id sourcing from list_hosts and controller resolution order. The description adds no parameter meaning beyond what the schema already provides, so baseline 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?

The description names a specific verb ('Download') and resource ('asset, e.g. floor plan image') and scopes it to InnerSpace, so an agent can tell it retrieves a file rather than listing metadata. It does not explicitly contrast with sibling tools like list_innerspace_floor_plans, but the download action is distinct enough.

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 is given on when to use this tool versus alternatives, nor any prerequisites or exclusions. The agent must infer that this is the retrieval counterpart to the InnerSpace listing tools.

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