Skip to main content
Glama

Export fenced code blocks

bpj_markdown_code_block_export
Read-onlyIdempotent

Extract the source and info string of each fenced code block in document order.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description contributes useful behavior beyond that by specifying exactly which two fields are captured per block and that results follow document order. It is silent on edge cases an extractor must resolve — unclosed fences, nested fences, and what is returned when no blocks exist.

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 verb and the extracted fields, ending with the ordering guarantee. No filler, no restatement of the tool name.

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 extractor the scope statement is nearly sufficient, and the lack of an output schema is partly offset by naming the two extracted fields. However, with no output schema and 0% parameter coverage, the description should have said what the returned collection looks like and how the input size limit affects behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description is expected to compensate for the single 'text' parameter, but it never mentions the input at all. The 6000-character maxLength is a real constraint an agent must plan around (chunking, truncation) and nothing in the prose flags it.

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 and resource ('Extract the source and info string of each fenced code block') and adds the ordering guarantee 'in document order', so the agent knows exactly what is produced. It does not distinguish itself from near-identical siblings such as bpj_markdown_fence_coverage or bpj_markdown_fence_language_mix, which keeps it short of 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 statement, no exclusion, and no named alternative, even though the sibling list contains several other fence-related tools an agent could reasonably confuse this with. The purpose is inferable from the description, but routing must be guessed.

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.