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.

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.
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. 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"
+]
  2. 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"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description reveals important non-obvious behavior: the response is a JSON array followed by a summary line, shared folders are appended in full on the first page, and totals are reported separately. These details materially change how an agent should parse and interpret results.

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 front-loaded with the core purpose and keeps all important behavioral details in four sentences. The optional-parameter sentence is slightly redundant with the schema, but it remains compact and useful as a summary rather than becoming bloated.

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 list tool with four optional parameters, no output schema, and annotations already covering safety, the description covers everything an agent needs: item shape, return format, paging totals, shared-container handling, team scope, and filter options. No critical invocation detail is missing.

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%, so the baseline is 3. The description adds a small amount of value by noting the default scope ('roots') and team semantics, but it largely repeats the schema and even omits the 'trashed' enum value that the schema documents. The schema remains the primary source for parameter meaning.

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 clearly identifies the operation ('List containers') and the resource ('folders for organizing notes'), and adds what each item contains (notes_count, children_count). It does not explicitly contrast with sibling tools like containers-get or notes-list, but the resource specificity is strong enough for an agent to select it correctly.

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

Usage Guidelines4/5

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

The description provides clear context on when to use team_id versus personal containers, scope options, and how shared containers behave when listing root-level personal containers. It does not explicitly state when not to use this tool or name alternatives, so it falls short of a full 5, but the usage context is concrete and actionable.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources