API Hub MCP — 337+ Tools

tsv_to_json

Convert tab-separated values (TSV) into structured JSON arrays for easy data handling.

Instructions

Convert tab-separated values (TSV) to JSON format.

Use this to transform TSV data from spreadsheets or database exports
into structured JSON arrays.

Parameters:
    tsv — TSV text with header row and data rows (tab-separated).

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": {
      "tsv": "<tsv>"
    },
    "name": "tsv_to_json"
  }
}

Input Schema

Name	Required	Description	Default
`tsv`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.1Jun 22, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It states it expects TSV text with header row and produces JSON arrays, but lacks details on edge cases, error handling, or format strictness.

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: two sentences plus parameter explanation. The purpose is front-loaded, and every sentence adds value without redundancy.

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 tool's simplicity (one input, clear conversion) and existence of an output schema (not shown), the description is fairly complete. It mentions the output is 'structured JSON arrays', which is sufficient, though it could mention error conditions or format constraints.

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

Parameters4/5

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

The only parameter 'tsv' has 0% schema description coverage, but the tool description compensates by explaining it is 'TSV text with header row and data rows (tab-separated)'. This adds meaningful context beyond the schema's type string.

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 verb 'Convert' and the resource 'TSV to JSON', and explains it transforms TSV text into structured JSON arrays. It distinguishes from sibling tool convert_csv_to_json by specifying TSV format.

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 says 'Use this to transform TSV data from spreadsheets or database exports', providing clear context. It does not explicitly mention when not to use or alternative tools, but the use case is well-defined.

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

Deploy Server