Skip to main content
Glama

create_data_table_record

Create a record. Fails if recordKey already exists (use upsert_data_table_record to overwrite). data keys must match declared table fields. Starts at version 1. Use when inserting a new row such as a lead or ticket item.

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": {
      "dataTableId": "<dataTableId>",
      "recordKey": "<recordKey>",
      "data": "<data>"
    },
    "name": "create_data_table_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesField values keyed by schema field name
recordKeyYesBusiness key unique within the table
dataTableIdYesData table id

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive write. The description adds real behavior the annotations lack: it fails on duplicate recordKey, new records start at version 1, and data keys must match declared table fields. It does not say what error shape is returned or how versions advance, which keeps it short of a 5.

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?

Four short sentences, front-loaded with the action and the failure mode, followed by the data-key constraint, the version behavior, and the usage example. No sentence is filler or duplicative.

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 3-parameter mutation with no output schema, the description covers the failure mode, the sibling alternative, the data shape constraint, and the initial version. Nothing an agent needs to invoke it correctly is missing, and return values are not required since no output schema exists.

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?

Schema coverage is 100%, so the baseline would be 3. The description adds a constraint not in the schema: data keys must correspond to declared table fields, which warns the agent that arbitrary keys will fail validation. It only restates the recordKey uniqueness rule already in the schema.

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?

States a specific verb and resource ('Create a record') and immediately distinguishes itself from the nearest sibling by noting it fails on existing recordKey whereas upsert_data_table_record overwrites. An agent can pick between create and upsert without opening either schema.

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?

Explicitly routes the overwrite case to upsert_data_table_record and gives a concrete insertion scenario ('a lead or ticket item'). Lacks any statement of preconditions such as required permissions or whether the data table must already exist, but the create-vs-upsert split is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources