Skip to main content
Glama

list_sections

Lists sidebar sections in display order with their chats, optionally filtering by section name or ID to locate a specific section.

Instructions

List your sidebar sections in sidebar order, each with its chats.

name (any case) or a section id limits it to that section.

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

Input Schema

NameRequiredDescriptionDefault
nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful traits: results are ordered by sidebar position, chats are nested under each section, and name matching is case-insensitive. It says nothing about permissions, pagination, or behavior on a non-matching name, which leaves real gaps for a no-annotation tool.

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, purpose front-loaded, the filter rule second. Nothing is redundant and the odd line break does not obscure meaning.

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?

A read-only listing tool with one optional parameter and an existing output schema needs little more: purpose, ordering, nesting, and filter semantics are all covered. Only permission/pagination expectations are unaddressed.

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?

Schema coverage is 0% and the schema only names the parameter 'Name' as a nullable string, so the description does substantial work: it states the parameter accepts a name in any case or a section id, and that it limits the response to that section. It does not spell out what an omitted/null value does, though 'limits it' implies the default is unfiltered.

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 opens with a specific verb and resource ('List your sidebar sections') plus the ordering ('in sidebar order') and payload ('each with its chats'), so an agent knows exactly what comes back. It does not explicitly distinguish itself from siblings such as list_spaces, so it falls short of a 5.

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?

The second sentence explains that supplying a name or section id narrows the result, which implies the unfiltered call lists everything. There is no explicit when-to-use/when-not-to-use guidance or named alternative, so guidance is implied rather than stated.

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