Skip to main content
Glama

Markdown pipe table widths

bpj_markdown_simple_table_width
Read-onlyIdempotent

Check column counts in outer-pipe table rows, respecting backslash-escaped pipes.

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": {
      "text": "<text>"
    },
    "name": "bpj_markdown_simple_table_width"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral detail beyond that: only outer-pipe rows are examined and backslash-escaped pipes are honored during splitting. What remains undisclosed is what the tool actually emits (counts, offending row positions, pass/fail) and whether the 6000-character cap is silent truncation, which matters for a checker with no output schema.

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?

One sentence, front-loaded with the action and object, with the escaped-pipe qualifier placed where it is needed. No filler or restatement of the title.

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?

For a simple read-only single-parameter checker this is close to adequate, and annotations cover the safety side. However, with no output schema the description should say what the result looks like, since an agent cannot otherwise predict whether it receives a count, a list of malformed rows, or a boolean.

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?

With a single parameter and 0% schema description coverage, the description carries the burden and does supply meaning: the 'text' input should be markdown containing outer-pipe table rows, and escaped pipes are significant. It stops short of saying whether a full document or only a fragment is expected, but that is minor for a one-string tool.

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?

States a specific verb and resource: 'Check column counts in outer-pipe table rows', which tells an agent exactly what is validated and what scope of input is considered (outer-pipe tables). It does not name any sibling checker, and the 'width' in the tool name is never reconciled with 'column counts', leaving a small ambiguity about whether it measures widths or counts columns.

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?

Usage is only implied: an agent can infer this is a markdown table validation check, but there is no explicit statement of when to call it versus alternatives such as bpj_csv_to_markdown_table or the other markdown lint tools, and no preconditions or exclusions are given.

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.