Skip to main content
Glama

bx_artifact_get

Read-onlyIdempotent

Read a digest-bound artifact page by page using Unicode codepoint offsets, then reassemble all pages and verify the SHA256 to confirm the full source, proposal, verification, and report bytes are intact.

Instructions

按摘要分页读取完整工件,offset单位是Unicode码点。 / Read a digest-bound artifact by Unicode codepoint pages, preserving full source, proposal, verification and report bytes. Reassemble every page and verify SHA256.

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": {
      "sha256": "<sha256>"
    },
    "name": "bx_artifact_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
sha256Yes

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 readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description adds genuinely new behavior: paging is codepoint-based and callers must reassemble all pages and verify the digest. It does not describe behavior on digest mismatch, offset past end-of-artifact, or truncation.

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 front-loaded sentences that state the operation, then the paging rule and verification duty; nothing wasted. The Chinese/English duplication doubles the surface text, though the content is not padded.

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 structure need not be explained, and the digest-plus-pagination contract is conveyed. Still missing for a paging reader with zero schema documentation: default limit, end-of-stream signaling, and failure handling when the reassembled bytes fail the SHA256 check.

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 0%, but 'sha256' and 'limit' are largely self-describing from name and constraints, and the description clarifies the one truly ambiguous parameter by specifying offset is measured in Unicode codepoints. It adds nothing about page-size defaults or what limit governs beyond the schema's 1..16384 bounds.

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 and resource: read a digest-bound artifact, and names the four byte-segments it preserves (source, proposal, verification, report). It does not explicitly distinguish itself from siblings like bx_result_get or bx_job_get, so an agent must infer the boundary from the 'artifact' framing.

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?

Gives procedural guidance for pagination ('Reassemble every page and verify SHA256'), which tells an agent how to use it correctly. It never states when to prefer this over a sibling reader or what to do when no more pages remain, so usage context is implied rather than explicit.

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