Skip to main content
Glama

Duplicate Challenge

duplicate_challenge

Duplicate a challenge. Requires confirm set to DUPLICATE. 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>"
    },
    "name": "duplicate_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action.
challengeIdYesChallenge ID, from list_products or a challenge tool for this business.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
targetChallengeTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / 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 / confirm / description
      Added value: +"Explicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false/destructiveHint=false about a tool that creates new data; the description adds the tier gating, the mandatory check_business_tool_access handshake, and the grace-period/resubscribe warning flow. It does not disclose what a duplicate actually copies (participants, dates, checkpoints) or whether the source is left untouched, which leaves one real behavioral gap.

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?

Purpose is front-loaded in the first sentence and the rest is a usable ordered checklist. There is mild duplication between 'Before offering this action... check business permissions' and 'Call check_business_tool_access before collecting inputs', which costs a point.

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 access-gating story is thorough, which is the hardest part of this tool. But with no output schema, the description never says what the caller gets back (a new challenge ID? draft status?) or what state the duplicate lands in, so an agent can't chain the result confidently.

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 is 75%, so the baseline is 3. The description does add high-value meaning for `confirm` — it specifies the literal DUPLICATE, where the schema example misleadingly shows DELETE — but `targetChallengeType` (the one enum parameter, allowing a type change on duplication) is never explained anywhere.

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?

States a specific verb+resource ('Duplicate a challenge'), which clearly separates it from create_challenge, update_challenge, and duplicate_challenge_checkpoint without naming them. No sibling is named explicitly, so it stops short of a 5.

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?

Gives explicit preconditions and routing: check business permissions first, call check_business_tool_access before collecting inputs, and do not offer the action at all for FREE businesses. It also names the exact condition that blocks use ('never proceed when access is blocked'), which is a true when-not rule.

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