Retrieves an SSID profile’s complete configuration, including security, network, QoS, firewall, and portal settings, by template ID with optional location context.
Full configuration of one SSID profile (security, network, QoS, firewall, portal...).
| Name | Required | Description | Default |
|---|---|---|---|
| location_id | No | Location context | |
| template_id | Yes | SSID profile templateId (from cvcue_list_ssids) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry behavioral disclosure. It communicates return breadth by naming the configuration areas included, which implies a read operation, but it does not state permissions, side effects, error behavior, or output format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no redundant or filler wording. It efficiently communicates the core scope of the tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter getter whose schema is fully documented, the description is adequate about what configuration is returned. However, it omits sibling differentiation and explicit usage guidance, and with no output schema it does not describe the response structure in detail.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the input schema already documents both parameters, including that template_id comes from cvcue_list_ssids and that location_id provides location context. The description adds no additional parameter meaning beyond that baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies a specific resource, 'one SSID profile', and specifies that it returns the full configuration across security, network, QoS, firewall, and portal areas. This is clearer than a tautology, but it does not explicitly differentiate the tool from siblings like cvcue_list_ssids or cvcue_ssid_usage.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied: retrieve the detailed configuration for a known SSID profile. The schema notes that template_id comes from cvcue_list_ssids, but the description itself does not state when to use this tool versus listing SSIDs or checking SSID usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.