Skip to main content
Glama

Markdown open action list

bpj_markdown_open_action_list
Read-onlyIdempotent

Collect unchecked Markdown list items with original line numbers and labels.

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

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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new information by stating what comes back (original line numbers and labels), which matters since there is no output schema, but it says nothing about ordering, deduplication, or handling of nested lists.

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 tight sentence with no filler, front-loading the verb and the resource so an agent can act on it immediately.

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 read-only utility the definition is largely sufficient, and it helpfully discloses the shape of the result in the absence of an output schema. It falls short on edge-case behavior (nested lists, checkbox syntax variants, the 6000-character cap) that an agent would need 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 a single required parameter whose schema description coverage is 0%; the schema only provides the title 'Source text' and a 6000-character cap. The description implies the input is Markdown text but adds no format constraints, no note about the length limit, and no clarification of what counts as an unchecked item, so the coverage gap is only partly compensated.

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?

The description uses a specific verb ('Collect') plus a specific resource ('unchecked Markdown list items'), and adds that results carry original line numbers and labels. That distinguishes it from siblings like bpj_markdown_bullets_to_checklist (which converts rather than collects), though 'labels' is left undefined.

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 explicit when-to-use or when-not-to-use guidance and no named alternative, even though the sibling set contains closely related Markdown list tools. The intended use (extracting open action items) is only implied by the word 'unchecked'.

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.