validate_csv
MCP server · Local · nothing leaves your machine
Lints your header row, and any sample values you pass, against the drop rules, then proposes a column mapping for what is left. The report never repeats back a value it flagged. Run it before every upload.
It runs in your own process and sends nothing anywhere, so the whole preparation happens before anything leaves the org.
What it needs
| Argument | Type | Required | Description |
|---|---|---|---|
headers | array | Yes | |
sample_values | any | No |
What it returns
A verdict on whether the file is safe to upload - ready, incomplete, or do not upload - with every flagged column and the reason it was flagged, and a proposed mapping for the columns that are left.
Credential
None. This tool runs entirely inside the agent: it makes no network call, needs no credential, and sends none of what you pass it anywhere.
Network call: no. The full credential split is on authentication.
Example call
Most readers never write the protocol themselves: the agent does, once the server is connected. Both forms are the same call.
Use the ax1om MCP server.Call validate_csv: lints your header row, and any sample values you pass, against the drop rules, then proposes a column mapping for what is left.{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "validate_csv", "arguments": {} }}The arguments object is whatever this tool's own input schema declares. An MCP client reads that schema from the server, so it is the server that answers for the exact shape rather than this page.