Skip to main content
Glama

packets

Compile self-contained work bundles with Bend 2 laws, Python AST skeletons, Spec docstrings, MUST CALL anchors, and baseline commit SHA for stale components.

Instructions

Step 3 (Build STALE Packet): Compile self-contained WorkPackets with Bend 2 laws_skeleton, Python AST python_skeleton (with Spec docstrings & # MUST CALL anchors), and baseline_commit_sha.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "packets"
  }
}

Input Schema

NameRequiredDescriptionDefault
waveNoFilter by wave (0, 1, or 2)
boardNoBoard name (default: lattice_core)
forceNoForce packet compilation even if board is INCOMPLETE_DRAFT
statusNoFilter by build_status (e.g. STALE, READY, VERIFIED)
componentNoFilter by component name
include_rawNoInclude raw artifacts and wave buckets (default: false)
project_rootNoOptional repository root path (auto-discovered by board name or file paths if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. "Compile" implies a write/build operation, yet the schema is dominated by filter-style parameters (wave, board, status, component, include_raw), leaving the agent unsure whether this reads, writes, or both, and whether existing packets are overwritten. Nothing is said about required board state, side effects, or the force/incomplete-draft behavior that the schema hints at.

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?

It is a single compact sentence with the step label front-loaded, so it is not padded. However, the sentence is jargon-dense to the point of opacity and packs three distinct artifacts into one clause, hurting parseability rather than earning its place. Brevity here reflects under-explanation more than disciplined concision.

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?

A seven-parameter tool with no annotations and no output schema needs the description to explain the compile-versus-filter relationship, the resulting artifact, and preconditions. Instead it supplies a single jargon-heavy clause. Given the complexity signals, an agent cannot confidently call this correctly from the description alone.

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 description coverage is 100%, so the schema already documents all seven parameters with defaults and examples, which sets the baseline at 3. The description adds no parameter meaning whatsoever — notably it does not explain how the filter parameters (wave, status, component) relate to the act of compiling packets. Baseline 3 is the correct ceiling here.

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

Purpose3/5

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

The description pairs a verb ("Compile") with a resource ("self-contained WorkPackets"), so the action is nominally identifiable, but the payload is described entirely in project-specific jargon ("Bend 2 laws_skeleton", "Spec docstrings", "# MUST CALL anchors") that an outside agent cannot decode. It also never distinguishes this tool from siblings like slice, atlas, or status. A reader knows it produces packets but not concretely what they contain or why this differs from other build steps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Step 3 (Build STALE Packet)" is the only usage signal: it implies a position in a sequence and a target state (STALE). There is no statement of when to call it versus alternatives, no prerequisites (e.g. board must exist or be past a given state), and no when-not-to-use guidance. An agent must infer ordering and preconditions from the ordinal label alone.

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

Deploy Server

Other Tools