Skip to main content
Glama

Wrap an inline code span

bpj_markdown_inline_code_wrapper
Read-onlyIdempotent

Select delimiters longer than any backtick run and pad a Markdown code span where needed.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, closed-world, non-destructive behavior, so safety is covered. The description adds useful algorithmic context — delimiter length chosen to exceed any backtick run and padding added where needed — but it omits the return shape and what 'padding' means concretely (leading/trailing spaces around backtick-adjacent content).

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?

It is a single tight sentence with no filler, and the delimiter-selection detail is front-loaded. It is perhaps too terse rather than bloated, but every word earns its place.

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 simple one-parameter transformation with no output schema, the description should at least state the input-to-output contract (source text in, wrapped inline code span out). It covers the delimiter nuance but omits the basic framing and any output expectations, so an agent cannot be fully confident about what it will receive.

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% and the single parameter 'text' is never explained in the description. The phrase 'any backtick run' hints that the input contains backticks, but it does not state that 'text' is the raw source content to be wrapped, leaving the parameter meaning to inference.

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 the specific operation: selecting longer delimiters and padding a Markdown code span, which is precise for the tricky part of the task. It does not explicitly frame the transformation as 'take source text and return a wrapped inline code span,' and it never names a sibling (e.g., escape_inline or safe_fenced_snippet) to distinguish scope, leaving some inference to the reader.

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 guidance, no when-not-to-use conditions, and no mention of alternatives such as bpj_markdown_escape_inline or bpj_markdown_safe_fenced_snippet. The agent must infer that this tool is for inline code spans rather than escaping or fenced blocks.

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.