Skip to main content
Glama

Arroway

by app.arroway
OverviewDiscussionsAdmin

Log what a task left behind

arroway_log

Record the durable residue of a COMPLETED task in the team-visible daily log: what someone arriving later needs in order not to redo it, dated state included. ALWAYS write the authored essence (only a frozen catalog without that field may omit it). If the person corrected you for re-litigating a decision, say so. If this work made a read memory's 'dies when' true, name it in fulfills and it is retired with this entry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoOptional free tag (e.g. 'marketing')
sourceNoOptional pointer to a living source (URL, doc, CRM id)
contentYesWhat was decided, found or changed, and what it cost. You judge the length.
essenceNoOne authored line with the operative result; never the opening of the body.
projectYesProject slug. Not from the person or a read this session? It is a guess: check the arroway_catch_up roster.
fulfillsNoMemories whose 'dies when' this work made true (decision/fact/reference received in full in a read). Never one that merely looks old.
backfilledNotrue for history from BEFORE Arroway existed, not today's work.
keep_wholeNotrue only after you considered cutting an indivisible oversized residue.
operationalNotrue for HOW the work went (failures, measurements, self-corrections): kept for catch-up, out of task reads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changed
    • changedInput schema / properties / backfilled / description
      Previous value: -"True when the entry describes something that happened BEFORE Arroway existed (history you are bringing in), not today's work."New value: +"true for history from BEFORE Arroway existed, not today's work."
    • changedInput schema / properties / content / description
      Previous value: -"The full durable residue: what was decided, found or changed, and what it cost. It remains recoverable by handle."New value: +"What was decided, found or changed, and what it cost. You judge the length."
    • removedInput schema / properties / content / minLength
      Removed value: -1
    • changedInput schema / properties / essence / description
      Previous value: -"One authored line with the operative result. This is what the normal project read serves; never copy the opening of the body."New value: +"One authored line with the operative result; never the opening of the body."
    • removedInput schema / properties / essence / minLength
      Removed value: -1
    • changedInput schema / properties / fulfills / description
      Previous value: -"ARROW-290. The memories this completed work REALIZED — their 'dies when' condition is now true because of what you did (a routine that an idea asked for is running; a planned move was made; a dated status has been replaced by what this entry records). Each one is retired in the same act as this log, with your 'how' as the reason on its archived line, reversible from the panel. Guards: only decision/fact/reference (a rule is never 'fulfilled'), and only memories this connection received in full in a read — if any item fails, the whole call is refused and nothing is written. Never list a memory because it merely looks old or unused: that is not evidence."New value: +"Memories whose 'dies when' this work made true (decision/fact/reference received in full in a read). Never one that merely looks old."
    • changedInput schema / properties / fulfills / items / properties / how / description
      Previous value: -"What this work did that met the memory's kill condition — one sentence; it stays on the archived line forever."New value: +"What met the kill condition, in one sentence."
    • removedInput schema / properties / fulfills / items / properties / how / minLength
      Removed value: -1
    • changedInput schema / properties / fulfills / items / properties / memory / description
      Previous value: -"The #handle from the read (8 chars), or the full id"New value: +"The #handle from the read, or the full id."
    • removedInput schema / properties / fulfills / items / properties / memory / minLength
      Removed value: -1
    • removedInput schema / properties / fulfills / items / properties / memory / pattern
      Removed value: -"^#?(?:[0-9a-fA-F]{8,32}|[0-9a-fA-F]{8}-[0-9a-fA-F-]{27})$"
    • changedInput schema / properties / keep_whole / description
      Previous value: -"Set true only after you considered cutting an indivisible oversized residue. Arroway records this exception for calibration; it never truncates your text automatically."New value: +"true only after you considered cutting an indivisible oversized residue."
    • changedInput schema / properties / operational / description
      Previous value: -"Set true when this is the record of HOW THE WORK WENT — what failed, what you measured, what you corrected about your own earlier reading. It is kept in full for catching up at the start of a session, and stays OUT of the task-scoped read, so a long account never pushes a teammate's residue out of their block. Leave it out (the default) for what the team needs to know HAPPENED: that is what reaches other people while they work. This is a record of work, never a transcript of the conversation."New value: +"true for HOW the work went (failures, measurements, self-corrections): kept for catch-up, out of task reads."
    • changedInput schema / properties / project / description
      Previous value: -"Project slug. If it did not come from the person or from a read in this session, it is a guess: check it against the roster that opens arroway_catch_up before writing, because material from one circle must never land in another."New value: +"Project slug. Not from the person or a read this session? It is a guess: check the arroway_catch_up roster."
    • removedInput schema / properties / project / minLength
      Removed value: -1
    • removedInput schema / properties / project / pattern
      Removed value: -"^[a-z0-9]+(?:-[a-z0-9]+)*$"
    • removedInput schema / properties / source / minLength
      Removed value: -1
    • removedInput schema / properties / topic / minLength
      Removed value: -1
    • removedInput schema / x-maxSerializedLength
      Removed value: -131072
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a write (readOnlyHint=false) and non-idempotent. The description adds context annotations cannot carry: the entry is team-visible, and naming a memory in 'fulfills' retires it as a side effect of this call. It omits the practical consequence of idempotentHint=false (repeat calls duplicate the entry).

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?

Four sentences, front-loaded with the action and scope, with no filler or marketing language. Density is high but the parentheticals ('only a frozen catalog without that field may omit it') are cryptic enough that an agent may need a second pass.

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 9-parameter, no-output-schema write tool this covers the hard parts: what to include, the essence requirement, the retirement side effect, and backfill vs today's work. Remaining gaps are minor (duplicate-write behavior on retry, and how to recover from a bad project slug beyond the catch_up hint already in the schema).

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, but the description adds real meaning beyond it: it declares 'essence' effectively mandatory ('ALWAYS write the authored essence') even though the schema does not list it as required, and explains the semantic trigger for 'fulfills' as a kill condition rather than mere staleness.

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 ('Record ... in the team-visible daily log') scoped to a COMPLETED task, so the agent knows this is a post-completion write, not an in-flight note. The metaphor 'durable residue' and 'dated state included' add fog rather than precision, and no sibling (e.g. arroway_remember or arroway_retire) is named for contrast.

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?

Gives a clear trigger ('COMPLETED task') plus conditional instructions for edge cases: when a correction happened, when a read memory's 'dies when' became true. It does not, however, state when NOT to use it or which sibling to prefer for related writes, so the agent must infer the boundary with arroway_remember/arroway_close.

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

All Arroway toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources