Skip to main content
Glama
Sign In
Gameball MCP Server

Gameball MCP Server

by Ahmedelmonady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

trackOrder

Create a new order in Gameball by submitting customer, payment, and line item details for transaction recording.

Instructions

🔒 Create order

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>",
      "orderId": "<orderId>",
      "orderDate": "<orderDate>",
      "totalPaid": "<totalPaid>"
    },
    "name": "trackOrder"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
extraNoKey-value pairs containin
guestNo
cartIdNo
mobileNo
channelNoOptions: mobile, pos, web, callcenter
orderIdYes
merchantNoThis object contains deta
totalTaxNo
lineItemsNoAn array containing detai
orderDateYesISO 8601
totalPaidYes
customerIdYes
redemptionNoRedemption details for th
totalPriceNo
totalDiscountNo
totalShippingNo
cashbackConfigurationsNoThis object contains conf

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/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 of behavioral disclosure. It only says 'Create order' and offers no information about side effects, authentication, idempotency, or response behavior. The lock emoji hints at security but is too vague to be useful.

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, but this is under-specification rather than concise efficiency. For a complex 18-parameter tool, a single phrase like 'Create order' fails to earn its place as a useful description.

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?

Given the tool's complexity (18 parameters, nested objects, no output schema, no annotations), this description is grossly incomplete. It lacks all contextual information needed for an AI agent to select and invoke the tool correctly.

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?

With only 39% schema description coverage and 18 parameters, the description should compensate by explaining parameter relationships or key fields. It adds no parameter information whatsoever, leaving required fields like customerId, orderId, orderDate, and totalPaid completely unexplained.

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 'Create order' clearly states a create operation on an order resource, but it fails to distinguish from sibling tools and directly conflicts with the tool name 'trackOrder', which implies tracking rather than creation. This internal inconsistency reduces clarity.

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 versus alternatives, no context, and no exclusions. It simply states 'Create order' with no mention of prerequisites or use cases.

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