Skip to main content
Glama

dev_tools_regex_test

[$x402 pago por llamada] Prueba un patrón regex contra un texto y devuelve todas las coincidencias.

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

Input Schema

NameRequiredDescriptionDefault
textYes
patternYesSintaxis regex del crate Rust `regex` (similar a RE2/PCRE, sin backreferences ni lookaround).
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the x402 pay-per-call behavior and that all matches are returned, which is useful. However it says nothing about regex engine limits (left to the schema), match-count limits, timeouts, or error behavior on invalid patterns.

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 functional sentence plus a short payment tag; nothing is wasted. The payment tag leads the description, which slightly delays the actual purpose, keeping it just short of a 5.

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

Completeness3/5

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

For a 3-parameter tool with no output schema and no annotations, the description is only just adequate. It mentions returning all matches but gives no sense of the result shape (match strings, positions, count) and leaves the payment handshake entirely to the schema.

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 67%: 'pattern' and 'x_payment' both have solid descriptions, including the Rust regex crate restrictions and the 402 fallback flow. The description itself adds no parameter-level meaning beyond the schema, so the 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?

Uses a specific verb and resource ('Prueba un patrón regex contra un texto') and states the output ('devuelve todas las coincidencias'). Within the dev_tools family this is unambiguously the regex-testing utility, though it never names or differentiates itself from any sibling explicitly.

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?

There is no guidance on when to use this versus alternatives, nor any preconditions beyond the bracketed payment note. The agent must infer the use case entirely from the tool name and the one-line statement of function.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources