Skip to main content
Glama

Arroway

by app.arroway
OverviewDiscussionsAdmin

Export this project's norms as a memory pack

arroway_export
Read-onlyIdempotent

Export OUT of a project what it has DECIDED, as a portable memory pack for another team or project. Only sanctioned, live memories travel: a FINDING never was one, so findings stay and the answer tells you how many did. Nothing about people travels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesWhat this pack IS, in a few words: the first thing the other side reads.
topicNoOptional: export only the memories carrying this topic.
projectYesSlug of the project whose norms you are exporting
descriptionNoOptional: who it is for, what it assumes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"Optional: who this pack is for and what it assumes. Written for someone who has never seen this project."New value: +"Optional: who it is for, what it assumes."
    • removedInput schema / properties / description / maxLength
      Removed value: -4096
    • removedInput schema / properties / description / minLength
      Removed value: -1
    • changedInput schema / properties / name / description
      Previous value: -"What this pack IS, in a few words — the vertical, the practice, the playbook. It travels with the document and is the first thing the other side reads."New value: +"What this pack IS, in a few words: the first thing the other side reads."
    • removedInput schema / properties / name / minLength
      Removed value: -1
    • removedInput schema / properties / project / minLength
      Removed value: -1
    • removedInput schema / properties / project / pattern
      Removed value: -"^[a-z0-9]+(?:-[a-z0-9]+)*$"
    • changedInput schema / properties / topic / description
      Previous value: -"Optional: export only the memories carrying this topic. Use it to hand over one practice instead of everything a project knows."New value: +"Optional: export only the memories carrying this topic."
    • removedInput schema / properties / topic / minLength
      Removed value: -1
    • removedInput schema / x-maxSerializedLength
      Removed value: -131072
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description does not contradict them. It then adds genuinely non-obvious scope behavior: only sanctioned live memories travel, findings are deliberately excluded, the response reports how many were withheld, and no personal data is included.

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 dense sentences, front-loaded with the action and scope, each clause carrying real information about inclusion/exclusion rules. No filler or restatement of the tool name.

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?

With no output schema, the description usefully notes that the answer reports how many memories were skipped. It covers scope and side effects well, though it leaves the pack's form and how the receiving side consumes it unspecified.

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 every parameter (name, topic, project, description) is already documented in the schema. The description adds no syntax, defaults, or semantics beyond that, which is the expected baseline when the schema carries the load.

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 (export) and resource (a project's decided norms, packaged as a portable memory pack) with unusual precision about what is and is not included. It does not name the obvious inverse sibling arroway_import, so an agent must infer the pairing, but the intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied through 'for another team or project', which signals the transfer scenario, but there is no explicit when-to-use statement and no reference to arroway_import as the counterpart operation. An agent can guess the intent but gets no routing 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