Skip to main content
Glama

Commit bulk import

commit_import
Destructive

Commit a bulk-import CSV, creating the work hierarchy (customers, projects, tasks, subtasks) in the organization. Call validate_import first to verify the file.

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": {
      "csv_content": "<csv_content>"
    },
    "name": "commit_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
csv_contentYesThe CSV content to import. Must pass validate_import with no errors first.
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false; the description adds useful context by enumerating the entity types that will be created. However, for a destructive bulk write it says nothing about atomicity/partial-failure behavior, duplicate handling, or whether existing records are matched or re-created.

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 front-loaded sentences with no filler: the effect first, the prerequisite second. Every clause carries information.

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 prerequisite and target entities are covered, and no output schema exists so return values need not be described. But a destructive, non-idempotent bulk-commit with only two parameters still leaves the agent guessing about rollback behavior and duplicate detection, which matters before invoking it.

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 both parameters are already documented in the schema, including the idempotency_key retry semantics. The description only echoes the csv_content validation requirement and adds nothing about idempotency_key, so baseline 3 applies.

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?

Names a specific verb ('commit') and resource ('a bulk-import CSV') and states the concrete effect: creating the customer/project/task/subtask hierarchy in the organization. That is well beyond restating the title, though the distinction from the sibling bulk_* tools is implied rather than stated.

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 an explicit prerequisite and ordering: 'Call validate_import first to verify the file,' reinforced by the schema note that the CSV must pass validation with no errors. It lacks any when-not guidance (e.g., when to use individual create_* tools instead), so it stops short of a 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