Skip to main content
Glama

Arroway

by app.arroway
OverviewDiscussionsAdmin

Retire a sanctioned memory, on the person's instruction

arroway_retire
Destructive

Retire a SANCTIONED memory when the person told you in this conversation to remove it and nothing replaces it. Archived, never deleted. With a corrected version, use arroway_remember supersedes_id; for your own pending proposal, arroway_withdraw.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whyNoOptional: what the person said made it obsolete, in their terms.
memoryYesThe memory to retire — the #handle from a read is enough.
projectYesProject slug.
decided_by_humanYesMust be true, and only when the person explicitly told you to remove it IN THIS CONVERSATION.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / decided_by_human / description
      Previous value: -"Must be true, and only when the person explicitly told you to remove it IN THIS CONVERSATION. Never infer it, never set it because it looks obsolete to you: a sanctioned memory is theirs. Without their word, say it is a gesture for them to make in the panel."New value: +"Must be true, and only when the person explicitly told you to remove it IN THIS CONVERSATION."
    • removedInput schema / properties / memory / minLength
      Removed value: -1
    • removedInput schema / properties / memory / pattern
      Removed value: -"^#?(?:[0-9a-fA-F]{8,32}|[0-9a-fA-F]{8}-[0-9a-fA-F-]{27})$"
    • removedInput schema / properties / project / minLength
      Removed value: -1
    • removedInput schema / properties / project / pattern
      Removed value: -"^[a-z0-9]+(?:-[a-z0-9]+)*$"
    • changedInput schema / properties / why / description
      Previous value: -"Optional: what the person said made it obsolete, in their terms. It stays on the archived line forever; if omitted, the history explicitly says no reason was declared."New value: +"Optional: what the person said made it obsolete, in their terms."
    • removedInput schema / properties / why / minLength
      Removed value: -1
    • removedInput schema / x-maxSerializedLength
      Removed value: -131072
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description adds the crucial nuance that the memory is 'Archived, never deleted' — a distinction the destructive hint alone would leave ambiguous. It also discloses the precondition that the instruction must be sanctioned and given in the current conversation.

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?

Two tightly packed sentences with no filler. The core action and its constraint come first, and the disambiguation to siblings follows, which is the right front-loading for a routing-sensitive tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation tool with no output schema, the description covers the action, the precondition, the postcondition ('archived, never deleted'), and the alternatives. Nothing an agent needs to invoke it correctly is missing.

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 all four parameters (project, memory, why, decided_by_human) are already documented in the schema. The description reinforces the decided_by_human condition but adds no format or syntax detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb (retire) and resource (a SANCTIONED memory), plus the gating condition (person instructed removal in this conversation). It also names the two sibling tools that handle the adjacent cases, so an agent can distinguish it without opening any schema.

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?

Explicit when-to-use (person said to remove it, nothing replaces it) and explicit when-not (use arroway_remember with supersedes_id for a corrected version; use arroway_withdraw for your own pending proposal). The routing to alternatives is unambiguous.

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 Every Agent Can ShareAgents share what they learn, hand off work, and keep 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