ScorpTech x402 API

Markdown Table

markdown_table

Read-onlyIdempotent

Build or parse Markdown (GitHub-flavoured) tables. Build: from an array of objects, an array of arrays or CSV, with column selection / order / renaming, alignment (numeric columns right-aligned automatically), pipe / newline escaping, cell truncation and padding that respects wide CJK / emoji characters; also returns an HTML table. Parse: extract every table from Markdown into headers, alignment and typed rows (JSON). Price: $0.001 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/markdown-table

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "markdown_table"
  }
}

Input Schema

Name	Required	Description
`data`	No	Rows: array of objects, array of arrays (first row = header unless headers given) or a CSV string
`align`	No	Per-column alignment (default auto)
`pretty`	No	Pad columns to equal width
`columns`	No	Columns to include, in order
`headers`	No	Header labels (rename / for header-less arrays)
`numbers`	No	Parse mode: convert numeric cells
`markdown`	No	Parse mode: Markdown containing tables
`maxWidth`	No	Truncate cells wider than this

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing cost ($0.001 USDC per successful call via x402 on Solana) and an HTTPS endpoint, plus return behavior (also emits an HTML table; parse returns headers, alignment and typed rows as JSON). Annotations already cover the read-only/idempotent profile, and the description adds the commercial/auth context.

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-loads the build/parse split and packs many useful specifics into compact clauses. Dense but nearly every clause carries information; the trailing pricing/endpoint sentence is slightly tacked on but still relevant.

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?

With no output schema, the description still covers return values (HTML table, parsed headers/alignment/typed rows). Modes, cost, and endpoint are all present, so an agent has enough to call it correctly.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real semantics: numeric columns auto right-align, escaping of pipes/newlines, CJK/emoji-aware padding, and typed row conversion in parse mode. It doesn't map these details to specific parameter names, keeping it at 4.

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 specific verbs (build, parse) and resource (Markdown/GitHub-flavoured tables), enumerating concrete capabilities like column reordering, alignment, escaping and truncation. Clearly distinguishes itself from nearby siblings such as html_tables, markdown_to_html and csv_profile.

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?

Splits usage into 'Build:' and 'Parse:' modes with the input source for each, which is clear context for choosing a path. It stops short of explicitly naming alternatives (e.g. markdown_to_html) or stating when not to use it, so not a 5.

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

All ScorpTech x402 API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?