smart-data-extractor

auto_schema_learn

Idempotent · 30s timeout · Automatically infer JSON Schema from sample data without extraction. Pass idempotency_key to deduplicate within 5 minutes.

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": {
      "sample_data": "<sample_data>"
    },
    "name": "auto_schema_learn"
  }
}

Input Schema

Name	Required	Description	Default
`sample_data`	Yes	Representative sample data as JSON string (array of objects or single object). Schema is inferred from structure; use first 1-10 rows for array samples. Max 200KB.
`idempotency_key`	No	Optional cache key (UUID/string) for 5-minute deduplication. Repeat calls with same key return cached inferred schema instantly.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedMay 19, 2026

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

changedInput schema / properties / idempotency_key / description

Previous value: -"Optional client-supplied key for dedup within 5min cache"New value: +"Optional cache key (UUID/string) for 5-minute deduplication. Repeat calls with same key return cached inferred schema instantly."

changedInput schema / properties / sample_data / description

Previous value: -"Sample JSON data as string (array or object)"New value: +"Representative sample data as JSON string (array of objects or single object). Schema is inferred from structure; use first 1-10 rows for array samples. Max 200KB."

addedInput schema / properties / sample_data / examples

Added value: +[
+  "{\"product_id\":123,\"title\":\"Laptop Pro\",\"price\":1299.99,\"in_stock\":true}",
+  "[{\"id\":1,\"email\":\"alice@example.com\",\"verified\":true},{\"id\":2,\"email\":\"bob@example.com\",\"verified\":false}]",
+  "{\"name\":\"Report Q1\",\"sections\":[{\"title\":\"Sales\",\"value\":50000}]}"
+]

Changed2 schema fields changedMay 19, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Optional client-supplied key for dedup within 5min cache",
+  "type": "string"
+}

changedInput schema / properties / sample_data / description

Previous value: -"Sample JSON data as string"New value: +"Sample JSON data as string (array or object)"

First observedMay 17, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden and succeeds by disclosing key behavioral traits: idempotency, 30-second timeout, 5-minute deduplication window, and the fact that it does not extract data. This is unusually transparent for a tool without annotations.

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?

The description is concise and front-loaded with key traits (Idempotent, 30s timeout) before stating the core function. The additional sentence about idempotency_key is necessary and directly actionable. No unnecessary words.

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 tool with only two parameters and no output schema or annotations, the description covers purpose, behavioral traits, and parameter guidance. It clearly implies the return value is a JSON Schema, making the tool's behavior complete enough for an agent to use correctly.

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 coverage is 100% with detailed parameter descriptions already provided in the schema. The description adds no new parameter semantics beyond what is already in the schema, such as the idempotency_key purpose, so it meets the baseline without adding extra value.

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 clearly states the tool infers JSON Schema from sample data, with the specific verb 'infer' and resource 'JSON Schema'. It distinguishes from sibling extraction tools via the phrase 'without extraction', making its unique purpose evident.

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?

The description provides clear context that this tool is for schema inference rather than data extraction, which implies when to use it versus the sibling tools. It also gives explicit guidance on using the idempotency_key for deduplication. However, it does not explicitly name alternatives or state when not to use it.

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

All smart-data-extractor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.