Skip to main content
Glama

Check a background job

flypost_job_status
Read-only

One non-blocking check of a background job. Use with the job handle a blocking tool returns when it times out, or after flypost_archive_source.

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": {
      "type": "<type>",
      "id": "<id>"
    },
    "name": "flypost_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe row id from the job handle.
typeYes
run_idNocarousel-deck jobs: the run_id from the job handle, so an older deck is not mistaken for this build.
slide_idNocarousel-slide jobs only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish read-only, non-destructive, closed-world safety. The description adds useful behavior by saying the check is non-blocking, single, and takes a handle from a timed-out blocking tool or archive_source. However, it does not state what statuses are returned or whether repeated polling is expected, and there is no output schema to cover that gap.

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 sentences with no wasted wording. The behavioral constraint and usage context are front-loaded, and every sentence earns its place.

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 four-parameter job status tool with annotations and no output schema, the definition covers when to call it and where the job handle comes from. It omits what the check returns and how to interpret terminal states, leaving an important gap for an agent using the result.

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?

The input schema documents id, type, run_id, and slide_id at 75% coverage. The description adds that these come from a job handle, which is useful context, but it does not explain the parameter mapping or the run_id/slide_id disambiguation beyond what the schema already provides.

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 states a specific action and resource: a non-blocking check of a background job, and contrasts it with blocking tools. It could more explicitly say what status information is returned, which keeps it from a 5.

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 clearly tells the agent to use the job handle returned by a blocking tool when that tool times out, or after flypost_archive_source. It does not describe when not to use it or name alternative status-checking tools, so it stops short of a 5.

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.