API Acre

data.clean

Read-onlyIdempotent

Clean CSV, TSV, JSON, JSON Lines, or YAML records with collision-safe header normalization, deterministic integrity hashes, and exact transformation counts.

Input Schema

TableJSON Schema

Name	Required	Description
`format`	Yes	Source format; use jsonl for JSON Lines or NDJSON
`content`	Yes
`trim_strings`	No
`empty_to_null`	No
`normalize_headers`	No

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Structured Dataset cleaning result
`meta`	Yes
`service`	Yes
`version`	Yes
`request_id`	Yes	Unique request identifier

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed7 schema fields changedAug 17, 2026

addedOutput schema / properties / meta / properties / next_actions / items / properties / checkout_path
```
Added value: +{
+  "pattern": "^/try/",
+  "type": "string"
+}
```
addedOutput schema / properties / meta / properties / next_actions / items / properties / executes_automatically
```
Added value: +{
+  "const": false,
+  "type": "boolean"
+}
```

addedOutput schema / properties / meta / properties / next_actions / items / properties / handoff_path

Added value: +{
+  "description": "Free full contract and spend-capped command handoff; reading it does not execute or purchase the follow-up.",
+  "pattern": "^/catalog/",
+  "type": "string"
+}

addedOutput schema / properties / meta / properties / next_actions / items / properties / handoff_payment_required
```
Added value: +{
+  "const": false,
+  "type": "boolean"
+}
```
addedOutput schema / properties / meta / properties / next_actions / items / properties / maximum_atomic_usdc
```
Added value: +{
+  "pattern": "^[1-9][0-9]*$",
+  "type": "string"
+}
```
addedOutput schema / properties / meta / properties / next_actions / items / properties / sample_path
```
Added value: +{
+  "pattern": "^/samples/",
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / properties / meta / properties / next_actions / items / required

Previous value: -[
-  "service",
-  "title",
-  "reason",
-  "method",
-  "path",
-  "price",
-  "input_template",
-  "use_output",
-  "authorization_required"
-]New value: +[
+  "service",
+  "title",
+  "reason",
+  "method",
+  "path",
+  "price",
+  "input_template",
+  "use_output",
+  "handoff_path",
+  "checkout_path",
+  "sample_path",
+  "maximum_atomic_usdc",
+  "handoff_payment_required",
+  "executes_automatically",
+  "authorization_required"
+]

Changed10 schema fields changedAug 14, 2026

addedOutput schema / properties / data / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / data / properties / cleaning

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "dateTimeScalarsNormalized": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "deterministic": {
+      "const": true,
+      "type": "boolean"
+    },
+    "emptyStringsAsNull": {
+      "type": "boolean"
+    },
+    "emptyStringsConvertedToNull": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "headerFieldsNormalized": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "networkRequestsMade": {
+      "const": 0,
+      "type": "integer"
+    },
+    "nodesProcessed": {
+      "maximum": 100000,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "nonStringKeysNormalized": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "normalizeHeaders": {
+      "type": "boolean"
+    },
+    "outputCanonicalization": {
+      "const": "json-sort-keys-compact-utf8",
+      "type": "string"
+    },
+    "sourceFormat": {
+      "enum": [
+        "csv",
+        "tsv",
+        "json",
+        "jsonl",
+        "yaml"
+      ],
+      "type": "string"
+    },
+    "stringsTrimmed": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "trimStrings": {
+      "type": "boolean"
+    },
+    "version": {
+      "const": "apiacre-data-clean/2",
+      "type": "string"
+    }
+  },
+  "required": [
+    "version",
+    "sourceFormat",
+    "trimStrings",
+    "emptyStringsAsNull",
+    "normalizeHeaders",
+    "headerFieldsNormalized",
+    "stringsTrimmed",
+    "emptyStringsConvertedToNull",
+    "nodesProcessed",
+    "nonStringKeysNormalized",
+    "dateTimeScalarsNormalized",
+    "outputCanonicalization",
+    "deterministic",
+    "networkRequestsMade"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / data / properties / inputSha256

Added value: +{
+  "pattern": "^[0-9a-f]{64}$",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / outputSha256

Added value: +{
+  "pattern": "^[0-9a-f]{64}$",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / records / items / type
```
Added value: +"object"
```
addedOutput schema / properties / data / properties / records / maxItems
```
Added value: +100000
```
addedOutput schema / properties / data / properties / rows / maximum
```
Added value: +100000
```
addedOutput schema / properties / data / properties / rows / minimum
```
Added value: +0
```

addedOutput schema / properties / data / properties / warnings

Added value: +{
+  "items": {
+    "maxLength": 120,
+    "type": "string"
+  },
+  "maxItems": 2,
+  "type": "array"
+}

addedOutput schema / properties / data / required

Added value: +[
+  "records",
+  "rows",
+  "inputSha256",
+  "outputSha256",
+  "cleaning",
+  "warnings"
+]

Changed2 schema fields changedAug 14, 2026

addedInput schema / properties / format / description

Added value: +"Source format; use jsonl for JSON Lines or NDJSON"

changedInput schema / properties / format / enum

Previous value: -[
-  "csv",
-  "json",
-  "yaml"
-]New value: +[
+  "csv",
+  "tsv",
+  "json",
+  "jsonl",
+  "yaml"
+]

Changed2 schema fields changedAug 11, 2026

addedOutput schema / properties / meta / properties / next_actions

Added value: +{
+  "description": "Optional separately priced follow-up calls. Each action requires a new payment challenge and explicit buyer authorization.",
+  "items": {
+    "properties": {
+      "authorization_required": {
+        "const": true,
+        "type": "boolean"
+      },
+      "input_template": {
+        "description": "Client-side template only: $request refers to the original input, $result to this response, and $json(...) serializes its argument. The server does not execute the follow-up.",
+        "type": "object"
+      },
+      "method": {
+        "const": "POST",
+        "type": "string"
+      },
+      "path": {
+        "pattern": "^/v1/",
+        "type": "string"
+      },
+      "price": {
+        "pattern": "^\\$[0-9]+",
+        "type": "string"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "service": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "use_output": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "service",
+      "title",
+      "reason",
+      "method",
+      "path",
+      "price",
+      "input_template",
+      "use_output",
+      "authorization_required"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / meta / required

Previous value: -[
-  "duration_ms",
-  "cached",
-  "sources",
-  "warnings"
-]New value: +[
+  "duration_ms",
+  "cached",
+  "sources",
+  "warnings",
+  "next_actions"
+]

First observedAug 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds specific behavioral details beyond the annotations, such as collision-safe header normalization, deterministic integrity hashes, and exact transformation counts, giving agents a clearer picture of what the operation does and returns. No contradiction with annotations.

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?

The description is a single sentence that front-loads the core purpose and lists supported formats and key features without redundancy. It is dense but not bloated; a slight structural breakdown could improve scannability, but it remains concise and effective.

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?

The output schema exists, so the description does not need to explain return values. It covers supported formats and the main transformation behaviors, while the schema handles limits like maxLength and the enum for format. The main gap is insufficient explanation of parameter semantics, but this is partly mitigated by the output schema and self-explanatory parameter names.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% (only 'format' is described). The description mentions 'collision-safe header normalization,' which partially explains normalize_headers, but trim_strings and empty_to_null are left entirely to their names. There is no clarification of how empty strings become null or how trimming behavior works, so parameter semantics remain under-specified.

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?

The description uses the specific verb 'clean' with a clear resource (CSV/TSV/JSON/JSONL/YAML records) and elaborates on what cleaning entails: collision-safe header normalization, deterministic integrity hashes, and exact transformation counts. This distinguishes it from sibling tools like data.convert and data.deduplicate, which have different purposes.

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?

No explicit when-to-use or alternative guidance is provided. The intent is implied by the purpose, suggesting use when records need standardization or transformation metrics, but it does not mention when not to use it or how it compares to closely related tools such as data.deduplicate or data.json-repair.

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

All API Acre tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Tools are grouped into clear domain prefixes (crypto, data, developer, document, research, web) and each tool name describes a specific function; however, a few umbrella tools like web.full-audit and data.contract overlap with their more targeted counterparts, creating minor ambiguity.

Naming Consistency5/5

All tool names follow a consistent pattern: a domain prefix, a dot, and a hyphenated lowercase compound name (e.g., crypto.base-block-inspect, web.seo-audit). This makes naming predictable and easy to scan.

Tool Count1/5

At 63 tools, the surface area is very large and exceeds the 50+ threshold for extreme mismatch. While the tools are organized into six domains, the sheer number makes it difficult for an agent to select efficiently, and some tools are bundled combinations of others.

Completeness5/5

Each domain offers a thorough set of operations: crypto covers address, account, block, contract, events, gas, and transaction inspection; data covers cleaning, conversion, schema, and validation; developer covers code review, dependency/license audits, and test generation; research covers SEC, OFAC, GLEIF, and USAspending; web covers extraction, SEO, security, and performance. No obvious dead ends exist for the read-only/inspection purpose.

Resources

Need Help?