Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

contacts_delete

Deletes a specific contact by its ID, removing outdated or incorrect contact records from Macola 10.

Instructions

Deletes the specific Contact.

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": "contacts_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesContact ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the whole burden. It states deletion but says nothing about whether removal is permanent, whether related records (addresses, orders, comment codes) are affected, whether the contact must be inactive first, or what happens if the ID is invalid.

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?

One short, front-loaded sentence with no filler, which is appropriate for a single-parameter tool. It is underspecified rather than verbose, and "specific" is slightly vague wording that earns little.

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

Completeness2/5

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

For a destructive tool with no annotations and no output schema, the definition should at minimum disclose permanence and failure behavior. As written, an agent knows only that something called a Contact is deleted by ID.

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% and the single `id` parameter is already documented as "Contact ID to delete". The word "specific" hints at ID-based targeting but adds no format, range, or lookup-syntax detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource combination ("Deletes the specific Contact"), so an agent can tell it is a destructive single-contact operation. It does not distinguish itself from the other *_delete siblings beyond the resource name, but the resource is unambiguous.

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?

There is no guidance on when to use this versus contacts_update or the other delete tools, and no mention of prerequisites such as verifying the contact exists first. The agent must infer the usage context entirely from the name.

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