Skip to main content
Glama

bx_job_get

Read-onlyIdempotent

Read one owned job's status, failures, observed request count, and exact saved result reference without making a model call.

Instructions

查询作业状态、失败、调用数及结果版本。 / Read one owned job status, failures, observed request count and exact saved result reference. No model call.

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": {
      "project_id": "<project_id>",
      "job_id": "<job_id>"
    },
    "name": "bx_job_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
project_idYes

Output Schema

NameRequiredDescriptionDefault
dataYes
kindYes
productYes
api_versionYes
business_decisionYes
execution_authorizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0-rc.9-linux.1

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely new context: no model invocation (cost/latency expectation) and that only 'owned' jobs are readable (authorization scoping). It does not mention behavior for pending vs failed jobs, but with annotations that is a minor gap.

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

Conciseness3/5

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

The content is front-loaded and short, but the Chinese sentence is a near-verbatim duplicate of the English one, so roughly half the text is redundant token cost with no added information.

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?

An output schema exists and annotations are rich, so return values and safety need not be described. However, for a two-parameter tool with zero schema description coverage, the description leaves the parameter meanings unexplained, which is the main incompleteness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both parameters are required UUID-pattern strings with no inline documentation. The description never explains what project_id versus job_id identify or that job_id must belong to project_id; 'owned' only weakly implies the ownership constraint. It fails to compensate for the coverage gap.

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 specific verb and resource ('Read one owned job status, failures, observed request count and exact saved result reference'), which plainly distinguishes it from bx_job_cancel and hints that the saved result lives behind bx_result_get. The scope word 'owned' and 'one' add precision. It stops short of naming a sibling, so 4 rather than 5.

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?

'No model call' implies this is the cheap polling/inspection path, and 'exact saved result reference' implies a downstream handoff to bx_result_get. But there is no explicit when-to-use or when-not-to-use statement, and no routing to bx_job_cancel or bx_result_get is spelled out.

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