Skip to main content
Glama
Sign In

DrUrls

by com.drurls
OverviewDiscussionsAdmin

hire_tester

Places an order for one test from the tester catalogue. A person performs it and returns a recorded walkthrough with a screenshot and the console output of every step, plus their written findings. It suits a specific doubt only a person can resolve; a brief that says what is suspected produces a sharper report. Charges the offer's price at purchase and releases it if no tester accepts within 72 hours. offer_id identifies an offer in the tester catalogue. Cost: set by the offer you choose — the tester catalogue states each offer's price in credits, its turnaround, and exactly what is delivered. Charged when the order is placed and released if no tester accepts within 72 hours, or if the tester who accepted misses the offer's turnaround. Rate limit: 100 requests/minute per API key.

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": {
      "offer_id": "<offer_id>",
      "target_url": "<target_url>",
      "brief": "<brief>"
    },
    "name": "hire_tester"
  }
}

Input Schema

NameRequiredDescriptionDefault
briefYesWhat to test and what would count as a problem. At least 20 characters. Example: 'Check the mobile checkout on iPhone — I think the pay button falls below the fold.'
offer_idYesThe offer's id, as listed in the tester catalogue
target_urlYesAbsolute http(s) URL of the page to test

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / offer_id / description
      Previous value: -"The offer's id, from list_tester_offers"New value: +"The offer's id, as listed in the tester catalogue"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the billing model (charged at order placement, released if no tester accepts within 72 hours or if the accepted tester misses turnaround) and an explicit rate limit of 100 requests/minute per API key. The openWorldHint is given concrete meaning by describing that a person performs the work and returns evidence.

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

Conciseness3/5

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

The pricing/timing rule is stated twice — 'Charges the offer's price at purchase and releases it if no tester accepts within 72 hours' then again as 'Charged when the order is placed and released if...'. The cost paragraph also restates the catalogue's role redundantly. Front-loading is good, but several sentences could be merged or cut.

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 three-parameter ordering tool with no output schema, it covers cost, delivery timing, release conditions, deliverables, and rate limits — essentially everything needed before calling. It doesn't say how or where the report arrives once completed, which is the one operational 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?

With 100% schema coverage the baseline is 3, but the description adds real signal: 'a brief that says what is suspected produces a sharper report' tells the agent how to write the brief, not just its length limit. offer_id is also anchored to the tester catalogue, tying it to the list_tester_offers sibling.

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?

States a specific verb and resource — 'Places an order for one test from the tester catalogue' — and immediately defines what is delivered (recorded walkthrough, screenshot, console output, written findings). That scope separates it cleanly from siblings like list_tester_offers (browsing) and free_page_check/start_scan (automated checks).

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?

'It suits a specific doubt only a person can resolve' plus the advice to state what is suspected gives a clear selection context. It stops short of naming the automated siblings (free_page_check, start_scan) as explicit alternatives for cases that don't need a human, so the routing is implied rather than spelled out.

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

All DrUrls toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources