obscura-capsolver-tool
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| solve_verification_checkpointC | Handle one explicitly authorized CAPTCHA checkpoint for the current Obscura 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 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clearly defined as solving a CAPTCHA checkpoint.
With a single tool, there is no naming convention to compare against. The name 'solve_verification_checkpoint' is descriptive and follows a clear verb_noun pattern.
A single tool for a CAPTCHA-solving server feels thin. Typical CAPTCHA services might include tools for checking status, listing pending checkpoints, or retrieving results, making this count inadequate for the apparent scope.
The tool surface only covers one action (solving a checkpoint) with no supporting operations like status checks or session management. This leaves notable gaps that could cause agent failures if the CAPTCHA flow requires more than a single solve action.