Skip to main content
Glama

blueprint_resume

Resume interrupted or failed jobs by job ID, validating and reusing stage caches while preserving cumulative call and token budgets.

Instructions

断点续跑已中断/失败任务,校验并复用阶段缓存;累计调用与 token 预算不会重置。

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

Input Schema

NameRequiredDescriptionDefault
job_idYes任务返回的 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations establish the mutation/open-world profile, and the description adds two non-obvious behaviors: stage caches are validated and reused, and cumulative call/token budgets are NOT reset. That budget detail is exactly the kind of consequence an agent cannot get from the schema. It stops short of saying what happens when validation fails or whether work is re-executed.

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?

A single dense sentence with the action front-loaded and the budget caveat trailing; no filler, no repetition of the title or schema.

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?

With no output schema, the description could have said what comes back on resume (job id, resumed stage, status), which is a real gap for a tool an agent will chain with blueprint_status. Otherwise the key non-obvious behaviors are covered and the single parameter is fully documented elsewhere.

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?

Only one parameter (job_id) and schema coverage is 100%, with the schema already documenting it as the ID returned by the task and constraining it to a 12-char hex pattern. The description adds nothing about job_id, so the schema baseline of 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 specific verb+resource+scope: resume a previously interrupted/failed task, validating and reusing stage cache. An agent can tell it is a continuation operation, though it does not name or contrast any sibling (e.g. blueprint_status or blueprint_result), so differentiation is left to inference.

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?

The condition for use is explicit: tasks that were interrupted or failed (已中断/失败任务). It does not state when NOT to use it, nor point to blueprint_status/blueprint_result as the check-first or fetch-results alternatives, so routing among siblings still requires guessing.

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