Skip to main content
Glama
Sign In
zai-one

grok-delegate

by zai-one
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Poll agent job

grok_agent_poll
Read-only

Poll a typed job to read bounded progress and events, and retrieve its final evidence receipt. Use it to track job status and obtain verifiable results.

Instructions

Read bounded progress/events and the final evidence receipt for a typed job.

Input Schema

NameRequiredDescriptionDefault
limitNo
job_idNo
wait_secondsNoBlock until the job reaches a terminal state, up to this many seconds, emitting notifications/progress while it waits. 0 or absent returns immediately, as before.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.26.1
    • addedInput schema / properties / wait_seconds
      Added value: +{
+  "description": "Block until the job reaches a terminal state, up to this many seconds, emitting notifications/progress while it waits. 0 or absent returns immediately, as before.",
+  "maximum": 1800,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv0.4.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that reads are 'bounded' and that a terminal 'evidence receipt' is available, but says nothing about rate limits, polling cadence, or what happens when the job is still running beyond the start of the wait.

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?

A single front-loaded sentence with no filler; 'bounded' and 'final evidence receipt' both carry weight. Slightly terse for a 3-parameter tool but structurally sound.

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

Completeness3/5

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

With no output schema, the description carries the burden of explaining returns; it gestures at 'progress/events' and a 'final evidence receipt' but gives no shape, fields, or terminal-state semantics. Combined with undocumented job_id/limit and no routing guidance among three status/poll siblings, it is only minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: wait_seconds is documented in the schema (including blocking and notification behavior) while limit and job_id have no description anywhere. The tool description adds nothing about what limit bounds or the format/expected value of job_id, so it fails to compensate for the coverage gap.

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?

States a specific verb (read) and resource (bounded progress/events and the final evidence receipt) scoped to a typed job, which is more informative than the title 'Poll agent job'. However, it never distinguishes itself from the sibling grok_agent_status or grok_delegate_status, leaving an agent unsure which polling verb to choose.

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?

No when-to-use guidance is given. It does not say when to poll versus calling grok_agent_status, nor whether polling should precede or follow grok_agent_execute, and the only usage note ('as before') refers to prior behavior rather than routing logic.

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