Radar noEixo

Delete companies without contacts

delete_companies_without_contacts

Destructive

EXCLUI DE VEZ as fichas de empresa SEM nenhum contato e com status "lead" (cliente, prospect e inativa nunca saem). Contatos, conversas e leads do Garimpo não são tocados. Não tem desfazer. Uso típico: depois de apagar contatos ou o Garimpo, limpar as empresas que ficaram soltas. Em duas chamadas: a primeira, sem "confirmar", só devolve quantas sairiam — mostre a quem pediu e só repita com "confirmar" igual ao número depois que essa pessoa confirmar. Roda em segundo plano; chame sem "confirmar" para ver quantas faltam.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_companies_without_contacts"
  }
}

Input Schema

Name	Required	Description	Default
`confirmar`	No	O número de empresas devolvido pela chamada sem confirmar. Sem ele, nada é excluído

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds substantial context the annotations cannot convey: no undo, the exact status/contact preconditions, what related data is left untouched, that execution happens in the background, and that the unconfirmed call is a dry-run. This is exactly the extra disclosure a destructive tool needs.

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 destructive scope and the exclusions before the workflow, so the highest-risk information lands first. Slightly redundant at the end ('Roda em segundo plano; chame sem "confirmar" para ver quantas faltam' restates the dry-run idea), which keeps it just short of a 5.

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 single-parameter tool with no output schema, everything an agent needs is present: preconditions, exclusions, irreversibility, the confirmation handshake, and what the unconfirmed invocation returns (a count). Nothing material is missing.

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% and already documents 'confirmar', so the baseline is met. The description goes further by explaining that the value must equal the number returned by the dry-run and must only be supplied after the requesting person confirms, which is semantic meaning absent from 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 ('EXCLUI DE VEZ') and a precisely scoped resource: company records with zero contacts and status 'lead'. It explicitly names what will NOT be deleted (cliente, prospect, inativa, contatos, conversas, leads do Garimpo), which cleanly separates it from sibling deleters like delete_contacts_by_tag.

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?

Gives an explicit typical scenario ('depois de apagar contatos ou o Garimpo, limpar as empresas que ficaram soltas') and a mandatory two-step protocol: call first without 'confirmar', show the count to the requester, and only repeat with 'confirmar' equal to that number after human confirmation. When-to-use and how-to-use are both spelled out.

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

All Radar noEixo 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?