Skip to main content
Glama
Sign In
mcp-lindoai

mcp-lindoai

Official
by lindoai
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
JavaScript
Remote

Delete Client

delete_client
Destructive

Delete a client from your workspace by specifying the client's record ID.

Instructions

Delete a client from the workspace.

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": {
      "record_id": "<record_id>"
    },
    "name": "delete_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
record_idYesClient record ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.17
  2. Removedv1.0.16
  3. First observedv1.0.14

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already signal destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutation. The description confirms it is a delete operation but adds no extra context about side effects, irreversibility, or permissions. Given annotation coverage, this is adequate but minimal.

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 concise sentence (6 words) that immediately conveys the action and resource, with no extraneous information.

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 operation with one parameter, annotations present, and no output schema, the description sufficiently covers the basic purpose. It could mention potential consequences (e.g., permanent deletion) but is not incomplete.

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 has full coverage (100%) on the single parameter record_id with a description. The tool description does not add any additional meaning or context beyond what the schema provides, so baseline 3 is appropriate.

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' and the resource 'client from the workspace', which is specific and distinguishable from sibling tools like delete_blog or delete_website.

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 whether the client must first be removed from associated resources, or mention of prerequisites. The description is purely declarative.

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