Skip to main content
Glama
Sign In
ClockNext MCP Server

ClockNext MCP Server

Official
by Clocknext-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ClockNext: subscribe customer to a plan

clocknext_create_purchase

Subscribe a customer to a plan to activate it, enabling usage-based billing for that customer.

Instructions

Subscribe a customer to a plan (a 'purchase') — this is what activates the plan for that customer. A usage signal only prices if the customer has an active plan whose components match the meter (credit / outcome / unit), so do this after clocknext_create_customer + clocknext_create_plan. Used to wire up a dummy customer before firing test signals.

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": {
      "customerId": "<customerId>",
      "planId": "<planId>"
    },
    "name": "clocknext_create_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoInternal notes for this purchase.
planIdYesThe plan id to subscribe them to (from clocknext_create_plan / _list_plans).
customerIdYesThe ClockNext customer id (from clocknext_create_customer / _list_customers).
autoPaymentNoCharge automatically when the invoice is due.
billingDateNoYYYY-MM-DD. Defaults to today; must be a valid, non-past date.
voidAfterMinutesNoAuto-void the purchase if it stays unpaid after N minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate a non-read-only (readOnlyHint=false) and non-idempotent (idempotentHint=false) operation. The description adds behavioral context by explaining that the plan becomes active and that usage signals only price when an active plan's components match the meter. This goes beyond the annotations, though it doesn't discuss side effects like billing or return values.

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 two sentences, front-loaded with the core action, and includes both purpose and context without any redundant wording. Every clause adds value.

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?

Given the tool's complexity (6 params, 2 required), the schema fully documents parameters, and the description provides clear purpose, prerequisites, and a use case. The only gap is that no output schema exists and the description does not mention return values, but for a mutating subscription tool, this is a minor omission.

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 for parameters is 100%, meaning all six parameters have descriptions in the input schema. The description itself does not add parameter-specific semantics, but it does mention the concept of 'active plan' indirectly. Since the schema covers parameters thoroughly, the baseline of 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 clearly states the verb and resource: 'Subscribe a customer to a plan', and elaborates that this is a purchase that activates the plan. It distinguishes from sibling tools like clocknext_create_plan and clocknext_create_customer by specifying the action is about subscription/activation, not creation of entities.

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

Usage Guidelines4/5

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

The description gives explicit sequencing: 'do this after clocknext_create_customer + clocknext_create_plan' and a concrete use case: 'wire up a dummy customer before firing test signals'. However, it does not explicitly mention when not to use this tool or list alternative tools, which prevents a perfect score.

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