Skip to main content
Glama

Get job status

vestige_job_status
Read-only

Retrieve the status, progress, and result counts of an analysis job by job ID to monitor running work and check completed results.

Instructions

Get the status, progress, and result counts of an analysis job.

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": {
      "jobId": "<jobId>"
    },
    "name": "vestige_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/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 the safety profile is covered. The description adds real value by saying the response includes status, progress, and result counts, but omits whether results are populated only on completion, what states exist, or how an unknown/expired jobId is 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?

A single front-loaded sentence with no filler. It is efficient, though at this length it leaves room that could have been spent on the jobId or job lifecycle without becoming bloated.

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 return values, and it does so only at the level of field names (status, progress, result counts). For a polling tool the agent would additionally benefit from job-state enumeration and re-poll guidance, which are absent.

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?

There is a single required jobId parameter whose schema has no description at all (0% coverage), and the description never mentions it. The only semantic hint is the word 'job' in prose, so it adds essentially nothing beyond the parameter name.

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?

The description uses a specific verb (Get) plus a named resource (the status, progress, and result counts of an analysis job), which is clearly distinct from siblings like vestige_analyze or vestige_job_cancel. It never names those siblings, so the differentiation is implicit rather than stated.

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?

There is no explicit guidance on when to call this versus vestige_analyze, vestige_list_findings, or vestige_job_cancel. The agent must infer from the word 'job' that this is the polling/check-in tool used after starting an analysis.

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