NomaCMS MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create Collection

create_collection

Create a new collection in NomaCMS, optionally including field definitions to define its complete schema in a single request.

Instructions

Create a new collection. Optionally include field definitions to create the collection with its full schema in a single request.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "slug": "<slug>"
    },
    "name": "create_collection"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Display name (max 60 chars)
`slug`	Yes	URL-friendly identifier, kebab-case (max 60 chars)
`fields`	No	Array of field definitions to create with the collection
`is_singleton`	No	If true, collection can only have one entry

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Jul 11, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description carries full burden but fails to disclose key behaviors like mutability, idempotency, error handling (e.g., duplicate slug), or required permissions. It only hints at atomic schema creation.

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 succinct sentences with no extraneous information. The first states the core action, the second adds the key optional behavior. Every word earns its place.

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

Completeness3/5

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

The description is minimal for a creation tool with 4 parameters and no output schema. It lacks detail on return values, uniqueness constraints, and error conditions. The detailed schema compensates partly but not fully.

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 coverage is 100% with detailed property descriptions. The description adds summary context ('optionally include field definitions') but doesn't enrich individual parameter understanding beyond what the schema provides.

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 action ('Create'), the resource ('a new collection'), and the optional inclusion of field definitions. This distinguishes it from siblings like 'update_collection' and 'create_field'.

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 implies use for creating a new collection but provides no explicit guidance on when to use alternative tools (e.g., creating fields separately) or prerequisites. Usage context is implied but not explicit.

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