rea-captcha
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| captcha_inspectA | Inspect a configured browser session for an active verification challenge and return evidence plus the handling policy. |
| captcha_completeC | Let the agent complete an authorized provider-test or owned-origin challenge in the existing browser session, then wait for fresh server-validated evidence. |
| captcha_waitB | Poll the same browser session until its verification challenge clears or the bounded timeout expires. |
| captcha_handoffC | Bind the current challenge to a caller-owned task and create a generation-scoped human handoff in the existing browser session. |
| captcha_resumeA | Consume the matching task-scoped handoff once, re-inspect the existing browser session, and resume only after the current challenge is clear. |
| captcha_analyzeB | Analyze URL, title, HTML, text, or runtime signals already available to the calling agent. This read-only tool needs no configured browser adapter and does not control or preserve a browser session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools are clearly distinct: handoff/resume form a clear pair, wait and complete target different outcomes. However, inspect and analyze both diagnose challenges (differing mainly by whether a browser session is used vs agent-supplied data), and complete vs resume could be blurred since both act on an existing session to move past a challenge.
All six tools use a consistent captcha_<verb> snake_case pattern (inspect, analyze, complete, handoff, resume, wait). The convention is predictable and readable throughout.
Six tools is well-scoped for a captcha-handling server, with each tool mapping to a distinct lifecycle stage (inspect, analyze, complete, handoff, resume, wait). No filler or redundant tools.
The surface covers a full challenge lifecycle: detection (inspect/analyze), resolution (complete), escalation (handoff), recovery (resume), and waiting (wait). Minor gaps like no explicit configuration/setup or detection-only tool, but the core end-to-end flow is covered.