Skip to main content
Glama
Sign In
ClockNext MCP Server

ClockNext MCP Server

Official
by Clocknext-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ClockNext: update credit

clocknext_update_credit
Idempotent

Replace a credit by ID with a complete new definition — a full rewrite that clears omitted fields. Pass current values to modify only active state or deliberately re-point agentKey.

Instructions

Replace a credit by id with its COMPLETE new definition — a full rewrite, NOT a partial patch (omitted fields are cleared). Pricing is re-grounded from the models mixer you pass (same as create). To only flip active state, pass the current values plus isActive. Read the current credit with clocknext_get_credit first. Changing agentKey re-points which runtime signals map here — do it deliberately.

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": "<name>",
      "agentKey": "<agentKey>",
      "models": "<models>",
      "marginPercent": "<marginPercent>"
    },
    "name": "clocknext_update_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe credit id to update.
nameYesCredit name.
modelsYesThe model mixer that GROUNDS the price — one or more enabled catalog models with avg tokens + input/output/cache split. The tool reads live prices and computes the base cost; you never type a raw price.
agentKeyYesLowercased stable key you report credit usage against (sent as `agentKey` when recording usage). The credit's durable identity.
descriptionNoOptional human-readable description.
marginPercentYesMarkup over the computed base cost, as a percent (e.g. 100 = double the base = pricePerCredit).
tokensPerCreditNoHow many tokens equal one credit (defaults to 0). Governs how usage draws the credit down.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses destructive semantics: omitted fields are cleared, pricing is re-grounded, and changing agentKey re-points runtime signals. This is exactly the kind of behavioral context annotations do not provide, and it does not contradict readOnlyHint/idempotentHint.

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?

Three sentences front-load the most important fact (full rewrite, not patch), then add prerequisites and cautions without redundancy. Every sentence carries operational 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?

For a 7-parameter mutation with no output schema, the description covers destructive behavior, prerequisite reads, pricing behavior, and the agentKey risk. It loses a point because the isActive advice conflicts with the closed input schema and the return/result shape is not mentioned, but overall it is unusually thorough.

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?

Schema covers all parameters, so baseline is 3. The description adds meaning by explaining the models mixer re-grounds pricing and that agentKey is the durable identity whose change deliberately re-points signals. However, it references 'isActive' which is not present in the schema, slightly muddying parameter guidance.

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?

Description opens with 'Replace a credit by id with its COMPLETE new definition', giving a specific verb and resource and distinguishing it from a partial patch. It also notes pricing is re-grounded 'same as create', which orients it among create/update/archive siblings.

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?

It gives an explicit prerequisite: read the current credit with clocknext_get_credit first. It also gives a concrete use case for toggling active state. It does not name alternative tools to avoid, but the full-rewrite framing makes the update-vs-create distinction clear.

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