Skip to main content
Glama

create_data_table

Create a Persistent Data Table with a typed schema (string | number | boolean | datetime). Optional queueConfig seeds reserved queue fields. Returns the table including its id for record operations. Use when a playbook needs structured storage, for example lead lists, invoice queues, or triage inboxes.

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": {
      "name": "<name>",
      "fields": "<fields>"
    },
    "name": "create_data_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable table name
fieldsYesSchema fields: { name, type, required?, description? }
queueConfigNoMarks the table as a Queue Table. Seeds reserved fields status, priority, claimedAt, pausedAt, attempts, lastError (those names cannot be renamed or deleted while set).

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/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 create; the description goes further by explaining that queueConfig seeds reserved queue fields and that the response returns the table with its id for later record operations. It omits permission requirements, name-collision behavior, and any limits, so it is not fully transparent.

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?

Three sentences, front-loaded with the verb and resource, and every sentence carries information an agent needs (type limits, queue seeding, return shape, use case). Minor redundancy in re-listing the type enum that already appears in the schema.

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?

With no output schema, the description correctly compensates by stating what the call returns and that the id enables follow-on record operations. Given a nested queueConfig object and 100% schema coverage, the remaining gap is small: no mention of failure modes such as invalid or duplicate table names.

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%, so name, fields, and the nested queueConfig sub-fields are already documented. The description mostly restates the schema's type enum and the queueConfig seeding note rather than adding new parameter meaning; the one genuinely new element, the returned id, is output info rather than parameter guidance.

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 ('Create') plus resource ('Persistent Data Table') and pins down the scope with 'typed schema (string | number | boolean | datetime)'. The resource noun alone separates it cleanly from create_data_table_record, update_data_table, and list_data_tables.

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?

Gives a concrete when-to-use condition ('when a playbook needs structured storage') backed by three illustrative cases (lead lists, invoice queues, triage inboxes). It stops short of naming alternatives or stating when not to use it, which keeps it at 4 rather than 5.

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