Skip to main content
Glama
Sign In
ClockNext MCP Server

ClockNext MCP Server

Official
by Clocknext-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ClockNext: archive outcome

clocknext_archive_outcome
DestructiveIdempotent

Deactivate an outcome type to retire it from active use, preserving history and existing plans. Soft archive only, not a delete—reversible.

Instructions

Deactivate an outcome TYPE in your catalogue (sets isActive→false) — ClockNext's soft archive, NOT a delete. The outcome, its steps, and any in-flight or completed history are kept; existing plans and outcomes already in progress are unaffected. It simply can't be added to new plans and drops out of active lists. Reversible: reactivate via clocknext_update_outcome with isActive:true (a full rewrite) — there is no separate un-archive tool. Use ONLY to retire an outcome you no longer sell. This does NOT delete anything and is unrelated to archiving a customer or ending a purchase.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "clocknext_archive_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe outcome id to deactivate (soft-archive — reversible, not a delete).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.9/5.0
Behavior5/5

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

The description goes well beyond the annotations (readOnly=false, destructive=true, idempotent=true) by explaining what exactly is kept (outcome, steps, history), what is affected (new plans only), reversibility, and that it's not a delete. It adds context about the soft-archive semantics without contradicting 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.

Conciseness5/5

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

Despite being multi-sentence, every sentence contributes essential information: the operation, what's preserved, what's affected, reversibility, and exclusions. It is front-loaded with the main action and avoids redundancy.

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?

Given the tool's complexity (soft archive, reversible, with side effects), the description covers all necessary context: what happens, what doesn't happen, how to reverse, and when to use. With no output schema, it doesn't need to explain return values, and the annotations already handle idempotency and destructiveness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers the single parameter (id) with a description. The description adds value by clarifying that the id refers to an outcome TYPE and explains the effect (sets isActive→false), which supplements the schema description.

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 explicitly defines the operation with a specific verb and resource: 'Deactivate an outcome TYPE' and clarifies it's a soft archive, not a delete. It clearly distinguishes from sibling tools like clocknext_archive_plan and clocknext_archive_credit by stating it's not related to archiving customers or ending purchases.

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?

Provides explicit when-to-use guidance ('Use ONLY to retire an outcome you no longer sell'), when-not-to-use context ('unrelated to archiving a customer or ending a purchase'), and an explicit alternative for reversing (reactivate via clocknext_update_outcome with isActive:true).

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