Skip to main content
Glama
Sign In
Coherence XRM

Coherence XRM

Official
by getcoherence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_record

Create a new record in any module. Provide a display name and field values to populate the record.

Instructions

Create a new record in a module. Provide displayName and a fields object with field values keyed by field ID or label.

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": {
      "moduleSlug": "<moduleSlug>",
      "displayName": "<displayName>"
    },
    "name": "create_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
moduleSlugYesModule slug
displayNameYesDisplay name for the record
fieldsNoField values keyed by field ID
ownerUserIdNoOwner user ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

B3.4/5.0
Behavior3/5

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

The description clearly indicates a write operation ('Create'), but with no annotations, the burden falls on the description. It lacks details on idempotency, side effects, permissions, or response format, which are not disclosed.

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 a single, front-loaded sentence with no wasted words. It efficiently communicates the tool's action and key inputs.

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?

Despite the moderate complexity (4 params, nested fields), the description is minimal. It fails to explain the return value, ownerUserId purpose, or behavior beyond creation. The schema covers each parameter, but the description lacks contextual completeness.

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 baseline is 3. The description adds some value by noting that fields keys are field IDs or labels, but it doesn't significantly augment the schema's parameter descriptions.

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 creates a new record in a module, specifying the key parameters (displayName and fields). This distinguishes it from sibling tools like update_record or delete_record, which modify or remove records.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it, prerequisites, or comparisons with sibling tools like update_record.

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