Markdown: tables
Category: markdown
Renders GFM pipe-tables. Some clients don't render, and terminal clients render them poorly in narrow columns.
Support by client
| Client | Status | Notes | Verified |
|---|---|---|---|
| supported | Full GFM table rendered inline: 'Here is a GFM pipe-table:' followed by a table with Client/Category/MCP status columns and rows Claude Web/ChatGPT Web/Ollama. Call id: c37451. | 2026-07-05T15:52:27.858Z | |
| supported | The assistant response renders a formatted table with column headers, alignment, and horizontal rules — not raw pipe-delimited markdown text. | 2026-07-08T15:05:03.048Z | |
| supported | Rendered as an actual table with aligned columns and bold header row, no literal pipes. call id 1abd8c. Automated via Mirroir. | 2026-07-09T14:29:48.112Z | |
| unknown | — | ||
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. | 2026-07-08T19:15:58.368Z | |
| supported | GFM pipe-table rendered as an actual table with three columns (Client, Category, MCP support) and three rows (Claude Web, ChatGPT Web, Ollama) in the assistant reply. Call id: 37505c. | 2026-07-05T15:24:51.842Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | Tool was called but the model did not echo the probe's call-id; can't infer rendering. Prefer vision-tier for a definitive answer. | 2026-07-02T17:49:25.101Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. | 2026-07-08T15:42:32.868Z | |
| unknown | — | ||
| unknown | — | ||
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. | 2026-07-04T14:44:56.828Z | |
| unknown | — | ||
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. | 2026-07-04T14:55:17.814Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| unknown | — | ||
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. (tool_use event and debug log both missed; inferred toolCalled from call-id echo) | 2026-07-02T18:10:01.759Z | |
| unknown | — | ||
| unknown | — | ||
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. | 2026-07-04T14:53:05.949Z | |
| partial | Tool was called and the model echoed the probe's call-id — but behavioral can't tell whether the client actually rendered the markdown variant (table/code/math/diagram/image/task/URL) vs. surfaced the source. Prefer vision-tier for a definitive answer. | 2026-07-04T15:27:14.797Z | |
| unknown | — | ||
| unknown | — | ||
| unknown | — |