Skip to main content
Glama

table_convert

Convert table data between CSV, TSV, JSON, JSONL, Markdown, and HTML to move structured data across formats or files.

Instructions

Convert tables between CSV, TSV, JSON, JSONL, Markdown, HTML (JSON output typed).

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": {
      "to": "<to>"
    },
    "name": "table_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromNo
pathNoor a file
textNo
out_pathNo
delimiterNo
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

B3.2/5.0
Behavior3/5

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

With only destructiveHint=false supplied, the description adds one genuinely useful behavioral detail: JSON output is typed. However it says nothing about the overwrite behavior exposed by the overwrite parameter, whether writing to out_path clobbers existing files, or how text vs path input is resolved — relevant for a tool that writes files.

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?

A single compact sentence with the verb and format set front-loaded and no filler. The trailing parenthetical '(JSON output typed)' is slightly cryptic, but nothing is wasted.

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

Completeness3/5

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

For a seven-parameter converter with low schema coverage and no output schema, the description covers the core purpose but leaves input-source selection, output destination, delimiter handling, and overwrite semantics unexplained. It is adequate to identify the tool but not to invoke it confidently.

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

Parameters2/5

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

Schema description coverage is 14% (only path is annotated), so the description must compensate, and it does not. It restates format values already given as enums for to/from but never explains text vs path, out_path, delimiter, or overwrite, leaving five of seven parameters undocumented anywhere.

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 names a specific verb (Convert) and resource (tables) and enumerates the supported formats, so an agent knows exactly what the tool does. It doesn't distinguish itself from siblings like json or markdown, though those are separate tools rather than competing converters.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the format list suggests when the tool applies, but there is no explicit when-to-use, no prerequisite, and no mention of alternatives such as the sibling json or markdown tools. An agent must infer the context from the name and format list.

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