Skip to main content
Glama

Plain list to HTML

bpj_markdown_list_html
Read-onlyIdempotent

Escape each nonblank line as HTML text and build a semantic unordered list.

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_list_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine behavioral detail beyond that: only nonblank lines are emitted and each is escaped as text, which tells the agent that blank lines are dropped and that markup characters are neutralized. It still omits whether pre-existing bullet markers are stripped and what the exact output shape/newlines look like.

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?

A single front-loaded sentence with the transformation and the output described in order, no filler, no restatement of the name. Nothing could be removed without losing meaning.

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 one-parameter pure transform with safety fully covered by annotations, the description covers what goes in and roughly what comes out. However, with no output schema it never states the return form (HTML fragment string? wrapped in <ul>?) and leaves the 6000-char bound undisclosed, so an agent lacks a couple of details needed to call it confidently.

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?

There is one parameter with 0% schema description coverage; the schema only supplies a title ('Source text') and a 6000-char cap. 'Escape each nonblank line' does imply line-delimited input semantics, which is real added meaning, but the description never mentions the length limit or clarifies whether lines should be plain prose or may carry markdown prefixes.

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 concrete verb pair (escape, build) and a concrete artifact (semantic unordered list) over the input lines, which is far more specific than the title 'Plain list to HTML'. It distinguishes itself from siblings like bpj_html_list_structure or bpj_markdown_bullets_to_checklist by making clear it is a one-way plain-text-to-<ul> conversion, though it never explicitly contrasts with them.

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 intended use is implied by the transform itself: feed line-delimited plain text, get an HTML list. There is no explicit statement of when to choose this over a sibling converter, no prerequisites, and no note on what input is unsuitable (e.g. already-markdown bullet lists).

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.