Riddle MCP Server

riddle_get_job

Check job status and retrieve artifacts from Riddle browser automation tasks using a job ID.

Instructions

Get status and artifacts of a Riddle job

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": {
      "job_id": "<job_id>"
    },
    "name": "riddle_get_job"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes	Job ID to check

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves 'status and artifacts,' implying a read-only operation, but doesn't specify if it requires authentication, has rate limits, or details the format of returned data. This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence that directly states the tool's function without any unnecessary words. It's front-loaded and appropriately sized, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'status and artifacts' entail, such as possible states or artifact types, nor does it cover error handling or prerequisites. For a tool with no structured behavioral data, this leaves too many gaps for effective use.

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?

The input schema has 100% description coverage, with the 'job_id' parameter clearly documented. The description doesn't add any extra meaning beyond the schema, such as explaining what a 'Riddle job' is or how to obtain the ID, so it meets the baseline score without enhancing parameter understanding.

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?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('status and artifacts of a Riddle job'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'riddle_automate' or 'riddle_run_script', which might also involve job-related operations, so it misses the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing a job ID from another tool, or clarify its role among siblings like 'riddle_batch_screenshot' or 'riddle_click_and_screenshot', leaving the agent without usage context.

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

Deploy Server