Skip to main content
Glama
Sign In

QuintaDB

by ru.quintadb
OverviewDiscussionsAdmin

seed_records

Seed a form with initial records in bulk. Use it to fill a form with test or reference data. For one record create_record is better. Supports subforms through subforms.

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": {
      "app_id": "<app_id>",
      "entity_id": "<entity_id>",
      "records": "<records>"
    },
    "name": "seed_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesProject ID (from list_projects)
recordsYesArray of records. Each record is a hash {field_name: value}
subformsNoSubform links [{property_id, dtype_id, subform_dtype_id}]. Rarely needed by hand.
entity_idYesForm ID (from list_forms or describe_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / records / description
      Previous value: -"Масив записів. Кожен запис — хеш {назва_поля: значення}"New value: +"Array of records. Each record is a hash {field_name: value}"
    • changedInput schema / properties / subforms / description
      Previous value: -"Зв'язки субформ [{property_id, dtype_id, subform_dtype_id}]. Рідко потрібно вручну."New value: +"Subform links [{property_id, dtype_id, subform_dtype_id}]. Rarely needed by hand."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world, so the safety profile is partly covered and the description adds the bulk and subform-support traits. However, for a mutation tool it does not say whether seeding is additive or overwrites/replaces existing records, nor that repeating the call may duplicate data (the non-idempotent hint). The sentence "Supports subforms through subforms" adds no real behavioral detail.

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 short sentences, front-loaded with the action and the bulk qualifier, then the intended use and the alternative. The final clause "Supports subforms through subforms" is circular and does not earn its place, a minor efficiency loss.

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

Completeness3/5

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

With four fully documented parameters and annotation coverage, the description covers purpose and the main alternative. It leaves open an important question for a bulk write tool — whether existing records are preserved or replaced and what happens on partial failure — which matters given the non-idempotent annotation and no output schema.

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 every parameter including the nested subform link objects is documented in the schema, setting the baseline at 3. The description only gestures at the subforms parameter and adds no interpretation of record hashes, required field values, or valid subform linkage beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — bulk-seed a form with initial records — and explicitly frames the operation as bulk rather than single. It contrasts itself with create_record, so an agent can distinguish it from the single-record path. It does not distinguish itself from other bulk write siblings like import_records or bulk_update_records, which slightly limits the differentiation.

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?

"Use it to fill a form with test or reference data" gives a clear intended context, and "For one record create_record is better" names the alternative and the condition that selects it. No exclusions are given relative to import_records or bulk_update_records, so the guidance, while clear, is incomplete for a toolset this dense.

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

All QuintaDB toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources