Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_collection

Create a custom data table with system columns and optional custom fields. Add columns with name/type, then write records via an HTTP function.

Instructions

Create a new collection (custom data TABLE). It starts with the system columns (id/inserted_at/updated_at/creator_id); pass columns to add custom fields. NOTE: to WRITE records into it, use an HTTP function (webcake-data: db.model(table).create({...})) — the dashboard has no direct record-insert API. See get_http_function for the SDK guide.

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name.
columnsNoCustom columns to add, e.g. [{name:'email',type:'text'},{name:'amount',type:'integer'}].
table_nameNoTable name (snake_case, unique). Defaults to name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.31.8

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, non-destructive mutation, so the bar is lower. The description adds real behavioral detail: the collection is seeded with system columns (id/inserted_at/updated_at/creator_id) and the dashboard exposes no direct record-insert API, which is a meaningful capability limitation.

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?

Three sentences, all front-loaded with the core action first, then the system-column behavior, then the important write-path caveat. No filler; the NOTE earns its place by preventing a wrong-invocation attempt.

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 3-parameter mutation with no output schema and safety already covered by annotations, the definition covers creation semantics, default state, and the record-write alternative. Nothing essential for a correct invocation 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 coverage is 100%, so the baseline is 3. The description goes slightly beyond the schema by framing the initial system columns and explaining that `columns` adds custom fields on top of them, which helps the agent understand what is and isn't supplied at creation.

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 ('Create') plus resource ('collection'), then clarifies the resource as a 'custom data TABLE', which an agent cannot infer from the name alone. Together with sibling verbs (get_collection, update_collection_columns, delete_collection) the create action is unambiguous.

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 the agent away from attempting record insertion here, naming the alternative (an HTTP function via get_http_function) and the mechanism (db.model(table).create). It gives clear context for the write path but does not state when a collection is preferable to, say, a CMS file or product type.

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

Deploy Server

Other Tools