Skip to main content
Glama

Job status

job_status
Read-only

State of an analysis job (queued, running with stage and percent, done, failed, cancelled). Waits up to wait_seconds for it to finish; a finished PCAP job includes its summary.

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 pcap_analyze
wait_secondsNowait up to this many seconds for the job to finish (0-55, default 0)

Output Schema

NameRequiredDescriptionDefault
nextNo
errorNo
stageNocurrent stage while running: parsing, audio, sip, ...
job_idYes
statusYes
percentYes
summaryNoset when a PCAP job is done
created_atYes
expires_atNothe result is deleted at this time
finished_atNo
queue_positionNoapproximate place in the queue while queued

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / job_id / description
      Added value: +"job_id returned by pcap_analyze"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false; the description adds the state vocabulary, the blocking wait semantics, and that a finished PCAP job returns a summary. It does not explain timeout or error behavior or why idempotentHint is false, but it adds useful context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loading the returned states and then the wait behavior. There is no filler; every clause contributes.

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 a rich schema and output schema, the definition covers the important state model and blocking wait. It could be stronger by specifying what is returned if wait_seconds elapses before completion or if the job is missing, but the core contract is present.

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?

With 100% schema coverage, job_id and wait_seconds are already fully documented in the schema. The description mentions wait_seconds but only restates its wait purpose; it adds no syntax, range, or default detail beyond the schema.

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 names the resource (an analysis job) and the exact state set it returns, plus the wait behavior. It is clearly a status-check tool, but it never names list_jobs or job_cancel as alternatives, so sibling differentiation is left implicit.

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?

It implies usage by describing the wait-for-completion behavior, but does not state when to prefer job_status over list_jobs or when to use job_cancel instead. No exclusions or preconditions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources