Skip to main content
Glama

askround_job

Poll a background multi-model answer round by job ID to track progress, retrieve its brief or report, and see retained answers if it failed or was interrupted.

Instructions

A round or prompt set started with background: true - running (with how many answers are in), done (with its brief or report), refused, failed, or interrupted (with the answers it finished, which are kept).

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": "<job>"
    },
    "name": "askround_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYesthe id the start returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well by disclosing the possible outcomes: running (with answer count), done (with brief or report), refused, failed, and interrupted (with finished answers kept). It still does not state whether the call is read-only, whether it blocks or returns a snapshot, or how invalid job ids are handled.

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?

The definition is a single compact sentence with no filler, and the core resource is front-loaded. The parenthetical state details are dense but purposeful, though the sentence is a fragment and slightly awkward to parse.

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?

For a simple one-parameter status tool with no output schema, the description helpfully explains what each state contains, which substitutes for some missing return documentation. It still omits important context such as read-only behavior, error handling for unknown job ids, and whether the call is a snapshot or waits for completion.

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?

Schema coverage is 100% and the single parameter is already documented as 'the id the start returned'. The description reinforces that this is for jobs started with background: true, but adds no further syntax, format, or validation detail beyond the schema. Baseline 3 is appropriate when the schema already defines the parameter clearly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource as a 'round or prompt set started with background: true' and enumerates the possible states, which makes the domain clear. However, it never states an action verb such as 'get' or 'check status', so the exact operation is only inferred. Sibling tools like askround_run and askround_report are not referenced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'started with background: true' gives a useful precondition for when this tool applies: it is for background jobs created elsewhere. Yet there is no explicit when-to-use vs. alternatives guidance, no exclusions, and no mention of how it relates to siblings such as askround_run or askround_report.

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