Skip to main content
Glama
cmssy-io

@cmssy/mcp-server

Official
by cmssy-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_record

Add a record to a data model using its ID or slug and a data object of field values.

Instructions

Add a record (entry) to a data model. Pass the model id or slug and a data object whose keys are the model's field keys (use get_model first if unsure). Only call AFTER you described the record and the user explicitly agreed; never create without that go-ahead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoField values keyed by the model's field keys. A translatable field (localized: true on the model) takes a language map, e.g. { title: { en: 'Ball bearing', pl: 'Łożysko' } }
modelIdOrSlugNoThe target model's id or slug (from list_models)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.73.1

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the primary side effect (adding a record) and an important consent guardrail, but it does not disclose permissions, reversibility, response format, or error behavior. This is more than the bare minimum but still leaves gaps.

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?

The description is three concise sentences with no filler. Each sentence contributes: what the tool does, how to pass inputs, and when it is safe to call it.

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?

The schema already documents both parameters and the translatable-field format in detail)SkipDate. The description completes the context with the user-consent precondition and clarifies that modelIdOrSlug and data are both needed. It does not mention return values or errors, but that is a minor gap for a create operation.

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 rephrases the parameter roles and adds a helpful 'use get_model first if unsure' hint, but it does not significantly extend the schema's own parameter documentation.

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 tool's action: 'Add a record (entry) to a data model.' This specific verb-resource pairing naturally distinguishes it from sibling tools like update_record, delete_record, and list_records.

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 gives explicit call conditions: use it only after the user has agreed, never create without that go-ahead, and consult get_model first if field keys are uncertain. It does not explicitly contrast with alternatives like update_record, but the create-only scenario is clear.

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