Skip to main content
Glama

bx_task_validate

Read-onlyIdempotent

Validate complete structured task inputs, parent-child links, resource bindings, and joint byte limits before processing, without saving data or calling a model.

Instructions

校验完整结构化输入、父子关系及容量,不保存。 / Validate full source texts, explicit parent links, resource binding and joint byte limits without persisting or calling 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": {
      "input": "<input>"
    },
    "name": "bx_task_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety bar is low. The description adds real context beyond them: no model invocation, no persistence, and the fact that joint byte limits and parent/child relations are checked together — behavioral facts the annotations cannot convey.

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?

Front-loaded with the verb and the validation scope in a single tight sentence, then repeated bilingually. The Chinese/English duplication costs some length but the content is dense and waste-free.

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 so return values need no explanation, and the safety profile is annotation-covered. Still, for a nested payload with many undocumented fields (dependencies, retained, dictionaries.sha256), the description does not explain enough about what makes those fields valid or what a failure looks like.

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, but it is a deeply nested object with 0% schema description coverage. The description names several validated aspects (source texts, parent links, resource binding, byte limits) which map to nodes, dictionaries and sizing, but the dependencies (kind enum), retained clauses and sha256 binding are left unexplained in both schema and description.

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 (validate) plus the exact validation targets: full source texts, explicit parent links, resource binding and joint byte limits. The negation 'without persisting or calling a model' separates it from an import/analysis sibling, though it never names that sibling explicitly.

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 rather than stated: 'without persisting' suggests a dry-run check before an import call, but the description never says 'use this before importing' or when to skip validation. No alternative tool is named for the agent to route between.

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