mcp-server-smallinvoice

delete_contact_people

Destructive

Remove specific people from a contact by providing the contact ID and comma-separated people IDs.

Instructions

Deletes specified people

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>",
      "people_ids": "<people_ids>"
    },
    "name": "delete_contact_people"
  }
}

Input Schema

Name	Required	Description	Default
`contact_id`	Yes	contact ID
`people_ids`	Yes	people IDs (comma separated)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description states the deletion action, which matches the destructiveHint annotation. However, it adds no further behavioral details beyond what the annotation already provides (e.g., irreversible, side effects). With annotations covering the destructive nature, the description is adequate but not enriched.

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

Conciseness5/5

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

The description is a single concise sentence with no unnecessary words. It is front-loaded and efficient, conveying the essential purpose without elaboration.

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?

Given the tool's simplicity, the description is too brief. It fails to specify that the deletion is from a contact (implied by name but not description), and does not mention any side effects, required permissions, or that the action is irreversible. The annotations indicate destructiveness, but the description should reinforce that. For a deletion tool, more context is needed.

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?

The schema covers both parameters with descriptions (contact_id, people_ids comma separated). The description does not add new information about parameters, but the schema coverage is 100%, so the baseline is 3. No extra value provided.

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 people' clearly indicates the action (delete) and the resource (people), but could be more specific by stating that these are people within a contact, especially given sibling tools like delete_contacts. The tool name already provides this context, so it's clear but minimal.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., remove_contact_groups or deleting the entire contact), nor does it mention prerequisites or consequences. An agent would have to infer usage solely from the name and schema.

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

Deploy Server