Gameball MCP Server

Overview Schema Source Related Servers Discussions Admin

getCampaignsConfigurations

Retrieve reward campaign configurations for a customer, product SKU, or collection. Use these settings to apply the correct rewards and promotions.

Instructions

Get reward-campaign

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getCampaignsConfigurations"
  }
}

Input Schema

Name	Required	Description
`lang`	No	If the lang header is provided
`customerId`	No
`productSku`	No	The SKU (Stock Keeping Unit) o
`collectionId`	No	Unique identifier for a produc

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.3/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden of disclosing behavioral traits. It only says 'Get reward-campaign' and does not mention return format, pagination, permissions, or any side effects, which is insufficient for a tool with no structured behavioral metadata.

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

Conciseness2/5

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

The description is a short fragment 'Get reward-campaign', which is under-specification rather than conciseness. It lacks a complete sentence and omits crucial context, making it more of a label than a useful description.

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?

For a tool with 4 parameters, no output schema, and no annotations, the description is critically incomplete. It does not explain the response structure, filtering logic, or how this tool fits into the broader reward-campaign system, leaving substantial gaps for an AI agent.

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 information about parameters. Although schema coverage is 75%, some parameter descriptions are truncated (e.g., 'The SKU (Stock Keeping Unit) o') and 'customerId' has no description. The tool description does nothing to clarify parameter usage or compensate for the gaps.

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

Purpose3/5

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

The description 'Get reward-campaign' provides a verb and a resource, indicating it retrieves something related to reward campaigns. However, it is vague and doesn't explicitly mention 'configurations' as the name does, nor does it distinguish itself from sibling tools like getTiersConfigurations or getReferralsConfigurations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus alternatives. It doesn't specify contexts, prerequisites, or exclusions, leaving the agent without enough information to decide among the many similar configuration-related tools.

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

Deploy Server