Skip to main content
Glama

Markdown blockquote export

bpj_markdown_blockquote_export
Read-onlyIdempotent

Collect adjacent explicitly marked blockquote lines and remove one quote prefix.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real behavioral content: only adjacent lines are grouped, and exactly one prefix level is removed (a nested '>>' concern). However, with no output schema the description never states what is returned — a single string, a list of grouped quotes, or a transformed document — which is a meaningful gap for a transformation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, so every word earns its place. It is efficient but so terse that the operational core (the one-prefix-removal rule) is buried mid-sentence rather than stated as the primary effect.

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 text transformer with no output schema, the definition should at minimum describe the return shape and how adjacent blocks are delimited in the result. Those are absent, leaving the agent with a correct but incomplete mental model of the call.

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 0% for the single 'text' parameter, so the description must carry the load and only partially does: it implies the input is text containing marked blockquote lines but never names the parameter, the 6000-character cap, or line-terminator expectations. It also leaves 'explicitly marked' undefined (whether '>' without a space, or indented quotes, count), which affects the outcome.

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 names a concrete transformation: gather adjacent explicitly marked blockquote lines and strip one quote prefix. That is a specific verb-plus-resource, not a restatement of the name. It lacks any explicit contrast with siblings such as bpj_markdown_escape_inline or bpj_markdown_cut_section, so it lands at 4 rather than 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 prerequisites, and no routing to an alternative tool. An agent must infer from the name that this is a blockquote-normalization operation and cannot tell from the text whether it applies to a whole document or a fragment.

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.