Agent Revenue Network

JSON Dataset Profiling · Data Quality

dataset_profile

Read-onlyIdempotent

Discover deterministic data-quality profiling for 1-5,000 JSON-object rows. Paid execution counts field presence, missing and null values, observed primitive types, primitive cardinality and exact duplicate rows without modifying input; use schema_infer to draft a flat-record contract or tabular_validate to enforce one. This is not statistical inference. This free MCP discovery call does not execute the advertised capability and does not charge; it returns the exact x402 endpoint, price and payment guide for execution.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`rows`	Yes	1-5,000 JSON objects. Rows are analyzed in memory and are not modified.

Output Schema

TableJSON Schema

Name	Required	Description
`price`	Yes
`method`	Yes	HTTP method for paid execution.
`endpoint`	Yes	Canonical absolute ARN HTTP URL to POST the same tool arguments to for paid execution.
`protocol`	Yes	Payment protocol required by the HTTP execution endpoint.
`instruction`	Yes	How to execute the capability after receiving the payment requirement.
`paymentGuide`	Yes	Public setup guide with a working x402 v2 Base-mainnet client example.
`paymentRequired`	Yes	Always true for paid ARN capabilities exposed over MCP.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 20, 2026

changedOutput schema / properties / endpoint / description

Previous value: -"ARN HTTP path to POST the same tool arguments to for paid execution."New value: +"Canonical absolute ARN HTTP URL to POST the same tool arguments to for paid execution."

addedOutput schema / properties / endpoint / format
```
Added value: +"uri"
```

addedOutput schema / properties / method

Added value: +{
+  "const": "POST",
+  "description": "HTTP method for paid execution.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "paymentRequired",
-  "protocol",
-  "endpoint",
-  "price",
-  "paymentGuide",
-  "instruction"
-]New value: +[
+  "paymentRequired",
+  "protocol",
+  "method",
+  "endpoint",
+  "price",
+  "paymentGuide",
+  "instruction"
+]

Changed2 schema fields changedOct 8, 2026

addedOutput schema / properties / paymentGuide

Added value: +{
+  "description": "Public setup guide with a working x402 v2 Base-mainnet client example.",
+  "format": "uri",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "paymentRequired",
-  "protocol",
-  "endpoint",
-  "price",
-  "instruction"
-]New value: +[
+  "paymentRequired",
+  "protocol",
+  "endpoint",
+  "price",
+  "paymentGuide",
+  "instruction"
+]

Changed5 schema fields changedOct 2, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / description

Added value: +"Input for bounded profiling of a JSON-record dataset."

addedInput schema / properties / rows / description

Added value: +"1-5,000 JSON objects. Rows are analyzed in memory and are not modified."

addedInput schema / properties / rows / minItems
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "description": "MCP payment instruction. Calling the MCP tool itself does not charge or execute the paid operation.",
+  "properties": {
+    "endpoint": {
+      "description": "ARN HTTP path to POST the same tool arguments to for paid execution.",
+      "type": "string"
+    },
+    "instruction": {
+      "description": "How to execute the capability after receiving the payment requirement.",
+      "type": "string"
+    },
+    "paymentRequired": {
+      "const": true,
+      "description": "Always true for paid ARN capabilities exposed over MCP.",
+      "type": "boolean"
+    },
+    "price": {
+      "additionalProperties": false,
+      "properties": {
+        "amount": {
+          "description": "Atomic asset amount.",
+          "type": "string"
+        },
+        "asset": {
+          "description": "Settlement asset.",
+          "type": "string"
+        },
+        "display": {
+          "description": "Human-readable current price.",
+          "type": "string"
+        },
+        "network": {
+          "description": "CAIP-2 settlement network identifier.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "amount",
+        "asset",
+        "network",
+        "display"
+      ],
+      "type": "object"
+    },
+    "protocol": {
+      "const": "x402",
+      "description": "Payment protocol required by the HTTP execution endpoint.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "paymentRequired",
+    "protocol",
+    "endpoint",
+    "price",
+    "instruction"
+  ],
+  "type": "object"
+}

First observedOct 2, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the readOnly, idempotent, and non-destructive annotations, the description discloses that this is a free discovery call that does not execute the advertised capability or charge, that paid execution counts field presence, missing/null values, primitive types, cardinality, and exact duplicates, and that it returns the x402 endpoint, price, and payment guide.

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 dense but tightly written, with the purpose front-loaded and each sentence adding useful information about capability, alternatives, exclusion, and discovery/payment behavior. The important caveat that this is a free discovery call rather than execution is placed last, which is slightly less ideal structurally but does not make the description verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with an output schema and rich annotations, the description supplies the missing context: what profiling metrics would be counted under paid execution, how this free discovery call differs, and what it returns. Nothing essential for correct invocation appears to be missing.

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 the single rows parameter is already fully documented with its 1-5,000 item bounds and object type. The description repeats the same range and JSON-object framing without adding new syntax or handling details beyond what the schema already provides.

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 (deterministic data-quality profiling for JSON-object rows) and later clarifies that the call itself is a free discovery endpoint that returns execution metadata. It distinguishes itself from schema_infer and tabular_validate, though the initial framing as profiling could briefly mislead an agent because the call does not actually execute the profiling.

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?

It names concrete alternatives: use schema_infer to draft a flat-record contract or tabular_validate to enforce one, and explicitly excludes statistical inference. It also explains the paid-execution versus free-discovery distinction, providing clear context for when to use this call, though it does not list every profiling alternative among the siblings.

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

All Agent Revenue Network tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?