Skip to main content
Glama

Validate bulk import

validate_import
Read-onlyIdempotent

Validate a bulk-import CSV without persisting anything. Returns row-level errors and a summary so you can fix the file before calling commit_import.

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": "validate_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
csv_contentYesThe CSV content to validate (use the template from get_import_template).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description reinforces this with 'without persisting anything' and adds genuinely new behavior by disclosing the return shape (row-level errors plus a summary) in the absence of an output schema. It stops short of noting limits on how many row errors are returned or size constraints on the CSV.

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 with no filler; the non-persistence guarantee is front-loaded and the pre-commit workflow follows immediately. Every clause carries information an agent would otherwise have to guess.

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?

For a one-parameter, non-destructive tool with no output schema, the definition covers purpose, side effects, return shape and downstream handoff. Only minor operational details (validation limits, template reference, behavior on malformed versus semantically invalid rows) are left unaddressed.

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?

There is a single parameter with 100% schema description coverage, and the schema itself points to get_import_template for the expected format, so the description does not need to re-explain it. The description adds no format or encoding detail beyond what the schema already supplies, which is the expected baseline.

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 ('Validate') plus a specific resource ('bulk-import CSV') and immediately adds the negative scope 'without persisting anything', which separates it from the write-side sibling commit_import. An agent can identify the operation without opening the schema.

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

Usage Guidelines5/5

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

Explicitly prescribes the workflow: validate first, 'fix the file before calling commit_import', naming the alternative tool and the condition that selects it. The when-to-use and the ordering relative to commit_import are both stated, leaving nothing to inference.

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