open-mcp-apps

Overview Schema Source Related Servers Discussions Admin

List collections

list_data_collections

Read-onlyIdempotent

Lists every data collection with name, item count, and last activity, helping you find where data lives or which collection to bind an app to.

Instructions

List every data collection that exists (name, item count, last activity). Use when unsure where data lives, what boards the user has, or which collection to bind an app to. Renders no UI.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`note`	No
`collections`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.10.1Oct 18, 2026

addedOutput schema / properties / collections / items / properties / shared

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "from": {
+      "type": "string"
+    },
+    "role": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "from",
+    "role"
+  ],
+  "type": "object"
+}

Addedv0.7.2Oct 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds a genuinely new trait: 'Renders no UI.' That is useful context about side effects on the interface that annotations do not convey. It stops short of describing sizing or volume of returned collections.

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 tight sentences: what it returns first, then when to reach for it. Every clause carries information and nothing is 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?

An output schema exists, so return-value detail is already covered and the description need not (and mostly does not) duplicate it. For a zero-parameter read tool with full annotation coverage, the definition is essentially complete; only the relationship to sibling listing tools like data_list is left unstated.

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, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly implies an unfiltered full listing rather than a parameterized query.

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 gives a specific verb and resource ('List every data collection') and even previews the returned fields (name, item count, last activity). It is clear on its own, but it never names or contrasts with the close sibling data_list, so an agent must infer the boundary between 'collections' and collection items.

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?

Explicit when-to-use triggers are given: 'unsure where data lives, what boards the user has, or which collection to bind an app to.' That covers discovery and binding scenarios well, though no when-not or named alternative (e.g., data_list) is offered.

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