Skip to main content
Glama

get_supported_tasks

Lists reviewed CAPTCHA task types and points to additional mentions in the official guide so users can identify supported solving workflows.

Instructions

List reviewed task types and discover additional mentions in the official guide.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_supported_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure and does not meet it. It doesn't say what "reviewed" means (curated? approved?), where the "official guide" mentions come from, whether results are cached, or whether discovery extends beyond the reviewed set. Only the output schema partially covers the return shape.

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 sentence with no filler, and the core action (listing task types) is front-loaded ahead of the secondary discovery clause. The brevity is appropriate for a no-argument read tool, though the second clause could have been spent on disambiguation instead.

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?

With an output schema present, return values needn't be explained, and the zero-parameter surface keeps complexity low. However, an agent still cannot tell from this definition how the tool differs from list_task_types or what the "additional mentions" output actually represents, leaving a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to add. Baseline 4 applies; nothing is missing on this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb "List" and the resource "reviewed task types" are identifiable, but the second clause ("discover additional mentions in the official guide") is vague and blurs whether this returns a catalog, documentation excerpts, or both. Sibling tools named list_task_types and refresh_task_catalog suggest closely related resources, and the description does nothing to distinguish this tool from them.

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 statement of when to call this tool versus list_task_types, get_task_schema, or refresh_task_catalog, and no prerequisite or exclusion is given. An agent must infer the choice from the description alone, which is not enough.

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