Skip to main content
Glama

Tools for Agents

by io.github.max124vip-dev
OverviewDiscussionsAdmin

regex_extract

Regex capture groups from text

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesInput text
groupNo
patternYesRegular expression
max_matchesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / args
      Removed value: -{
-  "description": "Tool arguments",
-  "properties": {
-    "text": {
-      "description": "Primary input text",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / group
      Added value: +{
+  "default": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / max_matches
      Added value: +{
+  "default": 50,
+  "type": "integer"
+}
    • addedInput schema / properties / pattern
      Added value: +{
+  "description": "Regular expression",
+  "type": "string"
+}
    • addedInput schema / properties / text
      Added value: +{
+  "description": "Input text",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "text",
+  "pattern"
+]
  2. Added

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not explain behavior for no matches, the meaning of group 0, how multiple matches are returned, or any error handling. 'Regex capture groups from text' only states the core operation without adding behavioral context.

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

Conciseness3/5

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

The description is extremely short and front-loaded, but it is more of a fragment than a fully formed sentence. While simplicity is good, it sacrifices crucial detail needed for a tool with multiple parameters and no annotations.

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 there is no output schema, no annotations, and a four-parameter input schema with incomplete parameter descriptions, the tool description is insufficient. It does not explain return format, the role of each parameter, or any constraints/behaviors, leaving the agent under-informed.

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

Parameters2/5

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

Schema coverage is 50%, with only text and pattern having descriptions. The description adds no additional meaning for the 'group' and 'max_matches' parameters, which remain ambiguous. It does not explain that group 0 typically means the full match or how max_matches limits results.

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

Purpose3/5

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

The description 'Regex capture groups from text' indicates the tool applies a regex and returns capture groups, but it lacks a clear verb and is more of a noun phrase. It does not explicitly distinguish itself from specialized extraction tools like extract_links or extract_phones, though the generic regex nature is somewhat apparent.

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 is provided on when to use this tool versus alternatives. The description does not mention use cases, what types of patterns are supported, or how it differs from sibling extraction tools.

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

All Tools for Agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources