Skip to main content
Glama

List indexed channels

list_channels
Read-onlyIdempotent

Channels in the continuously-updated public index that search covers. Optional query filters by name. Free.

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_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoCase-insensitive substring of the channel name or handle

Output Schema

NameRequiredDescriptionDefault
totalYes
channelsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description does add value beyond them: 'continuously-updated' signals index freshness and 'Free' signals no cost/quota, both unavailable in annotations. However it says nothing about result size limits, ordering, or pagination behavior.

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?

Two sentences with zero filler; the resource scope is front-loaded and the optional filter and cost note follow compactly. Nothing is redundant with the title.

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 single-optional-parameter read tool with a full annotation set and an output schema (so return shape needn't be described), the description is nearly sufficient. The main small gap is that it omits how this listing relates to the search workflow and any result-size limits.

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%, so the baseline is 3. The description adds that `query` is optional and filters by name, while the schema already specifies case-insensitive substring matching on name or handle - the description is actually slightly narrower than the schema, so it adds no meaning beyond it.

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 identifies the resource precisely - 'channels in the continuously-updated public index that search covers' - which tells an agent this is a browsable listing of the searchable channel corpus. It lacks an explicit verb and never names the sibling listing/search tools, so differentiation is inferred rather than stated.

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 only implied: the phrase 'that search covers' suggests this is the place to discover what search indexes, and 'Optional query' shows filtering is not required. There is no explicit when-to-use statement, no guidance versus search/discover, and no stated prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources