Skip to main content
Glama
Sign In
Gameball MCP Server

Gameball MCP Server

by Ahmedelmonady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

attachCustomerTags

Attach tags to a customer profile by providing their ID and the tags. Use this to organize customers for targeted marketing and personalized experiences.

Instructions

🔒 Create tag

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>",
      "tags": "<tags>"
    },
    "name": "attachCustomerTags"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsYes
customerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description must disclose side effects, permissions, or mutability, but it does not. The lock emoji is unexplained and adds no actionable behavioral information.

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 a single vague phrase, which is under-specification rather than effective conciseness. It does not earn its place because it omits essential information about the tool's purpose and parameters.

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?

With no output schema, no annotations, and an inadequate description, the tool lacks all essential context. The two required parameters are undocumented, and the tool's effect on the system is entirely undisclosed, leaving an agent unable to safely select or invoke 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?

Schema description coverage is 0%, and the description fails to explain the meaning of customerId or tags. It does not clarify whether tags is a single tag, a comma-separated list, or a JSON array, making correct invocation impossible.

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

Purpose1/5

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

The description 'Create tag' is misleading: the tool name 'attachCustomerTags' implies attaching tags to a customer, but the description says 'create' without mentioning customer or attachment. It may be confused with creating a tag definition rather than attaching existing tags. It does not distinguish from siblings like removeCustomerTags.

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 guidance is provided on when to use this tool versus alternatives such as removeCustomerTags or other customer-related operations. The description gives no context for selection.

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