Skip to main content
Glama
Sign In
Gameball MCP Server

Gameball MCP Server

by Ahmedelmonady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

getCustomerActivities

Retrieve a customer's activity history. Filter activities by type and control pagination using limit and startAfter parameters.

Instructions

🔒 Get activitie

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

Input Schema

NameRequiredDescriptionDefault
limitNoSpecifies the number of activi
customerIdYes
startAfterNoSpecifies the page will start
activityTypeNoFilters activities by a specif

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but 'Get activitie' with a lock emoji reveals nothing about pagination, filtering, permissions, rate limits, or return structure. The lock emoji is ambiguous and not a substitute for explicit behavioral context.

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 concisely informative. A two-word truncated phrase with an emoji does not earn its place; it is a fragment that provides minimal value while failing to convey essential information.

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 pagination and filtering parameters, no output schema, and no annotations, the description is grossly incomplete. It omits response format, pagination behavior, activity type options, and any auth or permission context, making it inadequate for an agent to invoke correctly.

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 75% but the descriptions are truncated (e.g., 'Specifies the number of activi'), and the tool description adds no parameter semantics. The required customerId has no description, and limit/startAfter/activityType are only partially explained, leaving their roles unclear.

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 activitie' is a truncated tautology of the tool name, stating only a verb and an incomplete resource. It does not differentiate from sibling tools like getCustomerActivitiesCount or getCustomerDetails, and the misspelling undermines 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?

No usage guidance is provided. The description does not suggest when to use this tool over alternatives, nor does it mention any exclusions, prerequisites, or context in which it should be chosen.

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