Skip to main content
Glama
Sign In
TextToolkit

TextToolkit

by Cicatriiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

regex_test

Test a regex pattern against provided text to find matches.

Instructions

Test a regex pattern against text

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>"
    },
    "name": "regex_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to test against the pattern
patternYesThe regex pattern to test
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?

No annotations provided, and the description does not disclose what the tool returns (e.g., boolean, matched text, capture groups). It lacks behavioral details beyond the basic action.

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 concise sentence, efficient and to the point. Could benefit from additional structure (e.g., return type), but remains clear and readable.

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?

With no output schema, the description should explain the return value (e.g., boolean match). It also fails to differentiate from sibling regex tools in terms of output, leaving agents uncertain.

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%, and the description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the schema already documents the parameters.

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 'Test a regex pattern against text' clearly states the verb 'Test' and the resource, distinguishing it from sibling tools like regex_extract and regex_replace which perform different operations.

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 (e.g., regex_extract, regex_replace). The description does not mention use cases or exclusions.

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