Skip to main content
Glama

查询副席任务进度与结果

sidedesk_job_status

Check a dispatched job's live status and progress by jobId, including shadow-copy change summaries, source integrity checks, and final replies; optionally wait up to 120 seconds.

Instructions

查询指定 jobId 的运行状态、实时进度、影子副本改动摘要、源目录完整性校验与最终回复。可配合 waitSeconds 优雅等待。

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": {
      "jobId": "<jobId>"
    },
    "name": "sidedesk_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYessidedesk_dispatch 返回的 jobId
waitSecondsNo可选:最多等待多少秒再返回(默认 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose that the call is a read of job state and that waitSeconds causes the call to block for a while ('优雅等待'), which is helpful behavioral context. It does not say what happens with an unknown or expired jobId, whether results persist after completion, or any auth/rate constraints, leaving meaningful gaps for an unannotated tool.

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, front-loaded with the query action and the list of returned artifacts. Each clause names a distinct piece of information, so nothing reads as filler. Slightly dense enumeration, but efficient.

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?

There is no output schema, so the description must convey return values, and it does so by naming five concrete result components including the final reply. It also explains the wait option. The main omission is failure behavior for an invalid jobId.

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%, with both jobId and waitSeconds fully documented including the 0-120 bound, so the baseline is 3. The description adds marginal meaning by framing waitSeconds as a way to avoid polling ('可配合 waitSeconds 优雅等待'), but adds no format or semantics 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 states a specific verb (查询) and resource (指定 jobId 的任务), then enumerates what is retrieved: 运行状态、实时进度、影子副本改动摘要、源目录完整性校验、最终回复. This tells an agent clearly that it is a status/result-read tool, distinct from dispatch or abort siblings by implication. It stops short of naming an alternative tool explicitly, so not 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the jobId comes from sidedesk_dispatch, so this is the follow-up call after dispatching. The waitSeconds hint suggests using it instead of tight polling loops, which is genuinely useful. However, there is no explicit when-not guidance, no mention of how it relates to sidedesk_abort_job, and no statement about whether repeated polling is acceptable.

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