Skip to main content
Glama

Renumber Markdown ordered runs

bpj_markdown_ordered_renumber
Read-onlyIdempotent

Renumber adjacent ordered list items at the same indentation starting at one.

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

Input Schema

NameRequiredDescriptionDefault
textYes

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the meaningful behavioral detail that numbering restarts at one and applies only to adjacent same-indentation runs, but it omits what happens to non-adjacent items, alternate delimiters like `)`, or items with intentionally non-sequential starts.

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 scope qualifier is placed after the verb. It is efficient, though its brevity leaves no room for the clarifications noted above.

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 single-string transformation with no output schema, the definition is close to adequate, but it never states that the returned value is the rewritten document, nor how existing numbers or mixed delimiters are handled. Given annotations cover the safety profile, the remaining gap is mainly about return behavior.

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?

One parameter (`text`) with 0% schema description coverage; the description says nothing about it. The meaning is largely self-evident from the name "Source text" and the string type with maxLength 6000, but the description fails to clarify whether the input is an entire document or just the list region.

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?

Uses a specific verb ("Renumber") plus a precise resource and scope ("adjacent ordered list items at the same indentation starting at one"). An agent can distinguish it from other markdown siblings such as bpj_markdown_bullets_to_checklist, though no sibling is named explicitly.

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 explicit when-to-use or when-not-to-use guidance, and no mention of alternatives (e.g. bullet-to-checklist conversion or heading renumbering tools). Scope is only inferable from the purpose sentence itself, and edge cases like nested lists or non-`1.` starting numbers are unaddressed.

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.