Skip to main content
Glama

hjarni

by com.hjarni
OverviewDiscussionsAdmin

containers-list

Read-onlyIdempotent

List containers (folders) for organizing notes. Each container includes notes_count and children_count. Returns a JSON array, followed by a line stating the total for the folders it pages through and whether more pages remain; folders shared WITH you are appended in full on the first page and counted separately in that line. Optional: team_id (integer) for team containers, scope ('roots' default|'all'|'archived'), page, per_page. Shared containers are automatically included when listing root-level personal containers. The space's root (the personal root, or a team's root folder) is not a folder: it holds the notes filed outside any folder and cannot be renamed, moved, archived or deleted. It is left out of the default 'roots' scope and appears under 'all' flagged root: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
scopeNoFilter scope (default: roots). 'archived' lists archived folders (personal, or the team's with team_id). 'trashed' lists deleted folders still restorable via containers-restore, one entry per delete with restores_with counts. On those entries notes_count and children_count are the folder's OWN notes and sub-folders in that delete, while restores_with totals the whole subtree that comes back with it.
team_idNoList containers in this team instead of personal containers. Omit it (or send null) for personal containers.
per_pageNoResults per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / scope / description
      Previous value: -"Filter scope (default: roots). 'archived' lists archived folders (personal, or the team's with team_id). 'trashed' lists deleted folders still restorable via containers-restore, one entry per delete with restores_with counts."New value: +"Filter scope (default: roots). 'archived' lists archived folders (personal, or the team's with team_id). 'trashed' lists deleted folders still restorable via containers-restore, one entry per delete with restores_with counts. On those entries notes_count and children_count are the folder's OWN notes and sub-folders in that delete, while restores_with totals the whole subtree that comes back with it."
  2. Changed2 schema fields changed
    • changedInput schema / properties / team_id / description
      Previous value: -"List containers in this team instead of personal containers"New value: +"List containers in this team instead of personal containers. Omit it (or send null) for personal containers."
    • changedInput schema / properties / team_id / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / scope / description
      Previous value: -"Filter scope (default: roots). 'archived' only for personal containers."New value: +"Filter scope (default: roots). 'archived' lists archived folders (personal, or the team's with team_id). 'trashed' lists deleted folders still restorable via containers-restore, one entry per delete with restores_with counts."
    • changedInput schema / properties / scope / enum
      Previous value: -[
-  "roots",
-  "all",
-  "archived"
-]New value: +[
+  "roots",
+  "all",
+  "archived",
+  "trashed"
+]
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only and non-destructive, but the description adds substantial behavioral context: pagination details, shared container inclusion, root folder exclusion, and scope-specific behavior (including 'trashed' with restores_with counts). This goes far beyond the annotations.

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?

The description is long but information-dense, with each sentence covering a distinct aspect (return format, pagination, scopes, root behavior). It is well-structured and front-loads the core purpose before diving into details, though it could be slightly tightened.

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

Completeness5/5

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

For a listing tool with no output schema, the description is remarkably complete: it specifies the return format (JSON array plus pagination line), explains all scope nuances, covers shared containers and root exclusion, and addresses edge cases like 'trashed'. Nothing essential is missing.

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 covers all parameters (100%), so baseline is 3. The description adds extra meaning: root container behavior, shared containers auto-inclusion, and explanation of the 'trashed' scope with restores_with. This enhances understanding beyond the schema's simple field descriptions.

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?

The description clearly states the tool lists containers (folders) for notes and specifies that each container includes notes_count and children_count. It is distinct from sibling tools like containers-get (single container) and containers-create, making the purpose unambiguous.

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 description explains the tool's behavior and scopes but does not explicitly say when to use this tool versus alternatives like containers-get. It lacks direct 'use this when' or 'not for' guidance, though the purpose is clear enough for an agent to infer basic usage.

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

All hjarni toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources