Skip to main content
Glama
the-real-talk

the-real-talk

list_channels

Lists channels held by connected Figma plugins, showing file names and last activity times. Use it to find your file's channel before joining it.

Instructions

List the channels currently held by a connected Figma plugin, with the Figma file name and the time of the plugin's last sign of life. Read-only. Use it to find the channel of your file, then join_channel.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and correctly declares 'Read-only' itself, plus discloses the returned fields. It stops short of clarifying what 'connected' or 'last sign of life' means for stale/offline plugins, and says nothing about ordering or empty results.

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 short sentences with zero waste: the capability and its payload come first, the usage routing second. Nothing is repeated or padded.

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 simple, parameterless read tool with no output schema, the description gives enough to call it correctly and interpret the result fields. Only minor gaps remain around result ordering and the semantics of 'connected' / 'last sign of life'.

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 tool takes zero parameters and the description does not invent any; there is nothing further an agent needs to supply. Baseline 4 applies for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (list the channels held by a connected Figma plugin) and even names the payload contents (file name, last sign of life). This clearly separates it from join_channel and the many mutation tools in the sibling set.

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

Usage Guidelines5/5

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

Provides an explicit workflow: 'Use it to find the channel of your file, then join_channel.' That names the follow-up alternative and the condition that selects it, so an agent knows exactly when this tool is the right first step.

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