Skip to main content
Glama

Create a list

create_list

Create a list. To set up several lists with indexes and rules, a schema sync document (plan_schema_sync, apply_schema_sync) is usually better. Rules that don't compile, or whose tests fail, refuse the whole create, with diagnostics in details. 1 request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe list's name
tagsNoTags (at most 20). Replaces the existing tags
rulesNoWrite rules, in the JSONPad rules language, checked on every item write made with an API token; null removes them. Check them first with the JSONPad docs server's check_write_rules
pinnedNo
schemaNoA JSON schema every item's data must match, or null for none
pathNameNoA unique name to use in URLs instead of the id (letters, digits, - and _)
readonlyNoRefuse writes to the list, its items and indexes
realtimeNoSend realtime events for the list's changes
activatedNoDeactivated lists are invisible to tokens
indexableNoAllow listing and searching its items with a token. A new list is not indexable unless this is set
protectedNoRefuse to delete the list while it has items
rulesTestsNoTests the rules must pass before they're saved, or null for none
descriptionNoWhat the list is for

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
listYes
ruleWarningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnly=false, non-idempotent, non-destructive), so the bar is lower. The description adds value the annotations cannot: non-compiling or failing rules abort the entire create (atomic failure), diagnostics arrive in details, and '1 request' signals cost. It doesn't explain what happens to a partially-created list beyond the refusal, but the failure semantics are notably well disclosed.

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?

Four terse sentences: purpose first, alternative routing second, failure semantics third, cost last. Zero filler and nothing redundant with the schema.

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?

With annotations covering the safety profile, an output schema covering return values, and 92% schema coverage for parameters, the description supplies exactly the missing glue: alternative routing and atomic failure behavior. Complete for correct invocation.

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 92%, so the schema already documents all 13 parameters and the baseline is 3. The description adds cross-cutting meaning for the rules/rulesTests pair (compilation and test failures block the create) but no per-parameter syntax or format detail beyond that.

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 ('Create a list') and immediately distinguishes itself from the bulk path by pointing at plan_schema_sync/apply_schema_sync. An agent can identify the tool's role without opening the schema.

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?

Explicitly routes bulk scenario (several lists with indexes and rules) to the schema-sync siblings, which is real when-to-use guidance. It doesn't state a when-not for the single-list case, but the alternative is named clearly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources