Skip to main content
Glama

Get Challenge End State

get_challenge_end_state
Read-only

Get challenge end-state counts and winners. 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": "get_challenge_end_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the extra value here is the entitlement rules: FREE businesses are blocked regardless of feature rows, and grace-period warnings plus the verified resubscribe link must be shown. That is genuinely useful behavior beyond the annotations, though it says nothing about response shape or whether counts are paginated or time-bounded.

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?

The purpose is front-loaded in one short sentence, but the access gating repeats itself: 'Before offering this action or requesting its inputs, check business permissions' and 'Call check_business_tool_access before collecting inputs' say the same thing twice, and 'never proceed when access is blocked' restates the obvious.

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

Completeness5/5

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

For a simple two-parameter read-only tool with full schema coverage and no output schema, the description covers the one thing the structured fields cannot: the entitlement gate and the required access-check call. Nothing an agent needs in order to invoke it correctly is absent.

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 100%, and the schema already explains that challengeId comes from list_products or a challenge tool and that communityId must be a real business ID. The description adds no further meaning about either parameter, so the baseline 3 applies.

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 gives a specific verb and resource: retrieve challenge end-state counts and winners. That is enough to tell it apart from mutation siblings like declare_challenge_winners or update_challenge, though it does not explicitly contrast with get_challenge, which covers adjacent data.

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 supplies a concrete prerequisite workflow: check business permissions and call check_business_tool_access before collecting inputs, and do not proceed if access is blocked. What is missing is guidance on when an agent should reach for this tool versus get_challenge or get_challenge_participant.

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