Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Markdown table from CSV: convert CSV into a GitHub table

csv_to_markdown
Read-only

Convert CSV (comma, semicolon, tab or pipe, detected automatically; quoted fields supported) into a GitHub-flavoured Markdown table, with number columns right-aligned, pipes escaped and line breaks kept as . Up to 100 KB. Use to show spreadsheet data in a README, chat reply, issue or report; for JSON use csv_to_json. Example: csv=tool,price,calls weather,0.01,120 search,0.01,45. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "csv": "<csv>"
    },
    "name": "csv_to_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYesThe CSV text (up to 100 KB)
headerNotrue (default) if the first row holds the column names

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds genuinely new behavior: a 100 KB size cap, delimiter auto-detection, pipe escaping, <br> for line breaks, and right-alignment of numeric columns. It also discloses the billing model (per-call charge, first 25 free, failed calls free), which explains the idempotentHint=false annotation rather than contradicting it. Slightly dense pricing detail keeps it from a 5.

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 transformation and its output characteristics, then routing, then a worked example. The pricing/credits sentence is somewhat promotional but does convey real cost behavior; the inline example is compact and useful.

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

Completeness5/5

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

No output schema exists, and the description fully describes the return shape (GitHub-flavored table, escaped pipes, <br> line breaks, numeric alignment). Size limits, input flexibility, cost, and side-effect freedom round out everything needed to invoke it correctly.

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 both parameters are already documented, and the description's added detail (auto-detected delimiters, quoted fields, size limit) describes the csv payload rather than adding semantics for the header flag. Baseline 3 is appropriate since the schema carries the parameter burden.

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 specific verb+resource pair ("Convert CSV ... into a GitHub-flavoured Markdown table") and immediately enumerates the accepted delimiters and quoting behavior. It explicitly distinguishes itself from the sibling csv_to_json ("for JSON use csv_to_json"), so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

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

Gives concrete usage contexts (README, chat reply, issue, report) and names the alternative tool plus the condition that selects it, i.e. JSON output. This is explicit when-to-use plus a named alternative, not merely implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.