Skip to main content
Glama
Sign In
garu-mcp

garu-mcp

Official
by Garu-Pagamentos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_customer

Remove a customer from your seller account. The customer is not deleted globally, only disassociated from your store.

Instructions

Remove a customer from the current seller. Does not delete the customer globally.

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": {
      "id": "<id>"
    },
    "name": "delete_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCustomer ID to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.18.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the deletion is scoped to the current seller, which is key. However, it lacks details on side effects (e.g., impact on associated data), reversibility, or prerequisites. The minimal disclosure is adequate for a simple action but could be more comprehensive.

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

Conciseness5/5

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

Two sentences, zero waste. The key point is front-loaded and the clarification is in the second sentence. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (single parameter, no output schema), the description provides the essential scope distinction. It could mention irreversibility or effect on related data, but for a straightforward deletion tool, it is largely complete.

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

Parameters3/5

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

The schema already describes the 'id' parameter as 'Customer ID to remove' (100% coverage). The description adds no additional meaning beyond the schema, so it is neither deficient nor additive.

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 clearly states the action ('Remove a customer') and resource ('from the current seller'), distinguishing it from a global delete. This provides a specific and unambiguous purpose.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that this tool should be used for local removal only and not for global deletion. While it provides useful context, it does not explicitly state when not to use it or mention alternatives, but the inference is clear given the sibling tools.

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