Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Regex Tester

cc_regex_test
Read-onlyIdempotent

Test regular expression patterns against text or file contents to validate matches, apply flags, and preview optional replacements before using them in code.

Instructions

Testet reguläre Ausdrücke gegen Text oder Dateiinhalt

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": {
      "pattern": "<pattern>"
    },
    "name": "cc_regex_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText to test against (or use file_path)
flagsNoRegex flags (g, i, m, s, u)g
patternYesRegular expression pattern
file_pathNoFile to test against (alternative to text)
replace_withNoOptional replacement string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.27
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.3.8

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds no behavioral context of its own: it never mentions that supplying 'replace_with' turns this into a substitution test, nor that the result is returned rather than written anywhere.

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 short sentence with no filler and the core action front-loaded. It is efficient but borders on under-specified rather than deliberately compact.

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?

Five parameters and no output schema: an agent calling this cannot tell from the description what it gets back (match list, replaced string, counts). For a tool whose whole value is the returned match result, that is a meaningful gap even with annotations covering safety.

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 description coverage is 100%, so the schema fully documents flags, pattern, text, file_path and replace_with. The description only echoes that testing runs against text or file content, adding nothing beyond the structured fields. Baseline 3 applies.

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 names a concrete verb+resource ('Testet reguläre Ausdrücke') and the two input modes it operates on (text or file content). No sibling tool does regex testing, so the function is distinguishable, though it does not explicitly differentiate itself.

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?

It says nothing about when to use this tool versus alternatives, nor about prerequisites. The only guidance is the implicit 'text or file content' choice, which is really parameter-level, not usage-level.

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