Skip to main content
Glama
Datris MCP Server

Datris MCP Server

wait_seconds

Pause execution for a specified number of seconds to pace polling against long-running tasks, preventing excessive API calls while waiting for job or pipeline completion.

Instructions

Sleep for a fixed number of seconds, then return. Use this to pace polling against long-running platform work (most often get_pipeline_status after run_tap, or get_job_status after upload_data) so you do not burn tool calls hammering an endpoint that is still in progress. ALWAYS poll once BEFORE the first wait — many runs finish in 1–5 seconds. Then use exponential backoff between polls: 5s, 10s, 20s, 30s, 60s, 60s, ... (cap at 60s normally, 120s only if the run is genuinely glacial). Reset to a short wait (5–15s) on the next cycle whenever a poll shows new jobs flipped to a terminal state — that means you're close to done. If 80%+ of jobs are terminal, wait ~15s; if only 1–2 jobs remain, wait ~10s. Hard upper bound is 120 seconds per call — for longer waits, call this tool in a loop interleaved with a status check.

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": {
      "seconds": "<seconds>"
    },
    "name": "wait_seconds"
  }
}

Input Schema

NameRequiredDescriptionDefault
secondsYesHow long to sleep, in seconds. Range: 1–120. Values outside this range are clamped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does well: it says the call blocks for the duration, states the hard 120s per-call upper bound, and explains the loop workaround for longer waits. It does not explicitly say the tool is side-effect-free or what happens if the caller is interrupted, so it falls just short of full coverage.

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?

Front-loaded with the core action and the primary alternative before the operational detail. It runs long for a single-parameter sleep tool, and the backoff/cap guidance is stated in a few overlapping ways, but nearly every sentence is actionable rather than filler.

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?

For a one-parameter pacing tool with no annotations and no output schema, the definition supplies everything an agent needs: when to call it, the sequence of values, the per-call ceiling, and how to extend past it. Nothing material 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% and already documents the 1–120 range and clamping, so the baseline would be 3. The description adds practical meaning beyond that range — recommended values of 5/10/20/30/60 and the guidance to cap at 60 normally and 120 only for glacial runs.

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?

Opens with a concrete verb+resource: 'Sleep for a fixed number of seconds, then return.' That unambiguously distinguishes it from every sibling like get_pipeline_status or run_tap, which are status/mutation tools rather than pacing primitives.

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?

Explicitly states when to use it and against which siblings ('get_pipeline_status after run_tap', 'get_job_status after upload_data'), what NOT to do ('do not burn tool calls hammering an endpoint'), and gives a full backoff schedule plus reset conditions. Also mandates polling once before the first wait.

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