Skip to main content
Glama
CapMonsterCloud

capmonster-mcp

Official
by CapMonsterCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create captcha task

create_task

Submit a CAPTCHA solving task to CapMonster Cloud and get a task ID for result polling. Supports inline task or a JSON file for large payloads.

Instructions

Submit a captcha task; returns taskId. Poll with get_task_result.

task must include 'type' and all required fields. Always look up required params at https://docs.capmonster.cloud/docs/captchas/ — do not rely on training data.

For a task holding one or more large base64 blobs (ComplexImageTask with several images, htmlPageBase64 for Cloudflare cf_clearance/wait_room, or any other opaque field/combined payload too big to type safely) pass task_file instead of task: the path to a JSON file, on this machine's filesystem, containing the exact task object. Write that file with a script or a browser-side save (never by hand-typing a long base64 literal into this tool call's own arguments — a single dropped/unclosed quote in a multi-KB string silently merges what should be separate array elements into one, which is why this exists: a 9-image ComplexImageTask sent inline this way became "Image count: 1, but the task supports: 9" even though the array had 9 entries when written). Provide exactly one of task or task_file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNo
task_fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.11

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description takes on the full burden of behavioral disclosure. It explains the return value, the polling flow, and warns against a real failure mode with inline base64. It does not cover auth or rate limits, but the core behavioral traits are well transmitted.

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?

The description is long, but the essential return/poll info is front-loaded, and the detailed example about the 9-image failure earns its place by preventing a subtle but costly mistake. It is verbose but structured and purposeful.

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?

For a tool with two parameters and no output schema, this description covers both input modes, points to external docs for required fields, and explains the follow-up polling. It does not document error cases, but an agent can invoke it correctly without missing critical context.

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

Parameters5/5

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

Schema coverage is 0%, yet the description fully compensates: task must include type and required fields, task_file is a filesystem path to a JSON task object, and exactly one of the two must be provided. This transforms two opaque parameters into clear, usable instructions.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Submit a captcha task; returns taskId. Poll with get_task_result.' This clearly states what the tool does and how it differs from the sibling result-polling tools.

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

Usage Guidelines5/5

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

It explicitly says when to use task_file instead of task, mandates looking up required params in the docs, and requires exactly one of task or task_file. This is actionable when-to guidance, not just a vague hint.

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

Deploy Server

Other Tools