Skip to main content
Glama

busabase

by com.busabase
OverviewDiscussionsAdmin

Archive a node (reversible; the node moves to Trash)

node_archive

Archive a node (reversible; the node moves to Trash)

This is the only way to move a node into the archived state, and it is reversible — the node appears in the Trash view and can be restored. Review is permission-aware, decided server-side: it archives immediately when your key has write access on the node and lands as a pending ChangeRequest otherwise. Pass requireReview to always propose instead. Do NOT use node_purge to remove a node: purge is permanent and only accepts a node that has ALREADY been archived by this task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesId of the node to archive.
messageNoExplanation for the human reviewer of why this node should go.
playbookNoOptional. The playbook you are following, as `kind:nodeId[:key]` from playbooks_search (e.g. `prompt:nod_123:log-visit`). Recorded on the change request so the person can see which playbook produced it.
autoMergeNoArchive immediately if you have write access. Not a permission override — a changeRequest-level key still gets a pending CR. Default is permission-aware: archive when you can, otherwise propose.
submittedByNoProducer label recorded on the change.
requireReviewNoAlways propose a pending ChangeRequest instead of archiving, even with write access.
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / playbook
      Added value: +{
+  "description": "Optional. The playbook you are following, as `kind:nodeId[:key]` from playbooks_search (e.g. `prompt:nod_123:log-visit`). Recorded on the change request so the person can see which playbook produced it.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare destructiveHint: false, which aligns with the description's statement that archiving is reversible and moves the node to Trash — no contradiction. The description adds valuable context beyond annotations: reversibility, Trash view appearance, permission-aware server-side review decision, and the requireReview override for proposing instead of acting.

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

Conciseness4/5

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

Moderate length but every sentence earns its place: the title front-loads the essential (reversible, to Trash), the body covers mechanism and the critical purge warning. Slightly verbose in the review-permission explanation but no filler.

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 7-parameter tool with no output schema, the description covers the core contract (reversibility, permission-aware behavior, override option) and the dangerous sibling. The parameter details are already fully documented in the schema, so little is left uncovered for an agent to make a correct call.

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 all 7 parameters in detail; the baseline of 3 applies. The description adds a small layer on top by explaining requireReview's role ('always propose instead') and the rationale for message (for the human reviewer), but it does not redefine or enrich parameters beyond what the schema already states.

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 (archive) + resource (node) and explicitly declares it is 'the only way to move a node into the archived state.' It differentiates itself from the sibling node_purge, clarifying that the two tools have distinct roles so an agent can disambiguate without opening either 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?

Gives explicit when-to-use conditions (permission-aware immediate archive vs. pending ChangeRequest), the override path (requireReview), and an explicit when-not: 'Do NOT use node_purge to remove a node' with the reason why (permanent, only accepts already-archived nodes). No inference required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All busabase toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources