Skip to main content
Glama
Sign In

NeoMind

by com.neomindhub.app
OverviewDiscussionsAdmin

Do not contact a lead

mark_lead_do_not_contact
DestructiveIdempotent

Mark one lead as do-not-contact, by lead id (from list_leads): your AI team will never follow them up again, and any follow-up waiting for them is dismissed. Only call when the owner has said so. Only the business owner's connection can do this.

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": {
      "id": "<id>"
    },
    "name": "mark_lead_do_not_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe lead's id (a UUID), from list_leads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

While annotations flag it as 'destructive,' the description adds crucial behavioral detail: that the AI team 'will never follow them up again' and that pending tasks are 'dismissed,' which explains the systemic impact of the action to the agent.

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

Conciseness3/5

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

The description is slightly verbose, bundling policy and execution details into one long sentence. It is functional but could be broken into sharper constraints for better readability.

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?

The description is highly complete for a destructive action. It defines the action, the necessary pre-conditions for use, and the operational results of the execution within the system.

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?

With 100% schema coverage, the description adds minimal structural value but provides excellent semantic context by specifying that the ID must come 'from list_leads,' narrowing the scope for the AI.

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 purpose is clearly stated: to mark a lead as do-not-contact using a lead ID. It distinguishes this action from listing leads or managing teammates, focusing entirely on the policy change.

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?

The tool explicitly provides usage boundaries, stating it should only be called 'when the owner has said so' and constrained to the 'business owner's connection,' preventing misuse by lower-level agents.

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

All NeoMind toolsInspect
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