Skip to main content
Glama

list_otto_channels

Read-only

Lists where Otto (Now Assist) is deployed, including assistant panels, Virtual Agent, voice channels, and configuration attributes that show enabled skills.

Instructions

List where Otto (Now Assist) is deployed: assistant deployments (sys_now_assist_deployment: Otto panel, Virtual Agent, voice), their channels (sys_now_assist_deployment_channel) and configuration attributes such as which skills are enabled (sys_now_assist_deployment_config_attributes).

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": "list_otto_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeNoOnly active deployments
include_attributesNoInclude config attributes (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully discloses the returned hierarchy (deployments -> channels -> config attributes such as enabled skills), which goes beyond annotations. It says nothing about volume, pagination, or cost of the open-world traversal.

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?

A single front-loaded sentence that enumerates the three record types without filler. The parenthetical ServiceNow table names (sys_now_assist_deployment, etc.) are mildly noisy but do clarify what data is actually returned.

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

Completeness4/5

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

For a read-only, two-optional-parameter list tool with no output schema and annotation-covered safety, the description gives enough to know what entity tree is returned. Only return cardinality and shape are unaddressed, which is a minor gap.

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% and both parameters (active, include_attributes) are documented in the schema with defaults, so the schema does the heavy lifting. The description adds no additional meaning for either parameter, leaving it at the baseline.

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?

Specific verb plus resource: 'List where Otto (Now Assist) is deployed', naming deployments, deployment channels, and config attributes. It is clearly distinct from ask_otto and get_otto_status by focusing on deployment inventory rather than interaction or health. It stops short of naming a sibling it must not be confused with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the described scope (deployments, channels, enabled skills), which tells an agent this is the discovery/audit entry point for Otto configuration. There is no explicit when-to-use versus when-not, and no prerequisites or alternatives are mentioned.

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