Nas.com

Award Challenge Checkpoint Points

award_challenge_checkpoint_points

Award points to a participant for a challenge checkpoint. 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>",
      "participantId": "<participantId>",
      "checkpointId": "<checkpointId>",
      "awardType": "<awardType>",
      "notify": "<notify>"
    },
    "name": "award_challenge_checkpoint_points"
  }
}

Input Schema

Name	Required	Description
`notify`	Yes	Whether to notify the participant.
`reason`	No
`awardType`	Yes	Size of the points award; use one of the allowed values.
`challengeId`	Yes	Challenge ID, from list_products or a challenge tool for this business.
`communityId`	Yes	Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
`checkpointId`	Yes	Challenge checkpoint ID, from the challenge checkpoint list.
`participantId`	Yes	Challenge participant ID, from a challenge participant listing.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 10, 2026

addedInput schema / properties / awardType / description

Added value: +"Size of the points award; use one of the allowed values."

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 / notify / description

Added value: +"Whether to notify the participant."

addedInput schema / properties / participantId / description

Added value: +"Challenge participant ID, from a challenge participant listing."

First observedNov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only declare that this is a non-destructive write to a closed system; the description adds a meaningful behavioral gate the annotations cannot express, namely that FREE businesses are blocked regardless of individual feature rows and that grace-period warnings plus a resubscribe link must be surfaced. It still omits post-call behavior such as idempotency, duplicate-award handling, or what the participant notification entails.

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 the first sentence, followed by gating instructions in a logical order. There is mild redundancy between 'Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs,' which costs it a point.

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 tool with no output schema, the description covers the highest-risk missing context: preconditions, entitlement exclusions, and blocking behavior. It is not fully complete because it never says what a successful award produces or how awardType sizes translate into actual points.

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 description coverage is 86%, so the schema already documents communityId, challengeId, participantId, checkpointId, awardType, and notify, and the description adds no further parameter meaning. Baseline 3 applies since the schema does the heavy lifting; the description only inherits the 'requesting its inputs' framing.

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 opening sentence states a specific verb (award) and resource (points to a participant for a challenge checkpoint), which is enough for an agent to recognize the operation. It does not explicitly distinguish itself from the adjacent reset_challenge_checkpoint_points sibling, so sibling differentiation is left implicit.

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 concrete when-to-use/when-not-to-use rules: check business permissions first, call check_business_tool_access before collecting inputs, and never proceed when access is blocked. What is missing is routing guidance among similar tools (e.g., when to reset instead of award), so it stops short of a 5.

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

All Nas.com tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.