Skip to main content
Glama
Sign In

QuintaDB

by ru.quintadb
OverviewDiscussionsAdmin

import_records

Import records in bulk from CSV or an array of objects. For the 'records' array ALWAYS use field IDs as keys.

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>"
    },
    "name": "import_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_idYesProject ID (from list_projects)
recordsNoArray of objects whose keys are the form's field IDs (not names!). An alternative to csv_text. Example: [{"dcTrJdP1bppyk3vCkKvCoN": "John"}]
csv_textNoCSV text with headers in the first row. Commas and semicolons are both taken as separators. Example: "Name,Email,Status\nJohn,john@ex.com,New"
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 / csv_text / description
      Previous value: -"CSV-текст з заголовками в першому рядку. Підтримує коми і крапку з комою як роздільник. Приклад: \"Ім'я,Email,Статус\\nІван,ivan@ex.com,Новий\""New value: +"CSV text with headers in the first row. Commas and semicolons are both taken as separators. Example: \"Name,Email,Status\\nJohn,john@ex.com,New\""
    • changedInput schema / properties / records / description
      Previous value: -"Масив об'єктів де ключі — ID полів форми (не назви!). Альтернатива до csv_text. Приклад: [{\"dcTrJdP1bppyk3vCkKvCoN\": \"Іван\"}]"New value: +"Array of objects whose keys are the form's field IDs (not names!). An alternative to csv_text. Example: [{\"dcTrJdP1bppyk3vCkKvCoN\": \"John\"}]"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-readOnly, non-destructive, non-idempotent mutation on a closed world, so the safety profile is covered. The description adds one genuinely important operational constraint — records array keys must be field IDs — which is useful. However, it says nothing about duplicate handling, partial-failure semantics, size limits, or whether csv_text and records are mutually exclusive, which are exactly the behaviors that matter for a bulk write.

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?

Two sentences, front-loaded with the action and the two input modes, then the one non-obvious constraint in caps. No filler; every sentence earns its place.

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?

The tool is a four-parameter bulk mutation with no output schema, so the description should carry more weight on failure behavior and the relationship between csv_text and records. Annotations cover the mutation safety profile and the schema covers parameters, but the agent is left guessing about exclusivity of the two input modes and what happens when some rows fail validation.

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 all four parameters (app_id, entity_id, records, csv_text) are already documented with examples, including the field-ID key rule. The description reinforces the field-ID constraint but adds no syntax or format detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

The description states a specific verb and resource ('Import records in bulk') and enumerates the two accepted input sources (CSV text or array of objects). It does not name relevant siblings like create_record (single-record) or bulk_update_records, so the agent must infer why it would choose this over bulk_update_records.

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

Usage Guidelines3/5

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

Bulk import is implied as the use case, but there is no explicit when-to-use guidance, no mention of when to prefer create_record or bulk_update_records, and no statement about prerequisites such as the form/entity needing pre-existing fields. Usage must be inferred from the tool name and the 'bulk' qualifier.

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