Skip to main content
Glama

aw.artifact.read_chunk

Read-only

Return one bounded binary embedded resource from this session artifact, plus range/whole-file hashes. Reassemble and hash ALL bytes. Not disk-save or whole-file verification from one range.

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": {
      "session": "<session>",
      "artifactId": "<artifactId>",
      "offset": "<offset>"
    },
    "name": "aw.artifact.read_chunk"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthNo
offsetYes
sessionYesPrivate short-lived session capability returned by aw.session.open. Never publish or log it.
artifactIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavior by disclosing that each call returns a bounded chunk plus range and whole-file hashes, and that the caller must reassemble all bytes. It does not mention how end-of-artifact is signaled or what happens if offset exceeds the artifact, leaving a small gap.

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?

Three short sentences with the core action front-loaded and no filler. The final negation fragment ('Not disk-save or whole-file verification from one range') is telegraphic and grammatically loose, costing some clarity for the guidance it carries.

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?

For a read-only chunked-fetch tool with no output schema, the description covers the essentials: what is returned (a bounded resource plus range and whole-file hashes) and how to use it (loop and reassemble all bytes). The remaining shortfall is the absent parameter-level detail on offset and length limits.

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 only 25% (only 'session' is documented, correctly warning that it must never be logged). The description gestures at 'bounded' and 'range', but never explains offset semantics, the length default/maximum of 262144, or the offset ceiling of 8388608, so it does not compensate for the undocumented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Return one bounded binary embedded resource from this session artifact') and scopes it to a single chunk. It also explicitly fences off the neighboring concept of 'whole-file verification from one range', which maps to the sibling aw.artifact.verify, so an agent can distinguish the two without opening either schema.

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?

'Reassemble and hash ALL bytes' tells the agent this tool is meant to be called repeatedly across offsets rather than once, which is real usage guidance. The exclusion 'Not disk-save or whole-file verification from one range' points away from misuse, but no alternative tool is named and no prerequisite/ordering guidance is given beyond that.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources