Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

addresses_delete

Delete a specific address by its ID to remove outdated or incorrect address records from Macola 10 business data.

Instructions

Deletes the specific Address.

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

Input Schema

NameRequiredDescriptionDefault
idYesAddress ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.5/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 full burden of behavioral disclosure, and it discloses nothing beyond the bare operation. For a destructive mutation it does not say whether deletion is permanent, whether the address must be unreferenced by orders or contacts, what permissions are needed, or what error is returned for an unknown id.

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 single sentence is front-loaded and free of waste, but its brevity reflects under-specification rather than tight writing; "specific" is redundant given the required id parameter.

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?

This is a destructive tool with no annotations and no output schema, so the description should have covered irreversibility, referential constraints, and failure behavior. Given that a single required id is the whole contract, the definition leaves the agent without the information needed to call it safely.

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 description coverage is 100% with a single required string id, so the schema already fully documents the parameter. The description adds no meaning beyond it, which is the baseline case for high-coverage schemas.

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

Purpose3/5

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

The verb+resource pair ("Deletes" + "Address") identifies the operation and distinguishes it from addresses_get/addresses_update by the delete verb. However, "the specific Address" is vague filler and the description says nothing about what identifies the address beyond the schema's id field.

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 addresses_update or the other delete tools, and no statement of prerequisites or conditions under which deletion is appropriate. The agent must infer everything about selection from the verb alone.

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