Skip to main content
Glama
Sign In
Gameball MCP Server

Gameball MCP Server

by Ahmedelmonady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

getCustomerTierProgress

Retrieve a customer's tier progress, showing points accumulated and points needed to reach the next loyalty tier. This enables tracking customer advancement.

Instructions

🔒 Get tier-progres

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": {
      "customerId": "<customerId>"
    },
    "name": "getCustomerTierProgress"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoIf the lang header is provided
expandNoComma-separated expansions: ti
customerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

No annotations exist, and the description only includes a lock emoji, which hints at authentication but doesn't explain permissions, side effects, or return behavior. The verb 'get' implies read-only, but that's also implied by the name.

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 fragment with a typo ('progres') and an unnecessary emoji. It's too terse to be informative.

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

Completeness1/5

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

Without an output schema or annotations, the description should explain what the response contains, but it merely states the obvious, leaving the tool's behavior and result format unexplained.

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 schema provides descriptions for lang and expand, but customerId has none. The description adds no parameter semantics, and the expand value 'ti' remains undefined.

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

Purpose2/5

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

The description '🔒 Get tier-progres' is essentially a restatement of the tool name with a typo, providing no additional purpose clarification. It doesn't specify what tier progress means or how it differs from sibling progress tools.

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?

No usage guidance is provided; the description doesn't mention when to use this tool versus getCustomerCampaignsProgress or getTiersConfigurations.

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

Deploy Server

Other Tools