Skip to main content
Glama
Sign In
ClockNext MCP Server

ClockNext MCP Server

Official
by Clocknext-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ClockNext: archive plan

clocknext_archive_plan
DestructiveIdempotent

Deactivate a plan to retire it from selling, preserving customer history and existing subscriptions. Reversible via reactivation; does not cancel purchases.

Instructions

Deactivate a plan in your catalogue (sets isActive→false) — ClockNext's soft archive, NOT a delete. The plan and its history are kept and customers already on it are unaffected; it simply becomes unsellable and drops out of active lists. Reversible: reactivate via clocknext_update_plan with isActive:true (a full rewrite) — there is no separate un-archive tool. Use ONLY to retire a plan you no longer sell. This does NOT delete anything and is unrelated to cancelling a customer's purchase or ending a subscription.

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_plan"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.9/5.0
Behavior1/5

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

The description contradicts the annotation destructiveHint: true by claiming 'NOT a delete', that it's reversible, and that customers are unaffected. This is a serious inconsistency that could mislead an agent about the tool's destructive potential.

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?

The description is well-structured and front-loaded with the core action. Each subsequent sentence adds necessary context about consequences, reversibility, and exclusions without redundancy or wasted words.

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 simple one-parameter tool with no output schema, the description is exceptionally complete. It covers the operation's effect (sets isActive to false), side effects (history kept, customers unaffected), reversibility, and usage limits. The annotation contradiction is separate and does not reduce the textual completeness.

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?

The schema already provides 100% coverage for the single parameter, describing it as 'The plan id to deactivate (soft-archive — reversible, not a delete).' The description's mention of soft-archive and reversibility merely mirrors the schema, adding no new parameter-specific semantics.

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 opens with a specific verb ('Deactivate'), names the resource ('plan in your catalogue'), and explicitly contrasts with 'NOT a delete', making its purpose unmistakable. It distinguishes itself from other archive tools and from deletion operations.

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?

The description gives explicit when-to-use guidance ('Use ONLY to retire a plan you no longer sell'), clarifies what it is not for ('unrelated to cancelling a customer's purchase or ending a subscription'), and names the alternative for reactivation (clocknext_update_plan).

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