Widely

Delete a CRM list

crm_delete_model

Destructive

Deletes one list and everything stored in it. Does not delete unless confirm is true. This is not crm_delete. crm_delete removes one saved thing inside a list. If another list is attached to this list, the delete is refused.

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": {
      "model": "<model>",
      "confirm": "<confirm>"
    },
    "name": "crm_delete_model"
  }
}

Input Schema

Name	Required	Description	Default
`model`	Yes	List name on this account.
`confirm`	Yes	Must be true. Deletes that list and everything stored in it.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, but the description goes further: it discloses the cascade scope ('everything stored in it'), the confirmation gate, and the referential-integrity refusal when another list is attached. That is real behavioral context beyond the structured fields.

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

Conciseness4/5

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

Four short sentences, front-loaded with the action and destruction scope, then the guard, then the sibling disambiguation. Minor redundancy between 'Does not delete unless confirm is true' and the schema's identical wording on confirm.

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 two-parameter destructive tool this covers scope, gate, refusal condition, and sibling routing. The only gap is that, with no output schema, it never says what a successful or refused call returns.

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%, with both model and confirm already documented inline. The description reinforces the confirm guard but adds no format, identifier convention, or error-shape detail beyond the schema.

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?

States a specific verb and resource ('Deletes one list and everything stored in it') and immediately distinguishes itself from the similarly named sibling crm_delete, which removes a single saved thing inside a list.

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

Usage Guidelines5/5

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

Explicitly routes the agent away from crm_delete and explains the selection rule between them, plus states the precondition (confirm must be true) and a blocking condition (refused if another list is attached).

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

All Widely tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.