Skip to main content
Glama
Sign In

RunHarvester

by com.runharvester
OverviewDiscussionsAdmin

data wait request

data_wait_request
Read-onlyIdempotent

Blocks while polling one request of this tenant until it reaches a terminal state (completed, failed, or cancelled), up to wait_ms. Returns {terminal, timed_out, polls, value}, where value is the latest request as data_get_request returns it; when timed_out is true, call again to keep waiting. Use data_get_request for a non-blocking check, data_wait_batch for batches, and data_get_result or data_read_result_content for the output.

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": {
      "id": "<id>"
    },
    "name": "data_wait_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUUID of the request or batch to wait for, as returned when it was created.
wait_msNoMaximum time to block in milliseconds (default 10000, max 30000). If the state is still not terminal when it elapses, the latest value is returned with timed_out=true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"UUID of the request or batch to wait for, as returned when it was created."
    • addedInput schema / properties / wait_ms / description
      Added value: +"Maximum time to block in milliseconds (default 10000, max 30000). If the state is still not terminal when it elapses, the latest value is returned with timed_out=true."
  2. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description still earns credit for disclosing the blocking behavior, the wait_ms bound, and the exact return shape including the timed_out retry pattern, which annotations cannot convey. It stops short of describing polling cadence or what happens if the id does not exist.

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?

Front-loads the blocking behavior and terminal states, then the return shape, then the alternatives. Dense but every clause carries new information; there is no filler or restatement of the tool name.

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?

No output schema exists, and the description compensates by enumerating the return object fields (terminal, timed_out, polls, value) and explaining what value contains. For a two-parameter blocking tool with full annotation coverage, nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the schema already documents id and wait_ms. The description adds meaning beyond the schema by tying wait_ms to the timed_out return flag and the instruction to call again, which is behavior the schema cannot express.

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: blocks while polling one request of this tenant until a terminal state (completed, failed, cancelled). It names the terminal states and the wait bound, which makes it immediately distinguishable from data_get_request and data_wait_batch.

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?

Gives explicit routing: use data_get_request for a non-blocking check, data_wait_batch for batches, and data_get_result or data_read_result_content for the output. It also states the retry condition (when timed_out is true, call again to keep waiting), so nothing about when to use or not use it is left to inference.

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

All RunHarvester 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