Skip to main content
Glama
Sign In
mcp-server-smallinvoice

mcp-server-smallinvoice

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_contact_addresses

Destructive

Remove one or more addresses from a contact by providing the contact ID and comma-separated address IDs.

Instructions

Deletes specified addresses

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": {
      "contact_id": "<contact_id>",
      "addresses_ids": "<addresses_ids>"
    },
    "name": "delete_contact_addresses"
  }
}

Input Schema

NameRequiredDescriptionDefault
contact_idYescontact ID
addresses_idsYesaddresses IDs (comma separated)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, and the description confirms deletion without contradiction. No additional behavioral details (e.g., permanence, cascading effects) are provided, but annotations bear the burden here.

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?

The description is a single sentence of three words, efficiently conveying the core function without extra verbiage. While minimal, it avoids redundancy.

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

Completeness3/5

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

For a simple deletion tool with two parameters and no output schema, the description is minimally complete. It lacks details about return state or side effects, but the schema fills the parameter gap.

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% with clear descriptions for both parameters. The description adds no extra meaning beyond the schema, meeting the baseline for high coverage.

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 'Deletes specified addresses' clearly states the action (deletes) and the resource (addresses). The tool name and title specify 'contact addresses', making the purpose unambiguous despite the description being generic.

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?

The description provides no guidance on when to use this tool versus alternatives like delete_contacts or create_contact_address. There is no mention of prerequisites or context.

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