Skip to main content
Glama
Sign In
Tools MCP Server

Tools MCP Server

by dongood
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

markdown_format_tables

Formats markdown tables for readability by calculating optimal column widths, aligning cells, and preserving alignment markers (left, center, right).

Instructions

Format markdown tables for human readability. Calculates optimal column widths based on content and aligns all cells. Preserves column alignment markers (left, center, right).

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": {
      "markdown": "<markdown>"
    },
    "name": "markdown_format_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
markdownYesThe markdown content containing tables to format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses key behaviors: calculating optimal column widths, aligning cells, and preserving column alignment markers. However, it omits potential side effects (e.g., whether non-table content is preserved) and does not explicitly state the return value, leaving some transparency gaps.

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?

The description is concise, front-loaded with the primary purpose, and consists of two sentences with no redundant information. Every clause contributes to understanding the tool's behavior.

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?

The description is reasonably complete for a tool with one parameter and no output schema. It explains the transformation logic and a key preservation guarantee, but could be more explicit about the return value and behavior on invalid input. Overall, it provides sufficient context for an AI agent to use the tool 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 coverage is 100% since the single 'markdown' parameter has a description ('The markdown content containing tables to format'). The tool description adds minimal extra meaning beyond the schema, so the baseline score of 3 applies.

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?

The description clearly states the tool formats markdown tables for human readability, specifying the verb 'Format' and the resource 'markdown tables.' It further distinguishes itself from sibling tools (e.g., TOC tools, conversions) by focusing specifically on tables and detailing behaviors like column width calculation and alignment preservation.

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

Usage Guidelines3/5

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

The description implies use when markdown tables need formatting, but it does not explicitly state when to use this tool over siblings like 'markdown_format' or provide exclusions or prerequisites. The context is clear but lacks comparative guidance.

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