Skip to main content
Glama

fort_job_get

Check the status of a Bearfort job on a hosted site, optionally retrieving its log to monitor backup, restore, or migration tasks.

Instructions

Status of a Bearfort job on this fort (backup, restore, migration, ...). with_log:true adds the job's log text. Needs BEARFORT_API_KEY.

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": {
      "site": "<site>",
      "job_id": "<job_id>"
    },
    "name": "fort_job_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites); must be hosted on Bearfort
job_idYesJob id (e.g. from fort_backup_create)
with_logNoAlso return the job log

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description does carry useful behavioral detail: it declares the BEARFORT_API_KEY credential requirement and explains that with_log:true increases the response payload with log text. It does not disclose what the status payload contains, whether unknown job ids error, or how large logs can get.

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 short sentences, with the core purpose front-loaded before the with_log note and the credential requirement. Slightly telegraphic phrasing ('on this fort', '(backup, restore, migration, ...)') but nothing wasted.

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?

There is no output schema, so the description is the only source of return-value information, and it stops at saying it returns 'status' without describing fields or state values. For a simple read tool with fully documented params this is serviceable but leaves a real gap on what comes back.

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 all three parameters are already documented, including 'site must be hosted on Bearfort'. The description adds only a slight restatement of with_log ('adds the job's log text'), which is essentially the schema's own wording, so the baseline 3 applies.

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?

States a concrete verb+resource: retrieves the status of a Bearfort job on a given fort, and enumerates job kinds (backup, restore, migration). It is clearly a job-status reader rather than a job creator or lister, though it never names a sibling to contrast with explicitly.

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?

Usage is only implied: the schema note that job_id comes 'from fort_backup_create' hints at the poll-after-create pattern, but the description itself gives no when-to-use, when-not-to-use, or alternative (e.g. fort_backup_list for enumerating jobs).

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

Deploy Server

Other Tools