Skip to main content
Glama

bx_task_import

Read-onlyIdempotent

Preview complete Markdown parent-child task input and validate structure without saving. Confirms missing parents and explicit Task ID/Parent Task ID so you can check a task tree before creating it.

Instructions

预览完整Markdown父子任务,支持多个DEV和明确父任务编号,不自动保存。 / Preview complete Markdown parent-child input. Supports ## PM → DEV(1/14), repeated DEV roles and explicit Task ID/Parent Task ID. Missing parents require confirmation; numbering never implies order. Does not create a project or call a model.

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": {
      "source": "<source>",
      "label": "<label>",
      "profile_id": "<profile_id>",
      "dictionaries": "<dictionaries>"
    },
    "name": "bx_task_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYes
sourceYes
parentsNo
profile_idYes
dictionariesYes

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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: no auto-save, no project creation, no model call, missing parents require confirmation, and 'numbering never implies order'. It stays silent on what the preview returns (errors vs. per-task rows), relying on the output schema for that.

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 dense, but every sentence is duplicated bilingually (Chinese then English), roughly doubling length without adding information for an agent. Within each language the wording is efficient, so the issue is redundancy rather than padding.

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?

For a 5-parameter tool with a nested object, 4 required fields and 0% schema coverage, the description should explain how profile_id and dictionaries.selection/sha256 bind the import, and it does not. The existence of an output schema excuses it from describing return values, but the input side remains materially under-documented.

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% across 5 parameters, yet the description only illuminates the 'source' Markdown format, parent references, and the 'parents' confirmation behavior. The required 'label', 'profile_id', and the nested 'dictionaries' object (selection l2/l3 plus a 64-hex sha256) get no explanation at all, leaving the agent to guess what a profile binding or dictionary hash must contain.

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 gives a concrete verb+resource: 'Preview complete Markdown parent-child input' and names the exact input format (## PM → DEV (1/14), repeated DEV roles, explicit Task ID/Parent Task ID). It also distinguishes itself from write-style siblings by stating 'Does not create a project or call a model', though it never names bx_task_validate as the likely alternative.

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 implied by 'Preview ... does not save' (preview-before-import step) and the rule 'Missing parents require confirmation' gives conditional guidance. There is no explicit statement of when to use this versus bx_task_validate or when to skip preview, so the agent must infer the workflow position.

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