Skip to main content
Glama
Sign In
TextToolkit

TextToolkit

by Cicatriiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

regex_replace

Replace portions of text by matching a regex pattern and substituting with a replacement string, with optional flags.

Instructions

Replace text using a regex pattern

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>",
      "pattern": "<pattern>",
      "replacement": "<replacement>"
    },
    "name": "regex_replace"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to perform replacements on
patternYesThe regex pattern to match
replacementYesThe replacement string
flagsNoRegex flags (e.g., 'g', 'i', 'gi')g

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits like global vs first-match replacement (though default flag 'g' is in schema), behavior on no match, return value format, and potential performance considerations. It does none of these.

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?

The description is a single concise sentence with no wasted words. It could be slightly expanded to include guidance or transparency without losing conciseness.

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?

Given 4 parameters, no output schema, and no annotations, the description is too brief. It lacks information about return values, edge cases (e.g., no match), and usage context, leaving the agent underinformed.

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 coverage is 100% with parameter descriptions. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the action (replace), the resource (text), and the method (regex pattern). It distinguishes from sibling tools like string_replace (non-regex) and regex_extract (extract matches), making it easy to select the correct tool.

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?

No guidance on when to use this tool versus alternatives. For example, it does not mention that for simple string replacements without regex, string_replace might be more appropriate, or that regex_test could be used for validation first.

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

Deploy Server

Other Tools