Skip to main content
Glama

Update Challenge Checkpoint Dates

update_challenge_checkpoint_dates

Update checkpoint dates for a challenge. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "challengeId": "<challengeId>",
      "checkpointId": "<checkpointId>",
      "startTime": "<startTime>"
    },
    "name": "update_challenge_checkpoint_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
startTimeYesStart date and time (ISO 8601).
applyToAllNo
challengeIdYesChallenge ID, from list_products or a challenge tool for this business.
checkpointsNo
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
checkpointIdYesChallenge checkpoint ID, from the challenge checkpoint list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / challengeId / description
      Added value: +"Challenge ID, from list_products or a challenge tool for this business."
    • addedInput schema / properties / checkpointId / description
      Added value: +"Challenge checkpoint ID, from the challenge checkpoint list."
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / startTime / description
      Added value: +"Start date and time (ISO 8601)."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly=false and destructive=false, and the description adds substantial context beyond them: plan-based entitlement gating, a mandatory verification call, disclosure of grace-period warnings and resubscribe links, and an explicit stop condition. It does not explain what happens to checkpoints not listed, whether date changes are reversible, or any validation rules on the new times.

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?

The purpose is front-loaded in sentence one, and the following sentences form a coherent permission/guardrail sequence with no filler. It is dense but every sentence carries an operational instruction, though the permissions preamble is longer than the functional description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete on the access-control dimension, which is clearly the highest-risk part of this mutation. However, for a write tool with a nested checkpoints array, an applyToAll switch, and no output schema, it says nothing about update semantics, precedence between applyToAll and checkpointId, or validation constraints — the agent must derive all of that from the schema.

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

Parameters2/5

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

The description adds no meaning for any of the six parameters; it is entirely about permissions. Schema coverage is 67%, leaving applyToAll and the checkpoints array (including endTime and isWelcomeCheckpoint) undocumented anywhere, and applyToAll in particular is ambiguous — whether it overrides checkpointId and writes dates across the whole challenge is not stated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource: 'Update checkpoint dates for a challenge,' which an agent can map directly to the tool's effect. It does not differentiate from closely named siblings such as calculate_challenge_checkpoint_dates, bulk_update_challenge_checkpoints, or update_challenge_checkpoint_event, so the agent must infer the distinction from names alone.

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, actionable preconditions: check business permissions, call check_business_tool_access before collecting inputs, and never proceed when access is blocked. It also gives a hard exclusion (FREE businesses cannot use this tool, regardless of individual feature rows). It omits guidance on when to use this tool instead of calculate_challenge_checkpoint_dates or bulk_update_challenge_checkpoints, which is the remaining gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources