Skip to main content
Glama
Sign In
Gameball MCP Server

Gameball MCP Server

by Ahmedelmonady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

getCustomerBalance

Retrieve a customer's current balance by providing their customer ID. Get the up-to-date points or wallet amount for any customer.

Instructions

🔒 Get balance

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

Input Schema

NameRequiredDescriptionDefault
expandNoComma-separated expansions: ti
customerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 carries the full burden for behavioral disclosure. The lock emoji is the only extra cue, but it is not a clear statement of authentication or side effects. The description does not mention permissions, response format, or any operational behavior.

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 extremely short, which is concise, but it is under-specified rather than optimally concise. It does not provide enough substantive information to be useful, so the brevity is not a strength.

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?

With no output schema, no annotations, and only a terse description, the tool is contextually incomplete. It does not explain what the balance represents, what the response looks like, or when this tool should be invoked relative to other customer-related tools.

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 coverage is 50% because only the 'expand' parameter has a description, and that description is cryptic ('ti'). The tool description adds no information about customerId or expand, failing to compensate for the schema's gaps or clarify parameter meaning.

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 uses a clear verb ('Get') and resource ('balance'), but the resource is generic and does not explicitly state 'customer balance' or the scope. The parameter name customerId implies the connection, but the description itself is vague and does not distinguish from sibling tools beyond the unique resource.

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?

There is no guidance on when to use this tool versus alternatives like getCustomer or getCustomerDetails. The description offers no context, prerequisites, or exclusions, leaving the AI agent to guess based on the name alone.

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