Skip to main content
Glama
Sign In
Engram

Engram

by staticroostermedia-arch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

mcp_engram_thought_tile_draft_from_chain

Build a verified_sequence_v0 draft payload from a trace chain without minting a tile. Use when condensation_hint fires or before calling thought_tile_create.

Instructions

WS-2: Build verified_sequence_v0 draft payload from trace chain without minting a tile. Use when condensation_hint fires or before thought_tile_create.

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": {
      "goal_context": "<goal_context>"
    },
    "name": "mcp_engram_thought_tile_draft_from_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
head_traceNoChain head trace id (optional — resolves from goal if omitted)
goal_contextYesGoal id to filter traces and set draft goal_context

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0-beta.2

TDQS

A4/5.0
Behavior3/5

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

No annotations provided; description discloses non-minting behavior but lacks details on side effects, permissions, or state modifications beyond 'build draft payload from trace chain'.

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 concise sentences front-load the action, though 'WS-2' is cryptic; no fluff, but clarity could be slightly improved without the prefix.

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?

Lacks description of output payload structure or error conditions; with 2 parameters and no output schema, the description is adequate but not fully comprehensive.

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% with clear explanations for both parameters; description does not add further meaning beyond what schema already provides.

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?

Description clearly states the tool builds a verified_sequence_v0 draft payload from a trace chain without minting a tile, distinguishing it from the sibling thought_tile_create which mints a tile.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'when condensation_hint fires or before thought_tile_create', providing clear context and alternative.

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