Skip to main content
Glama

Fenced code language mix

bpj_markdown_fence_language_mix
Read-onlyIdempotent

Count fenced blocks by the first word of the info string, including unlabelled blocks.

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

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuine behavioral rule — only the first word of the info string is used, and unlabelled blocks are counted too — but says nothing about the shape of the returned counts or how unlabelled blocks are keyed.

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 counting rule and the edge case are both stated compactly. It is perhaps too terse given the missing return-shape detail, but nothing is wasted.

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, non-destructive counting tool with annotations and no output schema, the definition covers purpose and one edge case. It is incomplete on the two things an agent still needs: the return format (map of language to count) and how unlabelled blocks appear in the result.

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?

With schema description coverage at 0% and a single parameter ('text', maxLength 6000), the description carries the burden and says nothing about it. It never states that 'text' is the Markdown source, nor what happens for input exceeding 6000 characters, so the agent learns nothing beyond the schema's type and title.

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 gives a specific verb and resource ('count fenced blocks') plus the exact grouping key ('first word of the info string'), which is precise enough to distinguish it from coverage-style siblings. It stops short of naming a sibling or stating what makes this different from bpj_markdown_fence_coverage.

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, and no alternative is mentioned. The agent can infer the tool reports a language distribution, but nothing tells it why to pick this over the related fence tools.

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.