Skip to main content
Glama
Sign In
Gameball MCP Server

Gameball MCP Server

by Ahmedelmonady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

deleteCustomer

Delete a customer from Gameball by their customer ID to remove their profile and associated data.

Instructions

🔒 Delete customer

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

Input Schema

NameRequiredDescriptionDefault
customerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely repeats the tool name ('Delete customer') without revealing that deletion is likely irreversible, may cascade to associated data, or requires specific permissions. The description adds zero behavioral context beyond the literal action.

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

Conciseness4/5

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

The description is extremely concise ('🔒 Delete customer'), with every word (except the decorative lock emoji) contributing meaning. The emoji is extraneous and does not aid understanding, so it loses one point.

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 destructive operation with no annotations, no output schema, and an undocumented parameter, the description is severely incomplete. It fails to mention effects (e.g., permanent deletion), return values, or error behavior, offering no safety net for an AI agent invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one required parameter (customerId) with no description, and schema description coverage is 0%. The description does not attempt to compensate, failing to mention that customerId identifies the customer to be deleted or what format it should take.

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

Purpose5/5

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

The description 'Delete customer' clearly states the action (delete) and the resource (customer), which is specific enough to distinguish it from sibling tools like createCustomer and getCustomer. The verb is explicit and the resource is unambiguous.

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 provides no guidance on when to use this tool, any prerequisites (e.g., not deleting active customers, irreversibility), or alternatives. It simply states the action with no context for appropriate usage.

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