smart-data-extractor

extract_from_api

Idempotent · 30s timeout · Extract structured data from API response JSON with schema adaptation. 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": {
      "content": "<content>"
    },
    "name": "extract_from_api"
  }
}

Input Schema

Name	Required	Description
`schema`	No	Optional target JSON Schema (draft-07) for field extraction. If omitted, inferred from content structure. Enforces consistent field extraction across multiple API responses.
`content`	Yes	API response body as raw JSON string (max 200KB). Can be single object, array of objects, or array of primitives. Automatically parsed and validated.
`idempotency_key`	No	Optional deduplication key (UUID or unique string) for 5-minute cache. Identical calls return cached result instantly.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedMay 19, 2026

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

changedInput schema / properties / content / description

Previous value: -"API response content (JSON string)"New value: +"API response body as raw JSON string (max 200KB). Can be single object, array of objects, or array of primitives. Automatically parsed and validated."

addedInput schema / properties / content / examples

Added value: +[
+  "{\"id\":1,\"name\":\"Alice\",\"role\":\"admin\"}",
+  "[{\"id\":1,\"name\":\"Alice\"},{\"id\":2,\"name\":\"Bob\"}]",
+  "[{\"user\":{\"id\":1,\"name\":\"Alice\"},\"status\":\"active\"}]"
+]

changedInput schema / properties / idempotency_key / description

Previous value: -"Optional client-supplied key for dedup within 5min cache"New value: +"Optional deduplication key (UUID or unique string) for 5-minute cache. Identical calls return cached result instantly."

changedInput schema / properties / schema / description

Previous value: -"Optional JSON Schema. If omitted, auto-inferred from content."New value: +"Optional target JSON Schema (draft-07) for field extraction. If omitted, inferred from content structure. Enforces consistent field extraction across multiple API responses."

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 / schema / description

Previous value: -"Optional schema for extraction. Auto-inferred if not provided"New value: +"Optional JSON Schema. If omitted, auto-inferred from content."

First observedMay 17, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently indicates idempotency, a 30s timeout, and a 5-minute deduplication window via `idempotency_key`. These are meaningful behavioral traits beyond what the schema reveals.

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 information ('Idempotent · 30s timeout') followed by the core purpose. Every sentence adds value, with no redundancy or filler.

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?

Given the moderate complexity (3 parameters, no output schema), the description covers the essential purpose and behavioral traits. It could mention the return format or error handling, but the schema already handles parameter details, making the description sufficiently complete for most use cases.

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 each parameter already has a detailed description. The tool description only mentions `idempotency_key` without adding new meaning beyond the schema. Thus, it meets the baseline for high coverage but does not exceed it.

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 states 'Extract structured data from API response JSON with schema adaptation'—a specific verb and resource that clearly defines the tool's function. This differentiates it from siblings like extract_from_url and batch_extract, which target different input sources or processing modes.

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 for use: API response JSON and schema adaptation. However, it does not explicitly state when to use this tool versus alternatives or when not to use it, so it earns a 4 rather than a 5.

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.