Skip to main content
Glama

Log what a task left behind

arroway_log

Record the durable residue of a COMPLETED task: what someone arriving later needs in order not to redo it. ALWAYS write the authored essence (only a frozen catalog without that field may omit it). If a read memory's 'dies when' came true, name it in fulfills.

Input 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. 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: kept for catch-up, out of task reads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / fulfills / description
      Previous value: -"Memories whose 'dies when' this work made true (decision/fact/reference received in full in a read). Never one that merely looks old."New value: +"Memories whose 'dies when' this work made true. Never one that merely looks old."
    • removedInput schema / properties / fulfills / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / operational / description
      Previous value: -"true for HOW the work went (failures, measurements, self-corrections): kept for catch-up, out of task reads."New value: +"true for HOW the work went: kept for catch-up, out of task reads."
  2. 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
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already establish a non-read-only, non-destructive, closed-world operation. The description adds durability and lifecycle-linkage context, but it does not explain the side effects of listing a memory in fulfills, whether log entries can be revised, or what the call returns.

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

Conciseness5/5

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

Three compact sentences front-load the purpose and then cover the two special recording rules. There is no filler or repeated background material, and each sentence has a distinct operational function.

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?

Together with the richly documented schema, the description supplies enough purpose, scope, and special parameter guidance for correct invocation. The absence of an output schema makes the missing return-behavior information more noticeable, and sibling differentiation and the consequences of fulfills remain underexplained.

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 description coverage is 100%, but the description still adds meaningful cross-field semantics: essence is effectively mandatory despite not being schema-required, with a narrow frozen-catalog exception. It also reinforces the condition for populating fulfills, although that condition largely repeats the schema.

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?

“Record the durable residue of a COMPLETED task” gives a specific verb, resource, and scope, and the following clause clarifies that the record should prevent later duplication of work. It does not explicitly distinguish this tool from siblings such as arroway_remember or arroway_close.

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?

The description clearly says to use it for a completed task and gives conditional guidance for essence and fulfills. It lacks explicit routing guidance for when another sibling should be used instead, or whether logging is required as part of a particular task-completion workflow.

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