Skip to main content
Glama
alexxcpr

ONE-MCP

by alexxcpr

update_entity_record

Update an existing entity record by specifying the entity, primary key, and properties to change. Only the provided properties are modified, preserving all other fields.

Instructions

Update an existing entity record. ⚠️ Requires Update permission on the entity.

Provide the entity name, primary key, and the properties to update. Only the properties you include will be changed — others remain unchanged. Optionally include child entity records.

IMPORTANT: This modifies real data. There is NO delete/undo via this MCP. Use get_entity_record first to see the current state before updating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesThe primary key of the record to update
childrenNoOptional. Map of child entity names to arrays of child records. When updating children, include the full set of children you want to exist after the update (existing children not included may be removed).
entityNameYesThe entity name to update (e.g., 'ui_catalog', 'user')
propertiesYesKey-value pairs of entity property names to their new values. Only include the fields you want to change.
Behavior5/5

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

With no annotations provided, the description fully carries the burden. It discloses the required Update permission, the fact that only included properties change, the full-replacement semantics for children, and the irreversible nature of the operation. This goes far beyond a simple 'update' statement.

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 concise and well-structured: a clear purpose line, a usage summary, and a prominent warning. Each sentence provides essential information without redundancy or fluff.

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 tool is a mutation with nested objects and no output schema. The description covers permissions, partial updates, children replacement, and read-before-update. It doesn't mention what the tool returns (e.g., updated record or success message), which would normally be needed without an output schema, but it is otherwise quite complete.

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% and the schema already describes each parameter. The description adds minimal parameter-specific value, mostly restating what the schema says. It does clarify the partial-update semantics for 'properties' but the schema already conveys 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?

The description begins with a clear verb and resource: 'Update an existing entity record.' This distinguishes it from sibling tools like create_entity_record and get_entity_record by explicitly stating that it modifies an already-existing record.

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 advises using get_entity_record before updating and warns that there is no undo. While it doesn't explicitly say when not to use this tool, it provides clear context for safe usage and a concrete alternative for inspection.

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