Capable

Delete record

delete_record

Destructive

Archive by object_type + id. DESTRUCTIVE: call for confirmation, then confirm:true. Sets deleted_at, never hard-deletes: custom objects, reports (creator/manager/admin), whole quotes (lines cascade), contacts, opportunities, tasks, signals and touches. Contact history/account links remain restorable. Accounts refuse while any open opportunity or subscription remains; returned counts guide closing, re-pointing or marking lost first. Contacts/touches/notes/tasks remain as history and do not block. Subscriptions use cancel_subscription or update_record; individual quote lines use update_quote to change the line set. Returns the archived record.

When to use: A mistaken or duplicate record should go (archive, soft delete).

Example: Delete that duplicate contact .

Input Schema

Name	Required	Description
`id`	Yes	A uuid.
`confirm`	No	Boolean (true/false).
`object_type`	Yes	Object key of the record to archive, e.g. contact, opportunity, task, touch, account, report, quote, a custom object's key, or rollup / automation / field / object / pipeline (admin-only; the id from describe_schema); subscription is refused.

Output Schema

Name	Required	Description	Default
`note`	No
`record`	No
`result`	No
`deleted`	No
`requires_confirm`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

removedInput schema / properties / confirm / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]

addedInput schema / properties / confirm / type

Added value: +[
+  "boolean",
+  "string",
+  "number"
+]

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / object_type / description

Previous value: -"Object key of the record to archive, e.g. contact, opportunity, task, touch, account, report, quote, a custom object's key, or rollup / automation (admin-only); subscription is refused."New value: +"Object key of the record to archive, e.g. contact, opportunity, task, touch, account, report, quote, a custom object's key, or rollup / automation / field / object / pipeline (admin-only; the id from describe_schema); subscription is refused."

Changed1 schema field changedOct 20, 2026
- removedInput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
Changed6 schema fields changedOct 19, 2026
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / record / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / record / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / result / additionalProperties
```
Removed value: -{}
```
- removedOutput schema / properties / result / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
First observedOct 6, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say destructiveHint=true; the description carries far more: a confirm-then-confirm:true flow, soft delete via deleted_at with no hard delete, quote-line cascade, restorable contact history/account links, and the blocking rule for accounts with open opportunities or subscriptions (with returned counts to guide remediation). It also enumerates exactly which object types remain as non-blocking history.

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?

Front-loaded with the action and the DESTRUCTIVE warning, then the consequences, then alternatives, then an explicit 'When to use' plus example. The middle sentences are dense and clipped, but nearly every clause carries operational information an agent needs.

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

Completeness5/5

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

For a destructive, dependency-laden mutation it covers confirmation, reversibility, cascade behavior, blocking preconditions, and routing to alternatives. Return values are noted ('Returns the archived record') and an output schema exists, so nothing material is left for the agent to guess.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by giving confirm a procedural meaning (ask the user, then set true) rather than the schema's bare 'Boolean (true/false)'. object_type's refusal case for subscription and the admin-only keys are also reinforced, though most enumerations duplicate 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?

Opens with a specific verb+resource+keying scheme: 'Archive by object_type + id,' immediately followed by the DESTRUCTIVE marker. It enumerates the supported object types and explicitly distinguishes itself from cancel_subscription and update_quote, so an agent can separate it from create_record/update_record/restore_record siblings without opening a schema.

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?

'When to use: A mistaken or duplicate record should go (archive, soft delete)' states the triggering condition directly. It also names the exclusions and their alternatives: subscriptions use cancel_subscription or update_record, individual quote lines use update_quote. That is explicit when/when-not/alternative coverage.

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

All Capable 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.

Resources

Need Help?