Skip to main content
Glama

Convert CSV to a Markdown table

bpj_csv_to_markdown_table
Read-onlyIdempotent

Use CSV headers to produce a document-ready 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": {
      "csv": "<csv>"
    },
    "name": "bpj_csv_to_markdown_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds only that headers are used and the output is 'document-ready', which hints at a header row but says nothing about malformed rows, delimiter handling, pipe escaping, or size limits.

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?

One front-loaded sentence with no wasted words. It is arguably too terse rather than padded, so no penalty for verbosity.

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?

This is a simple one-parameter, read-only tool with no output schema, so the bar is low, and the description covers the basic input-to-output mapping. Gaps remain around edge-case input handling (ragged rows, embedded pipes, max length) that an agent would need to call it reliably.

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 0% for the single required 'csv' parameter, so the description must compensate; saying 'Use CSV headers' does confirm that the first row is treated as the header row. It still omits the 12,000-character limit and the expected delimiter/quoting conventions documented nowhere else.

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 says it produces a Markdown table from CSV headers, which identifies the resource (CSV) and output (Markdown table) well enough to act on. It leans on the title for the verb ('Convert') and does nothing to separate it from siblings like bpj_csv_to_json or bpj_filter_csv.

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 rather than bpj_csv_to_json or another CSV sibling, and no prerequisites or exclusions are given. The one-sentence description leaves the agent to infer the use case from the name alone.

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.