Skip to main content
Glama

get_task_schema

Read-only

Retrieve the required inputs and JSON Schema for a CapSolver CAPTCHA, challenge, or recognition task before submitting it, without creating a paid task.

Instructions

Check the required inputs for a known CapSolver CAPTCHA, challenge or recognition task.

Returns JSON Schema, conditional requirements, examples and documentation caveats. This lookup does not create a paid task.

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": {
      "task_type": "<task_type>"
    },
    "name": "get_task_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description adds real value by stating the call incurs no cost ('does not create a paid task') and by enumerating what the response contains: JSON Schema, conditional requirements, examples, and documentation caveats. The caveats mention is especially useful since it warns that the schema alone may not capture all constraints.

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?

Three short sentences with the action and precondition front-loaded, followed by what is returned and the cost reassurance. No filler, though the return-value sentence partially duplicates what the output schema already communicates.

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

Completeness4/5

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

An output schema exists, so the description did not need to enumerate return fields, and it is complete on cost and side-effect behavior for a read-only lookup. The remaining gap is guidance on sourcing a valid task_type and on how this differs from the similarly named sibling, which matters for a one-required-parameter tool.

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?

There is a single parameter, task_type, with 0% schema description coverage, so the description must carry the meaning. It conveys that the value identifies a CapSolver CAPTCHA/challenge/recognition task, but it does not say where valid values come from (e.g., list_task_types or get_supported_tasks) or the expected format. Partial compensation only.

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?

States a specific verb and resource: it looks up the required inputs for a known CapSolver CAPTCHA/challenge/recognition task. It also implicitly separates itself from creation tools by noting the lookup does not create a paid task. It does not explicitly distinguish itself from the closely named sibling get_task_parameters, which is the only real clarity gap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'known ... task' implies you should already have a task type before calling, and the description clarifies it is a free metadata lookup rather than a task execution. However, it never states when to prefer this over get_task_parameters or where to obtain a valid task_type. Usage is inferable but not spelled out.

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