Skip to main content
Glama

Arroway

by app.arroway
OverviewDiscussionsAdmin

Import a memory pack as proposals

arroway_import

Bring a memory pack made by arroway_export INTO a project. Everything lands as a PROPOSAL for the person's review and nothing is pinned, whatever the pack says. If any part is malformed, nothing is imported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packYesThe pack document itself; this server does not fetch URLs.
projectYesProject slug. Not from the person or a read this session? It is a guess: check the arroway_catch_up roster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / pack / description
      Previous value: -"The pack document itself, as it was written by arroway_export. Read the file and pass its contents — this server does not fetch URLs on your behalf."New value: +"The pack document itself; this server does not fetch URLs."
    • 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 / x-maxSerializedLength
      Removed value: -131072
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the write/non-idempotent profile, but the description adds real semantics beyond them: everything lands as a PROPOSAL, nothing is pinned regardless of pack content, and the import is atomic (any malformed part aborts the whole thing). It stops short of naming required permissions or a result shape.

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 tight sentences: purpose first, then the propose-not-pin guarantee, then the atomicity constraint. No filler and every clause adds information.

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 two-parameter write tool with no output schema, the description covers purpose, default state (proposals), and failure behavior (all-or-nothing). It omits required authorization and what the response reports, which keeps it just short of fully complete.

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 the schema already documents the pack and project parameters, including the roster cross-check guidance for project. The description only implicitly references the pack and target project, so the baseline 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 (import/bring) and resource (a memory pack) with explicit scope (INTO a project), and names the sibling that produces the input (arroway_export). An agent can distinguish this from siblings like arroway_remember without opening the schema.

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 establishes the context of use: importing a pack that originated from arroway_export. It does not, however, state exclusions or route the agent to any alternative tool for a different need.

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