Skip to main content
Glama

Solve MTCaptcha

capskip_solve_mtcaptcha

Solve an MTCaptcha widget with its sitekey and page URL to obtain the v1( token, then place that token in the form's hidden mtcaptcha-verifiedtoken field before submitting.

Instructions

Solve an MTCaptcha text captcha — a widget configured by a mtcaptchaConfig object, or an iframe from service.mtcaptcha.com — and get its token. Requires sitekey (starts with 'MTPublic-') and url; pass action too when mtcaptchaConfig sets one. You do not need to read or type the characters in the picture. Put the returned token, which starts with v1(, in the form's hidden mtcaptcha-verifiedtoken field, then submit the form.

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": {
      "sitekey": "<sitekey>",
      "url": "<url>"
    },
    "name": "capskip_solve_mtcaptcha"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL of the page the captcha appears on, including scheme.
proxyNoSolve from this network. Every solve requests fresh challenges from MTCaptcha's service, so many solves from one address are what its rate limits catch.
actionNoThe action value the page sets in its mtcaptchaConfig object, such as 'login'. Leave it out when the page sets none.
sitekeyYesThe MTCaptcha sitekey, which starts with 'MTPublic-' (for example 'MTPublic-KzqLY1cKH'). Read it from the sitekey of the mtcaptchaConfig object in the page source, or from the sitekey= parameter in the address of the widget iframe on service.mtcaptcha.com. Copy it exactly.
timeoutNoSeconds to wait before giving up. Maximum 600.
userAgentNoThe User-Agent to present to MTCaptcha. Usually leave it out.

Output Schema

NameRequiredDescriptionDefault
codeYes
tokenYes
captchaIdYes
solveSecondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.1

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, and destructiveHint=false. The description adds useful behavioral context beyond that: the user does not need to read the image characters, the returned token starts with v1(, and the token belongs in the hidden mtcaptcha-verifiedtoken field before form submission. It does not mention rate limits, though those are covered in the proxy parameter description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: it first states what the tool does, then the requirements, then the token workflow. Every sentence carries operational value, especially the clarification that the agent need not read the captcha characters.

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

Completeness5/5

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

Given the tool's complexity, annotations, rich input schema, and output schema, the description is complete enough to invoke correctly. It covers the required inputs, conditional action usage, token format, and post-solve workflow without needing to restate the schema's optional parameter details.

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?

Schema description coverage is 100%, so the schema already documents all six parameters, including sitekey format, action conditions, proxy behavior, timeout, and userAgent. The description reinforces the required sitekey/url and conditional action usage but does not add materially new meaning beyond the schema.

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 states a specific verb and resource: solve an MTCaptcha text captcha. It further disambiguates the two supported widget forms (mtcaptchaConfig object or service.mtcaptcha.com iframe) and states that the output is a token, so the agent can distinguish this tool from the other capskip_solve_* siblings.

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

Usage Guidelines4/5

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

The description clearly establishes the context in which this tool applies and states the required inputs (sitekey and url), plus the conditional action parameter. It does not explicitly name alternative tools or state when not to use this one, but the MTCaptcha-specific scope makes the intended usage clear.

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