Skip to main content
Glama

Bullets to Markdown checklist

bpj_markdown_bullets_to_checklist
Read-onlyIdempotent

Add unchecked boxes to unordered list items while preserving existing checkbox states.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: existing checkbox states are preserved rather than reset. It does not disclose what happens to ordered lists, nested items, or items already unchecked, which for a text transform is the remaining meaningful gap.

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 sentence with zero filler, and the core action is front-loaded before the preserving-behavior qualifier. Nothing could be cut 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 simple, single-parameter, non-destructive transform with rich annotations and no output schema, the description covers the essentials. It leaves out the output shape (`- [ ]` prefixing) and edge-case handling for ordered or nested lists, which an agent would otherwise have to guess at.

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?

Only one parameter exists and schema description coverage is 0% — the schema gives just 'Source text' and a 6000-char limit. The description implicitly characterizes that text as markdown containing unordered list items, which is real added meaning, but it offers no detail on accepted bullet syntax ('-', '*', '+') or formatting constraints.

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+resource ('Add unchecked boxes to unordered list items') plus a scope qualifier ('preserving existing checkbox states'), so an agent can immediately tell this is a markdown list-to-task-list transform rather than a generic conversion. It does not explicitly contrast itself with the many sibling markdown tools, which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of alternatives such as bpj_markdown_list_html or bpj_claim_evidence_checklist, and no stated precondition (e.g. input must be markdown containing '-' or '*' list items). The agent must infer applicability from the tool name alone.

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.