Skip to main content
Glama

Split Markdown front matter

bpj_markdown_frontmatter_split
Read-onlyIdempotent

Separate raw front matter enclosed by leading triple-dash lines from the remaining body.

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

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 this read-only, idempotent and non-destructive, so the safety profile is covered. The description adds the useful constraint that only *leading* triple-dash blocks count, but says nothing about behavior when no front matter is present or whether the delimiters are included in the returned matter.

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?

One front-loaded sentence with no filler, and the discriminating detail ('enclosed by leading triple-dash lines') comes before the consequence. It is efficient, though the brevity contributes to the gaps elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity tool the bar is modest, but with no output schema the description should state what comes back (two parts? a list? null when absent?) and what happens on input without front matter. Neither is addressed, leaving the caller unable to predict the result.

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?

With a single parameter and 0% schema description coverage, the schema only offers the title 'Source text' and a 6000-character cap. The description implies the input is markdown text containing front matter, but adds no format, encoding, or edge-case meaning beyond that.

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 specific verb ('Separate') and resource ('raw front matter ... from the remaining body'), and the 'leading triple-dash lines' detail pins down exactly which front matter is meant. It does not explicitly distinguish itself from nearby markdown tools such as section or fence utilities, so it stops 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 framing, no stated preconditions (e.g. text must begin with '---'), and no mention of alternatives. The agent must infer from the name and the sentence alone that this is the tool for pulling front matter out of a markdown string.

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.