sigtap Agent Tools

regex_test

Regex matches with groups, count and a backtracking-risk heuristic Free check: https://sigtap-outreach-api.sigtap.workers.dev/preview/tools/regex = 200 demo sample, no wallet. Paid call: 402 challenge -> sign -> retry = settled on-chain. ($0.001 USDC on Base, x402)

Input Schema

TableJSON Schema

Name	Required	Description
`text`	Yes	Text to search
`flags`	No	Regex flags (subset of dgimsuy)
`pattern`	Yes	Regular expression

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`matches`	Yes
`pattern`	Yes
`backtracking_risk`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "backtracking_risk": {
+      "type": "object"
+    },
+    "count": {
+      "type": "number"
+    },
+    "matches": {
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pattern": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "pattern",
+    "count",
+    "matches"
+  ],
+  "type": "object"
+}

First observedSep 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and discloses important behaviors: the free demo requires no wallet, the paid call triggers a 402 challenge requiring signature and retry, and settlement occurs on-chain with a specific cost. This is meaningful transparency, though it does not mention details like execution environment or data handling.

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 concise, information-dense sentences with no filler. The first sentence front-loads what the tool does, and the second efficiently packs the free and paid invocation details, cost, and network.

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

Completeness4/5

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

For a simple 3-parameter tool with an output schema, the description covers the key invocation modes and payment flow. It could be more explicit about what exactly triggers the paid call, but the output schema and parameter schema cover the remaining details.

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 all parameters are already documented in the input schema. The description adds no parameter-specific detail beyond what the schema provides, making the baseline of 3 appropriate.

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 states that the tool performs regex matching and returns groups, count, and a backtracking-risk heuristic. It clearly identifies the resource and output, though it lacks an explicit verb like 'test' or 'match' at the start, making it slightly less direct.

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

Usage Guidelines3/5

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

The description gives clear context on the two invocation paths: a free preview URL and a paid on-chain call with a 402 challenge flow. It does not explicitly address when to use this tool versus alternatives or when not to use it, but the free vs paid distinction implies usage guidance.

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

All sigtap Agent Tools tools Inspect

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.