Skip to main content
Glama

turn

Compile Markdown pipe tables into the Whiteboard before editing verified files when contracts or architecture change, keeping the board current and preventing stale architecture state.

Instructions

Step 2 (Mutate Board First -> STALE): Compile Markdown pipe tables into the Whiteboard in <50ms BEFORE editing any VERIFIED file when contracts/architecture change. Canonical table headers: | Charter | Summary | Principles |, | Component | Role | Why | Owner | Stage | Depends_On | Files | (Why column is optional), | Flow | Source | Target | Payload | Condition |, | Interface | Component | Inputs | Outputs | Owner | Stage | File | Spec |, | Law | Component | Owner | Stage | Bend_Dir | Args | LHS | RHS | Spec | (reserve % LAW for multi-variable k>=2 boolean rules using Bool.and/or/not; never invent 1-boolean x==x tautologies), | Schema | Component | Fields | Owner | Stage | File | Spec |, | Rule | Component | Type | Property | Op | Value | Condition |.

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": {
      "board": "<board>",
      "message": "<message>"
    },
    "name": "turn"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardYesTarget board name
messageYesCanonical Markdown pipe tables (Charter, Component, Flow, Interface, Law, Schema, Rule)
profileNoRuntime profile (cloud, hybrid, local)
speakerNoSpeaker alias (default: agent)
round_numNoOptional round number
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

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful traits: a sub-50ms performance expectation, a mandatory ordering relative to file edits, and content-schema constraints (Why column optional, % LAW reserved for multi-variable rules, no 1-boolean tautologies). It says nothing about overwrite semantics, failure behavior, or whether board contents are replaced or merged.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single run-on sentence that packs the purpose, ordering constraint, performance claim, and eight table header schemas into one breath. The reference material is arguably necessary, but it is not front-loaded or structured, making it hard to scan for the actual instruction.

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?

For a 6-parameter mutation tool with no annotations and no output schema, the description covers the payload format and timing but omits what the tool returns, whether the board is created or overwritten, and how profile/project_root affect behavior. It is adequate on content, thin on operational behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description goes beyond it by expanding the accepted `message` payload with concrete canonical headers and column lists, plus rules on which columns are optional and what may not be authored. The remaining parameters (profile, speaker, round_num, project_root) get no added meaning.

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 core purpose is stated: 'Compile Markdown pipe tables into the Whiteboard.' However, it is buried inside cryptic process jargon ('Step 2 (Mutate Board First -> STALE)', 'VERIFIED file') that an agent must decode, and nothing distinguishes it from siblings like atlas or status that may also touch board content.

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?

There is an explicit ordering/timing constraint ('BEFORE editing any VERIFIED file when contracts/architecture change'), which is real usage guidance. But it names no alternatives and gives no when-not conditions, so an agent still cannot tell what to use instead when the trigger condition does not hold.

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