Skip to main content
Glama
Sign In

RegexForge

by io.github.walkojas-boop
OverviewDiscussionsAdmin

regexforge_synth

Synthesize a battle-tested regex from labeled examples. Input: optional natural-language description + 20 examples (10 positive, 10 negative, or any mix of ≥4). Output: regex + flags + test matrix proving every example is handled correctly + backtracking-risk analysis. Deterministic; no LLM at serve time.

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": {
      "examples": "<examples>"
    },
    "name": "regexforge_synth"
  }
}

Input Schema

NameRequiredDescriptionDefault
examplesYes
descriptionNoOptional natural-language description, used only for tie-breaking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden of disclosing behavior. It states determinism, no-LLM-at-serve-time, and the guaranteed test matrix with backtracking-risk analysis. It does not cover failure modes or edge cases, but the provided behavioral traits are sufficient for usage understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core purpose, then covering inputs, outputs, and behavioral guarantees. Every sentence contributes value with no redundancy.

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

Completeness5/5

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

Despite no output schema, the description enumerates all output components (regex, flags, test matrix, backtracking analysis). It also covers input constraints and core behavioral characteristics, making it complete for an agent to decide on and invoke the tool.

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?

Schema coverage is 50%; the description compensates by detailing that the description parameter is optional and used for tie-breaking, and by explaining example mix constraints (10 positive/10 negative or ≥4 total). This adds meaning beyond the schema's simple field definitions.

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 opens with a specific verb and resource: 'Synthesize a battle-tested regex from labeled examples.' It clearly states the tool's function and distinguishes it from generic regex tooling by emphasizing the synthesis from examples, plus its deterministic nature.

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

Usage Guidelines4/5

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

The description provides explicit input requirements (optional description + 20 examples, or any mix ≥4) and output expectations (regex, flags, test matrix, backtracking analysis). It also gives behavioral guidance ('Deterministic; no LLM at serve time'). However, it does not explicitly contrast with alternatives since no sibling tools are present.

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

All RegexForge toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources