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_handoffB | Mark the current challenge as awaiting a person in the existing browser session. |
| captcha_resumeB | Re-inspect the existing browser session and resume its agent lifecycle only after the 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
The tools map to distinct captcha-handling lifecycle steps (inspect, complete, wait, handoff, resume, analyze), and descriptions clarify their different outcomes. There is minor overlap between inspect, wait, and resume, since all examine the existing browser session's challenge state, but the intended actions differ enough for an agent to choose correctly.
All tool names follow the same predictable pattern: the captcha_ prefix plus a concise snake_case verb. The convention is applied uniformly with no mixing of styles or casing.
Six tools is well-scoped for a captcha-handling server, with each tool covering a meaningful operation in the lifecycle. There are no redundant or trivial tools that would bloat the surface.
The surface covers the full practical lifecycle: detection via inspect, authorized completion, bounded waiting, human handoff, resumption, and read-only offline analysis. No obvious agent workflow or lifecycle stage appears to be missing.