Skip to main content
Glama
kompas-mcp

kompas-mcp

by biryak

Job status

job_status
Read-onlyIdempotent

Check a long-running job's status by ID to see done, failed, and pending counts plus results for each finished item, with an optional wait for completion.

Instructions

Status of a long-running job (export returns a job id): done/failed/pending counts and the result of every finished item (each is a checkpoint). Job ids live as long as the server process.

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": "job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id returned by a long operation
wait_sNowait up to this long for the job to finish

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower. The description still adds real value by disclosing what the response contains (per-item results treated as checkpoints) and the important lifetime constraint that job ids live only as long as the server process, implying ids can become invalid after restart.

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?

Two compact sentences with the core purpose and return shape front-loaded and the lifetime caveat last. The parenthetical '(each is a checkpoint)' is slightly cryptic but still earns its place.

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

Completeness4/5

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

For a read-only polling tool with full schema coverage and clear safety annotations, the description covers origin of the id, return contents, and the id-lifetime caveat that absent output schema would otherwise leave unexplained. It stops short of describing error behavior for expired ids explicitly.

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%, so job_id and wait_s are already documented in the schema. The description reinforces where job_id comes from (export) but adds no format or constraints beyond that, so the baseline 3 applies.

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 pairs a specific resource (a long-running job's status) with what it reports — done/failed/pending counts plus the result of each finished item — and names the sibling that produces the id (export), so an agent can distinguish it from the other tools in the list.

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 makes the usage context explicit: call this with the job id that a long-running operation such as export returned. It doesn't state an explicit when-not or name polling alternatives, which keeps it out of 5 territory.

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