Skip to main content
Glama
alexxcpr

ONE-MCP

by alexxcpr

create_entity_record

Create a new entity record by specifying entity name and property values, with optional nested child records. Requires Create permission; creates real data, so double-check values before submitting.

Instructions

Create a new entity record. ⚠️ Requires Create permission on the entity.

Provide the entity name and a properties object with field values. Optionally include child entity records (nested creation).

Example: create a new catalog entry:

  • entityName: "ui_catalog"

  • properties: { "name": "my_catalog", "fetch": "FETCH ..." }

IMPORTANT: This creates real data. Double-check your values before submitting. There is NO delete functionality via this MCP — mistakes must be corrected manually.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
childrenNoOptional. Map of child entity names to arrays of child records, each with 'entity_name' and 'properties'. Used when the entity has related child entities that should be created in the same transaction. Example: { "child_entity": [{ "entity_name": "child", "properties": {...} }] }
entityNameYesThe entity name to create (e.g., 'ui_catalog', 'user')
propertiesYesKey-value pairs of entity property names to their values. Required fields depend on the entity schema — use get_entity_schema first.
Behavior5/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It warns about requiring permission, creating real data, and having no delete functionality, which are critical operational traits.

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 compact and well-structured, with a warning, step-by-step guidance, an example, and a final caution. Every sentence contributes meaningful information with no redundancy.

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 create tool with nested objects, the description covers prerequisites, usage, side effects, and a warning about irreversibility. It is sufficiently complete given the schema coverage and lack of an output schema.

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 input schema already documents all three parameters 100%, so the baseline is 3. The description adds a concrete example and clarifies nested child record creation, enhancing understanding beyond the schema alone.

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 'Create a new entity record' with a specific verb and resource, distinguishing it from sibling tools like get_entity_record and update_entity_record. It also highlights nested creation as a unique feature.

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 provides clear usage instructions, including an example and the requirement for Create permission. It does not explicitly name alternatives or exclusion scenarios, but the context strongly implies when this tool should be used.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexxcpr/ONE-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server