Skip to main content
Glama
JAAvila-Of

vivac

by JAAvila-Of
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Park a node: not now

vivac_park

Suspend a work node without abandoning it, with an optional return date so it resurfaces in the brief later. Use when someone says not now.

Instructions

Suspend a node without abandoning it: it drops off the stack and becomes something a later session is told not to touch. Given an until day, the brief puts it back in front of whoever opens a session on or after that day; it stays parked until somebody takes it back. Call it when the person says not now, or when work is stuck on something outside this session -- never as a substitute for vivac_pop on something that is simply finished. What is put off has to be a node first: if it is not in the tree yet, file it with vivac_add and park that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe node to park. Defaults to the current focus.
untilNoYYYY-MM-DD, a day after today: the node comes back in vivac_brief under BACK FROM PARKED on that day. Leave it out to park with no return date.
reasonNoWhy it waits: the person's own words when they said not now. Read back verbatim under DO NOT TOUCH NOW.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.4
    • addedInput schema / properties / until
      Added value: +{
+  "description": "YYYY-MM-DD, a day after today: the node comes back in vivac_brief under BACK FROM PARKED on that day. Leave it out to park with no return date.",
+  "type": "string"
+}
  2. First observedv0.17.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the safety profile (not read-only, not idempotent, not destructive) and leave the lifecycle opaque. The description fills that gap: the node stays parked until reclaimed and resurfaces in vivac_brief under BACK FROM PARKED on/after the until day, which is meaningful state-change context beyond the annotations.

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?

Four sentences, all substantive and front-loaded, with the core 'not now, not finished' idea leading. Slightly verbose in the final routing sentence but every clause carries decision-relevant information.

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 mutation tool with no output schema, the description covers the full lifecycle an agent needs: what happens to the node, how it returns (BACK FROM PARKED), how long it stays parked, and how to handle a node not yet in the tree. Nothing essential 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 coverage is 100%, so the schema already documents id, until, and reason in detail, including the YYYY-MM-DD format and the BACK FROM PARKED return behavior. The description restates the same conceptual behavior rather than adding new syntax or constraints, so the baseline 3 is appropriate.

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?

The description states a specific action (suspend a node without abandoning it) and its immediate effect (drops off the stack, becomes something a later session is told not to touch). It explicitly distinguishes itself from siblings vivac_pop and vivac_add, so an agent can disambiguate 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?

It gives explicit triggers ('when the person says not now, or when work is stuck on something outside this session'), an explicit exclusion ('never as a substitute for vivac_pop on something that is simply finished'), and a prerequisite routing ('if it is not in the tree yet, file it with vivac_add and park that'). Nothing about when to choose this tool is left to inference.

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

Deploy Server

Other Tools