Skip to main content
Glama

markdowntable_convert

Read-onlyIdempotent

Convert CSV or TSV text into a Markdown table with configurable delimiter and header options, making tabular data ready for Markdown documents and automated workflows.

Instructions

Convert CSV or TSV text into a Markdown table.

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": {
      "input": "<input>"
    },
    "name": "markdowntable_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesCSV or TSV text.
delimiterNo',' (default) or 'tab'.
has_headerNoFirst row is header (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds no behavior beyond the transformation itself — nothing about how malformed rows or ragged column counts are handled. For a pure text transform this is acceptable but not enriching.

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?

One sentence, front-loaded with the verb and both source and target formats. Nothing superfluous.

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 three-parameter, single-purpose converter with a fully documented schema, the description states input and output formats, which is the key missing piece given there is no output schema. It stops short of covering edge-case behavior (ragged rows, quoting), which is a minor gap.

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 input, delimiter and has_header are all documented in the schema. The description adds nothing about accepted delimiter values or header handling, so the baseline 3 applies.

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?

Specific verb ('Convert') plus explicit source formats (CSV or TSV) and target format (Markdown table). An agent can tell what goes in and what comes out. It does not explicitly differentiate itself from nearby siblings such as csv_parse or markdown_to_html, which keeps it at 4.

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

Usage Guidelines2/5

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

There is no statement of when to use this instead of alternatives — notably csv_parse (CSV to structured data) or markdown_to_html (the opposite direction). Usage is only inferable from the purpose sentence itself.

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

Deploy Server

Other Tools