Skip to main content
Glama

List Challenge Participants

list_challenge_participants
Read-only

List participants for a challenge with manager filters and checkpoint paging. 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": "list_challenge_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number to return, starting at 1.
sortByNoField to sort results by.
pageSizeNoNumber of results per page.
sortOrderNoSort direction for the results.
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.
searchStringNoText to search for.
specificPageNo
checkpointLimitNo
checkpointOffsetNo
checkpointIdStartNo
filterCheckpointIdsNo
checkpointIndexStartNo
filterChallengeStatusesNo
filterCheckpointStatusesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 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 / pageNo / description
      Added value: +"Page number to return, starting at 1."
    • addedInput schema / properties / pageSize / description
      Added value: +"Number of results per page."
    • addedInput schema / properties / searchString / description
      Added value: +"Text to search for."
    • addedInput schema / properties / sortBy / description
      Added value: +"Field to sort results by."
    • addedInput schema / properties / sortOrder / description
      Added value: +"Sort direction for the results."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine, non-obvious context about business-tier entitlement and grace-period messaging. It says nothing about pagination behavior, result limits, or what happens when checkpoints are filtered, despite advertising 'checkpoint paging'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in one sentence, which is good. The remaining four sentences are repetitive permission boilerplate ('check business permissions' and 'Call check_business_tool_access before collecting inputs' overlap), and no space is left for the parameter detail an agent actually needs.

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

Completeness2/5

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

This is a 15-parameter listing tool with no output schema and near-half schema documentation, so the description bears heavy burden. It spends all of its length on entitlement gating and none on the paging/filter mechanics that make the tool usable correctly.

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?

Schema description coverage is only 47%, and the description does not compensate: eight parameters (specificPage, checkpointLimit, checkpointOffset, checkpointIdStart, filterCheckpointIds, checkpointIndexStart, filterChallengeStatuses, filterCheckpointStatuses) are undocumented in both places. 'Checkpoint paging' is mentioned but the cursor/offset interaction is never explained.

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?

Opens with a specific verb and resource ('List participants for a challenge') and adds scope hints ('manager filters and checkpoint paging'), which separates it from the singular get_challenge_participant and the mutate-style add/remove siblings. It stops short of naming those siblings explicitly, but the read-only list framing is clear.

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?

Gives concrete when-not conditions: FREE businesses are excluded regardless of feature rows, and access must be verified via check_business_tool_access before collecting inputs. It also prescribes sequencing (show grace-period warning, verified resubscribe link, halt when blocked). No guidance on choosing this over get_challenge_participant or the filter-based list siblings, which keeps it from a 5.

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