Skip to main content
Glama
Sign In

Arroway

by app.arroway
OverviewDiscussionsAdmin

Move a memory or log entry to another project

arroway_move

Move something to the project it belongs in. A memory is only PROPOSED: the change waits for the person's review, because moving changes who sees it. A log entry you wrote moves at once, text unchanged.

Input Schema

NameRequiredDescriptionDefault
whyYesWhy it belongs there and not here. For a memory, the person decides on this sentence.
memoryYes#handle of the memory or log entry, from a read or arroway_search_log
targetYesSlug of the project you believe it belongs to
projectYesSlug of the project it is in TODAY

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed11 schema fields changed
    • changedInput schema / properties / memory / description
      Previous value: -"#handle of the memory, from a read"New value: +"#handle of the memory or log entry, from a read or arroway_search_log"
    • 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})$"
    • changedInput schema / properties / project / description
      Previous value: -"Slug of the project the memory is in TODAY"New value: +"Slug of the project it is in TODAY"
    • removedInput schema / properties / project / minLength
      Removed value: -1
    • removedInput schema / properties / project / pattern
      Removed value: -"^[a-z0-9]+(?:-[a-z0-9]+)*$"
    • removedInput schema / properties / target / minLength
      Removed value: -1
    • removedInput schema / properties / target / pattern
      Removed value: -"^[a-z0-9]+(?:-[a-z0-9]+)*$"
    • changedInput schema / properties / why / description
      Previous value: -"Why it belongs there and not here — the human decides on this sentence"New value: +"Why it belongs there and not here. For a memory, the person decides on this sentence."
    • removedInput schema / properties / why / minLength
      Removed value: -1
    • removedInput schema / x-maxSerializedLength
      Removed value: -131072
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only say this is a non-read-only, non-destructive, closed-world tool; the description adds the crucial fact that memory moves are pending proposals requiring the person's review while log-entry moves are immediate and leave text unchanged. It also supplies the rationale ("moving changes who sees it"). What remains undisclosed is the effect on the source project and what the call returns for each mode.

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 short sentences, zero filler, with the most consequential fact (proposal vs. immediate) front-loaded right after the purpose statement.

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 four-parameter mutation tool with full schema coverage and no output schema, the description covers the essential behavioral divergence between modes. It stops short of describing the outcome of each call, which an agent might want to know when confirming a move succeeded or is pending.

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% and all four parameters carry their own descriptions, including the meaning of why for memory moves. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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?

The description names a specific verb and resource ("Move something to the project it belongs in") and then immediately resolves the vague "something" into the two resources it covers: a memory or a log entry. The two-mode split makes it unambiguous what gets moved, though the opening line alone is less precise than the two that follow.

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?

It clearly separates the two cases an agent must choose between: memory moves are proposed and wait for human review, log entries move immediately. It does not name alternatives such as creating a new entry with arroway_remember or when a move should be avoided, so there is no exclusion guidance.

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