Skip to main content
Glama
Sign In
Gameball MCP Server

Gameball MCP Server

by Ahmedelmonady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

removeCustomerTags

Removes specified tags from a customer's profile using their customer ID.

Instructions

🔒 Delete 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": "removeCustomerTags"
  }
}

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 carries the full burden for behavioral disclosure. It merely states 'Delete tag' with no mention of irreversibility, permission requirements, side effects, or scope (e.g., whether it deletes all tags or specific ones). The lock emoji hints at security but provides no factual content.

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 effective conciseness. A concise description should pack essential information into few words; this omits critical context about parameters and usage, making it nearly useless.

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 a tool with two required parameters, no annotations, no output schema, and a minimal description, there is insufficient context for an agent to invoke it correctly. The description does not explain what a 'tag' is, how to format the tags parameter, or what the tool returns.

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 an input schema of two required params (tags, customerId) and 0% description coverage, the description must compensate by explaining parameter meanings. It does not mention either parameter at all, leaving the agent to guess what 'tags' means (e.g., comma-separated list?) and how 'customerId' relates.

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 'Delete tag' is a near-tautology of the tool name 'removeCustomerTags', restating the action in simpler words without adding specificity. It fails to mention that tags are customer tags, and the singular 'tag' is ambiguous given the sibling tool 'removeCustomerTag'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 indicate when to use this tool over its siblings (e.g., 'removeCustomerTag' singular) or any prerequisites, making it impossible for an agent to decide when this tool is appropriate.

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