Skip to main content
Glama
lindoai

mcp-lindoai

Official

delete_client

Destructive

Delete a client from your workspace by providing the client record ID. This action removes the client and its data.

Instructions

Delete a client from the workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
record_idYesClient record ID to delete

Implementation Reference

  • Registration of the 'delete_client' tool via server.tool() with name 'delete_client', description, schema, and handler.
    server.tool(
      "delete_client",
      "Delete a client from the workspace.",
      {
        record_id: z.string().describe("Client record ID to delete"),
      },
      { title: "Delete Client", readOnlyHint: false, destructiveHint: true, openWorldHint: false },
      async ({ record_id }) => {
        const data = await apiCall("/v1/workspace/client/delete", "DELETE", { record_id });
        return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
      }
    );
  • Input schema for 'delete_client' expecting a single 'record_id' (string) via Zod validation.
    {
      record_id: z.string().describe("Client record ID to delete"),
    },
  • Handler function for 'delete_client' that calls apiCall to DELETE /v1/workspace/client/delete with record_id.
    async ({ record_id }) => {
      const data = await apiCall("/v1/workspace/client/delete", "DELETE", { record_id });
      return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
    }
  • The apiCall helper function used by the handler to make HTTP requests with the API key.
    async function apiCall(path, method, body) {
      const url = `${BASE_URL}${path}`;
      const res = await fetch(url, {
        method,
        headers: {
          Authorization: `Bearer ${API_KEY}`,
          "Content-Type": "application/json",
        },
        ...(body ? { body: JSON.stringify(body) } : {}),
      });
      return res.json();
    }
Behavior3/5

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

Annotations already provide destructiveHint=true and readOnlyHint=false, so the description adds no substantive behavioral context beyond stating the obvious deletion. No contradiction.

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 sentence with no filler, efficiently communicating 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 single-parameter deletion tool with annotations, the description is nearly complete. It explicitly states the workspace scope, but no output schema or additional behavioral notes are necessary.

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% and the parameter description ('Client record ID to delete') is straightforward but adds little beyond the schema's required field specification.

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 uses a specific verb ('Delete') and resource ('a client from the workspace'), clearly distinguishing it from sibling tools like 'create_client' and 'update_client'.

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?

The description omits any guidance on when to use this tool versus alternatives (e.g., 'update_client'), prerequisites (e.g., client existence), or consequences (e.g., irreversibility).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lindoai/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server