OnlineCyberTools MCP (280+ filterable tools)

text_add_line_numbers

Read-onlyIdempotent

Add sequential line numbers to any text, with options for numbering style, start value, increment, and blank line handling. Ideal for annotating logs, code, or lists.

Instructions

Add Line Numbers. Prefix every line of the supplied text with a sequential number, returning the numbered text plus before/after statistics. Choose simple ("N: line"), zero-padded, or a custom template using {line} and {text} placeholders; control the starting number, increment, pad width, and whether blank lines are skipped (kept verbatim and uncounted). Use this to annotate logs, code, or lists; use text_remove_line_numbers for the inverse. Pure local compute: read-only, non-destructive, offline, and rate-limited (60 requests/min for anonymous callers). Returns the numbered result, the final number reached, and original/result line-word-character counts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Multi-line text to number; split on newline (\n).
`startNumber`	No	First line number. Values below 1 are clamped to 1.
`increment`	No	Amount added per numbered line. Values below 1 are clamped to 1.
`format`	No	Output style. simple and padded emit "<number>: <line>"; padded zero-pads the number; custom uses the customFormat template.	simple
`customFormat`	No	Template used when format is custom; {line} is replaced by the number and {text} by the line content.	{line}: {text}
`padding`	No	Zero-pad width when format is padded; falls back to 3 when 0. Ignored for other formats.
`skipEmptyLines`	No	When true, blank/whitespace-only lines are kept as-is, not numbered, and counted as skipped.

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	Always true on success.
`result`	No	The numbered text.
`stats`	No	Counts for the input and output plus numbering summary.
`options`	No	The effective settings applied after clamping/normalization.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.5.1Jun 3, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties

Added value: +{
+  "customFormat": {
+    "default": "{line}: {text}",
+    "description": "Template used when format is custom; {line} is replaced by the number and {text} by the line content.",
+    "type": "string"
+  },
+  "format": {
+    "default": "simple",
+    "description": "Output style. simple and padded emit \"<number>: <line>\"; padded zero-pads the number; custom uses the customFormat template.",
+    "enum": [
+      "simple",
+      "padded",
+      "custom"
+    ],
+    "type": "string"
+  },
+  "increment": {
+    "default": 1,
+    "description": "Amount added per numbered line. Values below 1 are clamped to 1.",
+    "minimum": 1,
+    "type": "integer"
+  },
+  "padding": {
+    "default": 0,
+    "description": "Zero-pad width when format is padded; falls back to 3 when 0. Ignored for other formats.",
+    "maximum": 20,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "skipEmptyLines": {
+    "default": false,
+    "description": "When true, blank/whitespace-only lines are kept as-is, not numbered, and counted as skipped.",
+    "type": "boolean"
+  },
+  "startNumber": {
+    "default": 1,
+    "description": "First line number. Values below 1 are clamped to 1.",
+    "minimum": 1,
+    "type": "integer"
+  },
+  "text": {
+    "description": "Multi-line text to number; split on newline (\\n).",
+    "type": "string"
+  }
+}

addedInput schema / required
```
Added value: +[
+  "text"
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "options": {
+      "description": "The effective settings applied after clamping/normalization.",
+      "properties": {
+        "customFormat": {
+          "description": "Effective custom template.",
+          "type": "string"
+        },
+        "format": {
+          "description": "Effective format.",
+          "type": "string"
+        },
+        "increment": {
+          "description": "Effective increment.",
+          "type": "integer"
+        },
+        "padding": {
+          "description": "Effective pad width.",
+          "type": "integer"
+        },
+        "skipEmptyLines": {
+          "description": "Effective skip-empty-lines flag.",
+          "type": "boolean"
+        },
+        "startNumber": {
+          "description": "Effective starting number.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "result": {
+      "description": "The numbered text.",
+      "type": "string"
+    },
+    "stats": {
+      "description": "Counts for the input and output plus numbering summary.",
+      "properties": {
+        "numbering": {
+          "properties": {
+            "finalNumber": {
+              "description": "Last number assigned.",
+              "type": "integer"
+            },
+            "format": {
+              "description": "Effective format used.",
+              "type": "string"
+            },
+            "increment": {
+              "description": "Effective increment.",
+              "type": "integer"
+            },
+            "startNumber": {
+              "description": "Effective starting number.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "original": {
+          "properties": {
+            "characters": {
+              "description": "Byte length of the input.",
+              "type": "integer"
+            },
+            "emptyLines": {
+              "description": "Blank/whitespace-only line count of the input.",
+              "type": "integer"
+            },
+            "lines": {
+              "description": "Line count of the input.",
+              "type": "integer"
+            },
+            "words": {
+              "description": "Alphabetic word count of the input.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "result": {
+          "properties": {
+            "characters": {
+              "description": "Byte length of the result.",
+              "type": "integer"
+            },
+            "lines": {
+              "description": "Line count of the result.",
+              "type": "integer"
+            },
+            "numberedLines": {
+              "description": "Number of lines that received a number.",
+              "type": "integer"
+            },
+            "skippedLines": {
+              "description": "Number of blank lines skipped when skipEmptyLines is true.",
+              "type": "integer"
+            },
+            "words": {
+              "description": "Alphabetic word count of the result.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "Always true on success.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, etc. Description adds useful context: pure local compute, offline, rate-limited, and behavior for blank lines. No contradictions.

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?

Description is a single well-structured paragraph of about 4 sentences, front-loaded with main purpose, and efficiently packs details without redundancy.

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

Completeness4/5

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

Covers all key aspects: purpose, usage, parameters, return values (numbered result, final number, counts), and constraints (rate limit, offline). Output schema enriches completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% description coverage. Description adds value by explaining format options (simple, padded, custom) and control over start, increment, pad width, and blank lines.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Add Line Numbers' with specific verb and resource, explains it prefixes lines with sequential numbers, and distinguishes from sibling tool text_remove_line_numbers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this to annotate logs, code, or lists; use text_remove_line_numbers for the inverse.' Also mentions rate limit and pure local compute, guiding when to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server