4d-mcp

upsert

Create or update single or multiple records in a specified 4D dataclass with one API call.

Instructions

Create or update records in a 4D dataclass

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": {
      "dataClass": "<dataClass>",
      "body": "<body>"
    },
    "name": "upsert"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Record data to create or update (object for single record, array for multiple)
`dataClass`	Yes	Name of the dataclass

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It only states 'Create or update records' without mentioning idempotency, partial vs full updates, how records are matched for update (e.g., primary key), or return values. Given that this is a mutating operation, this is a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It is efficient and to the point, though it could optionally incorporate more behavioral detail without losing conciseness.

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

Completeness2/5

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

The tool has no annotations and no output schema, so the description must compensate. It fails to mention bulk update behavior (array body), how existing records are identified for update, or what the response contains. For an upsert operation, this leaves the agent under-informed about critical usage details.

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 descriptions cover 100% of the parameters, so the baseline is 3. The tool description adds no additional parameter semantics beyond what the schema already provides. The body parameter's object/array duality is documented in the schema but not elaborated in the description.

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 operation ('Create or update') and the resource ('records in a 4D dataclass'), which is specific and distinct from sibling tools like query or delete. The verb 'upsert' in the name is reinforced by the description, leaving no ambiguity about the tool's purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context (e.g., 'use this to insert or modify records'). The usage context is only implied by the name and operation, not explicitly stated.

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

Deploy Server