Skip to main content
Glama
Sign In
Gameball MCP Server

Gameball MCP Server

by Ahmedelmonady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

getCustomerReferrals

Retrieve customer referral lists with pagination and limit options. Get details of referred friends for any customer by ID.

Instructions

🔒 Get referral

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": "getCustomerReferrals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoSpecifies the number of friend
customerIdYes
startAfterNoSpecifies the page will start

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior1/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It provides none: no mention of pagination, sorting, side effects, or response shape. The lock emoji is not explained and adds no clarity.

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 under-specified rather than concise. '🔒 Get referral' is a brief phrase but lacks essential structure and information. It is too short to be considered appropriately sized for a tool with three parameters and no annotations.

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?

For a tool with three parameters, no output schema, and no annotations, this description is profoundly incomplete. It fails to explain what referrals are, how pagination works, or what the response contains, leaving the agent without adequate context.

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 meaning to the parameters. While the schema documents 67% of parameters, those descriptions are truncated ('Specifies the number of friend', 'Specifies the page will start '). The tool description does not clarify customerId, limit, or startAfter beyond what the incomplete schema already provides.

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 referral' is vague, stating only a verb and a resource without scope or detail. It does not clarify whether a single referral or a list is returned, nor does it differentiate from siblings like getCustomerReferralsCount. The tool name helps, but the description itself lacks specificity.

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 does not indicate when to use this tool versus related tools such as getCustomerReferralsCount or getReferralsConfigurations, nor does it mention any prerequisites, alternatives, or exclusions.

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