Skip to main content
Glama

Fence a source excerpt

bpj_markdown_safe_fenced_snippet
Read-onlyIdempotent

Choose a fence longer than every backtick run in the source and attach a language label.

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>",
      "language": "<language>"
    },
    "name": "bpj_markdown_safe_fenced_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
languageYes

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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: the fence is chosen adaptively to exceed any backtick run in the source, which explains why the result is safe. It omits what is actually returned (a wrapped block? a fence string only?) and how the content is placed relative to the label.

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; the core selection rule comes first. It is efficient, though it is terse enough that the useful adaptive-fence detail sits in the same breath as the label instruction, leaving no room for scope or output details.

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 two-parameter read-only utility with no output schema, the definition covers the core behavior adequately. It still leaves an agent guessing about the return shape and edge cases (source with no backticks, fence minimums), which matters since nothing else documents the output.

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 description coverage is 0%, so the description must carry meaning, and it does map the two concepts loosely: 'source' corresponds to text and 'language label' to language. However, it adds no constraint or format detail such as length limits, whether the label may be empty, or how the label is emitted, so it only partially compensates for the empty schema documentation.

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 operation: select a fence longer than every backtick run in the source and attach a language label to the source text. This is a concrete verb-plus-resource description that lets an agent distinguish it from sibling markdown utilities that analyze fences (coverage, language mix) rather than produce one. It falls short of 5 because it never names an alternative or explicitly contrasts itself with adjacent export/wrapper tools.

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?

The sentence describes the algorithm (pick a longer fence, attach a label) but gives no guidance on when to call this tool versus alternatives such as the inline code wrapper or code block export. No preconditions, no when-not-to-use, no mention of what input suitability looks like.

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.