HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News

Read a government dataset file as JSON rows

hubvibe_opendata_table

Read-onlyIdempotent

Dataset file to JSON rows: a CSV, TSV, XLSX or JSON link from any portal, an e-Stat (Japan) download or a data.go.kr (Korea) dataset page. Encoding detected (Korean, Japanese, Chinese, UTF and Western code pages), header row found, numbers typed, XLSX sheets selectable, large files capped and disclosed. Use it after opendata.search or on any data file URL. Input: url; optional max_rows, sheet, encoding, delimiter. $0.10 per call. Returns: source_url, resolved_from, file_url, final_url, filename, content_type, bytes, format, encoding, sheet, sheets[], columns[], column_count, rows[{...}], row_count, total_rows, truncated, notes[], checked_at.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	File link, e-Stat file-download link, or a data.go.kr dataset page.
`sheet`	No	XLSX sheet name or 0-based index. Default: first sheet.
`encoding`	No	Force a codec (cp949, shift_jis, big5). Default: detected.
`language`	No	Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable strings of the result (notes, details, reasons) are translated into this language; data, codes, numbers and URLs are untouched. Default: as produced.
`max_rows`	No	Rows to return, default 200.
`delimiter`	No	Force a CSV delimiter. Default: sniffed.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes
`status`	Yes
`worker`	Yes
`price_usd`	Yes
`provenance`	Yes
`receipt_id`	Yes
`attribution`	No
`receipt_url`	Yes
`billing_warning`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedOct 1, 2026

removedOutput schema / description

Removed value: -"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on every /work route. A receipt for the job is at `receipt_url`."

removedOutput schema / properties / attribution / description

Removed value: -"Present only when the result's text was machine-translated: the credit to show with it."

removedOutput schema / properties / attribution / items / description
```
Removed value: -"A credit."
```

removedOutput schema / properties / attribution / items / properties

Removed value: -{
-  "text": {
-    "description": "Credit.",
-    "examples": [
-      "Translated by Google"
-    ],
-    "type": "string"
-  },
-  "url": {
-    "description": "Link.",
-    "examples": [
-      "https://translate.google.com"
-    ],
-    "type": "string"
-  }
-}

removedOutput schema / properties / attribution / items / required
```
Removed value: -[
-  "text",
-  "url"
-]
```
removedOutput schema / properties / attribution / items / type
```
Removed value: -"object"
```

removedOutput schema / properties / billing_warning / description

Removed value: -"Present only when the charge was recorded with a caveat."

removedOutput schema / properties / billing_warning / examples
```
Removed value: -[
-  "settlement pending"
-]
```
removedOutput schema / properties / price_usd / description
```
Removed value: -"What this call cost, in USD."
```
removedOutput schema / properties / price_usd / examples
```
Removed value: -[
-  0.02
-]
```

removedOutput schema / properties / provenance / description

Removed value: -"How the result was produced: which providers ran and how long each took."

removedOutput schema / properties / provenance / properties

Removed value: -{
-  "attempts": {
-    "description": "Provider attempts made, including retries and failovers.",
-    "examples": [
-      1
-    ],
-    "type": "integer"
-  },
-  "elapsed_ms": {
-    "description": "Wall-clock milliseconds for the whole job.",
-    "examples": [
-      340
-    ],
-    "type": "integer"
-  },
-  "providers_used": {
-    "description": "Providers that served the job.",
-    "examples": [
-      [
-        "coinbase-advanced-trade-public"
-      ]
-    ],
-    "items": {
-      "description": "Provider name.",
-      "examples": [
-        "coinbase-advanced-trade-public"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "steps": {
-    "description": "Every step the job ran, in order.",
-    "items": {
-      "description": "One step of the job.",
-      "properties": {
-        "ms": {
-          "description": "Milliseconds the step took.",
-          "examples": [
-            312
-          ],
-          "type": "integer"
-        },
-        "ok": {
-          "description": "Whether the step succeeded.",
-          "examples": [
-            true
-          ],
-          "type": "boolean"
-        },
-        "provider": {
-          "description": "Provider that served the step.",
-          "examples": [
-            "coinbase-advanced-trade-public"
-          ],
-          "type": "string"
-        },
-        "reason": {
-          "description": "Failure reason, on a failed step.",
-          "examples": [
-            "provider_timeout"
-          ],
-          "type": "string"
-        },
-        "step": {
-          "description": "Step name inside the worker.",
-          "examples": [
-            "quote"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "step",
-        "ok",
-        "ms"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / properties / provenance / required

Removed value: -[
-  "steps",
-  "providers_used",
-  "attempts",
-  "elapsed_ms"
-]

removedOutput schema / properties / receipt_id / description
```
Removed value: -"Receipt id for this job."
```
removedOutput schema / properties / receipt_id / examples
```
Removed value: -[
-  "rcpt_9f1c2b3a4d5e6f70"
-]
```

removedOutput schema / properties / receipt_url / description

Removed value: -"Where to fetch the machine-readable receipt (free, no payment)."

removedOutput schema / properties / receipt_url / examples

Removed value: -[
-  "/work/receipts/rcpt_9f1c2b3a4d5e6f70"
-]

removedOutput schema / properties / result / properties

Removed value: -{
-  "bytes": {
-    "description": "File size in bytes.",
-    "examples": [
-      12331
-    ],
-    "type": "integer"
-  },
-  "checked_at": {
-    "description": "When this node read the source (UTC). Nothing here is cached.",
-    "examples": [
-      "2026-09-26T18:00:00Z"
-    ],
-    "format": "date-time",
-    "type": "string"
-  },
-  "column_count": {
-    "description": "Number of columns.",
-    "examples": [
-      14
-    ],
-    "type": "integer"
-  },
-  "columns": {
-    "description": "Columns in file order.",
-    "examples": [
-      [
-        "행정구역코드",
-        "행정구역명",
-        "성별",
-        "내국인"
-      ]
-    ],
-    "items": {
-      "description": "Column name from the header row.",
-      "examples": [
-        "행정구역명"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "content_type": {
-    "description": "Server content type.",
-    "examples": [
-      "application/octet-stream"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "encoding": {
-    "description": "Text encoding used; null for XLSX.",
-    "examples": [
-      "cp949"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "file_url": {
-    "description": "The file actually fetched.",
-    "examples": [
-      "https://www.data.go.kr/cmm/cmm/fileDownload.do?atchFileId=FILE_000000003522968&fileDetailSn=1&insertDataPrcus=N"
-    ],
-    "type": "string"
-  },
-  "filename": {
-    "description": "File name from the server or the URL.",
-    "examples": [
-      "울산광역시_인구 현황(20251112).csv"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "final_url": {
-    "description": "After redirects.",
-    "examples": [
-      "https://www.data.go.kr/cmm/cmm/fileDownload.do?atchFileId=FILE_000000003522968&fileDetailSn=1&insertDataPrcus=N"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "format": {
-    "description": "Parsed format.",
-    "enum": [
-      "csv",
-      "tsv",
-      "xlsx",
-      "json"
-    ],
-    "examples": [
-      "csv"
-    ],
-    "type": "string"
-  },
-  "notes": {
-    "description": "Caveats; empty when none.",
-    "examples": [
-      []
-    ],
-    "items": {
-      "description": "A caveat.",
-      "examples": [
-        "45 data rows in the file; the first 5 are returned (max_rows)."
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "resolved_from": {
-    "description": "The dataset page that was resolved to a file link; null when a file link was given.",
-    "examples": [
-      "https://www.data.go.kr/data/15005995/fileData.do"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "row_count": {
-    "description": "Rows returned.",
-    "examples": [
-      5
-    ],
-    "type": "integer"
-  },
-  "rows": {
-    "description": "Rows in file order, up to max_rows.",
-    "items": {
-      "additionalProperties": true,
-      "description": "One row keyed by column; numbers typed, blanks null.",
-      "examples": [
-        {
-          "내국인": 564888,
-          "성별": "남자",
-          "행정구역명": "울산광역시",
-          "행정구역코드": 31
-        }
-      ],
-      "properties": {},
-      "required": [],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "sheet": {
-    "description": "XLSX sheet read; null otherwise.",
-    "examples": [
-      "Sheet1"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "sheets": {
-    "description": "All sheet names for an XLSX; empty otherwise.",
-    "examples": [
-      []
-    ],
-    "items": {
-      "description": "Sheet name.",
-      "examples": [
-        "Sheet1"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "source_url": {
-    "description": "The URL as given.",
-    "examples": [
-      "https://www.data.go.kr/data/15005995/fileData.do"
-    ],
-    "type": "string"
-  },
-  "total_rows": {
-    "description": "Data rows in the file (excluding the header).",
-    "examples": [
-      45
-    ],
-    "type": "integer"
-  },
-  "truncated": {
-    "description": "True when total_rows exceeds max_rows.",
-    "examples": [
-      true
-    ],
-    "type": "boolean"
-  }
-}

removedOutput schema / properties / result / required

Removed value: -[
-  "source_url",
-  "resolved_from",
-  "file_url",
-  "final_url",
-  "filename",
-  "content_type",
-  "bytes",
-  "format",
-  "encoding",
-  "sheet",
-  "sheets",
-  "columns",
-  "column_count",
-  "rows",
-  "row_count",
-  "total_rows",
-  "truncated",
-  "notes",
-  "checked_at"
-]

removedOutput schema / properties / status / description

Removed value: -"Present only on a delivered result."

removedOutput schema / properties / worker / description

Removed value: -"Catalog name of the worker that ran."

removedOutput schema / properties / worker / examples
```
Removed value: -[
-  "market.quote"
-]
```

removedOutput schema / title

Removed value: -"opendata.table response"

Changed1 schema field changedSep 28, 2026

addedOutput schema / properties / attribution

Added value: +{
+  "description": "Present only when the result's text was machine-translated: the credit to show with it.",
+  "items": {
+    "description": "A credit.",
+    "properties": {
+      "text": {
+        "description": "Credit.",
+        "examples": [
+          "Translated by Google"
+        ],
+        "type": "string"
+      },
+      "url": {
+        "description": "Link.",
+        "examples": [
+          "https://translate.google.com"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "text",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable strings of the result (notes, details, reasons) are translated into this language; data, codes, numbers and URLs are untouched. Default: as produced.",
+  "maxLength": 35,
+  "pattern": "^[A-Za-z]{2,3}(-[A-Za-z0-9]{2,8})*$",
+  "type": "string"
+}

AddedSep 27, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial behavior beyond them: automatic encoding detection, header discovery, number typing, sheet selection, truncation of large files being disclosed, and a per-call cost. The truncation and cost disclosures are exactly the kind of non-obvious traits an agent needs.

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?

Front-loaded with the core purpose and source coverage, then behavior, then usage, then I/O. Efficient despite being dense. The 'Returns:' enumeration is somewhat redundant given an output schema exists, costing a bit of the score.

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?

For a read tool with full annotations, an output schema, and 100% schema coverage, this is largely complete: sources, detection behaviors, limits, cost, and the upstream sibling are all covered. The only gaps are the unmentioned 'language' parameter and no explicit unsupported-format guidance.

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 schema already documents each parameter including enums-free codecs and defaults. The description only lists a subset of params (url, max_rows, sheet, encoding, delimiter) and even omits 'language', adding essentially no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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?

States a precise verb and resource ('Dataset file to JSON rows') and enumerates the accepted sources (CSV/TSV/XLSX/JSON links, e-Stat, data.go.kr). It explicitly distinguishes itself from the sibling hubvibe_opendata_search, so an agent can route between them without opening schemas.

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?

Gives clear context: 'Use it after opendata.search or on any data file URL.' This names the upstream sibling and the general trigger condition. It lacks an explicit when-not or an alternative for non-tabular/unsupported formats, which keeps it short of a 5.

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

All HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News 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.