Skip to main content
Glama

refresh_status

Check a refresh job's progress per procurement source, including status, attempts, observed and saved notices, and errors, so you can identify partial, failed, timed-out, or interrupted work.

Instructions

Read job progress per source: status, attempts, observed/saved notices and error.

    observed counts yielded notices, saved counts committed notices. An adapter may buffer
    pages internally, so RUNNING with observed=0 can still be fetching. PARTIAL means some
    sources completed and some failed; FAILED means none completed. TIMED_OUT marks a source timeout. Read completed sources with
    ordinary searches. After a server restart, lost work becomes INTERRUPTED; resume it
    with resume_refresh. Polling does not repeat completed sources or retry failures.
    

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_id": "<job_id>"
    },
    "name": "refresh_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it decodes RUNNING/PARTIAL/FAILED/TIMED_OUT/INTERRUPTED, explains that observed=0 can still mean fetching due to adapter buffering, and documents that polling neither repeats completed sources nor retries failures. The post-restart INTERRUPTED behavior is exactly the kind of non-obvious trait an agent could not infer.

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?

Nearly every sentence carries distinct information, with the core definition front-loaded before the status semantics. Minor cost: the mid-sentence line breaks split thoughts awkwardly and the status enumeration is dense, but no sentence is 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?

An output schema exists, so return shapes need not be explained, yet the description still maps each status value to a meaning, covering the interpretive gap that a schema alone would leave. For a single-parameter read tool with full status semantics and restart/resume guidance, nothing essential is missing.

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 0% and the single parameter, job_id, is never explained in the description — no indication of where the ID comes from (presumably start_refresh) or what happens on an unknown/stale ID. The semantic detail about statuses does not compensate for this undocumented parameter.

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?

The description opens with a specific verb and resource ('Read job progress per source') and enumerates exactly what is returned: status, attempts, observed/saved notices, and error. That scope clearly separates it from start_refresh and resume_refresh, which create or advance jobs rather than read them.

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 explicitly routes the agent: read completed sources with ordinary searches, and resume INTERRUPTED work with resume_refresh. It also clarifies that polling is safe and non-repeating, which tells the agent when repeated calls are appropriate. It stops short of stating when this tool is not needed (e.g., before a job exists).

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