BlindOracle

check_job_status

Retrieve the current status of a submitted job using its job ID and optional token for validation.

Instructions

Check status of submitted job @requirement: REQ-MCP-006 - Job status tracking @requirement: REQ-AUTH-002 - Job token validation Properties: Durability(+0.4), Alignment(+0.2)

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": "check_job_status"
  }
}

Input Schema

Name	Required	Description	Default
`job_id`	Yes
`job_token`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions requirements and 'Durability'/'Alignment' properties, but these are opaque and do not clarify behavior like whether the tool is read-only, what side effects occur, or what the response contains.

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 description is short but includes extraneous lines like '@requirement' and 'Properties' that are not helpful for tool selection or invocation. These could be removed for conciseness without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema but the description fails to explain what 'status' means or what the output contains, the description is incomplete. It does not cover the full scope of information needed for an agent to correctly interpret results.

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%, meaning the description adds no meaning to parameters beyond the schema. The description does not explain what 'job_id' or 'job_token' represent or how they should be used, leaving the agent to rely solely on 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 clearly states the tool's purpose: 'Check status of submitted job'. It uses a specific verb 'check' and resource 'job status', but does not differentiate from sibling tools like 'get_job_result', which might also provide status information.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'get_job_result' or 'submit_arbitrage_job'. There is no indication of prerequisites or context.

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