Skip to main content
Glama
Sign In
Headquarter

Headquarter

by axeldotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_client

Delete a client and all their contacts by providing the client ID (slug).

Instructions

Delete a client and all their contacts

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_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesClient ID (slug)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior4/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 tool is destructive and cascades deletion to contacts. However, it does not mention any other potential side effects, such as deletion of related projects or issues, though those might be handled by separate tools.

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?

The description is a single, clear sentence with no unnecessary words. It is front-loaded and efficiently conveys the tool's purpose.

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?

For a simple delete tool with one required parameter and no output schema, the description is mostly complete. It states the effect and cascading behavior. However, it could mention that the operation is irreversible, though this is implied by 'delete'.

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?

Schema coverage is 100%, so the parameter is already described in the input schema. The tool description adds no additional meaning or usage context for the 'id' parameter beyond what the schema provides.

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 verb 'delete', the resource 'client', and the scope 'and all their contacts'. It distinguishes itself from siblings like delete_contact by specifying that it deletes the client and associated contacts.

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

Usage Guidelines3/5

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

The description indicates when to use the tool (to delete a client and its contacts), but does not provide explicit guidance on when not to use it, nor does it mention alternatives such as using delete_contact for removing contacts without deleting the client.

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