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

mcp-server-smallinvoice

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_contact_groups

Destructive

Delete contact groups from Smallinvoice by submitting a comma-separated list of group IDs.

Instructions

Deletes specified groups

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": {
      "groups_ids": "<groups_ids>"
    },
    "name": "delete_contact_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
groups_idsYesgroups IDs (comma separated)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already flag this tool as destructive (destructiveHint=true) and not read-only. The description adds no additional behavioral context, such as permanence of deletion, cascade effects, or required permissions. With annotations covering the basic safety profile, a score of 3 is appropriate.

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 that is efficient and to the point. It is appropriately sized for a straightforward deletion tool, though it could include more detail without becoming verbose.

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 destructive nature and the presence of a similar sibling ('remove_contact_groups'), the description is insufficient. It does not explain the outcome (e.g., successful deletion, impact on related data) or clarify when 'delete' versus 'remove' should be used. The lack of output schema increases the need for descriptive context.

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 input schema provides a full description of the single parameter 'groups_ids' as 'groups IDs (comma separated)'. The description does not add any extra meaning beyond what the schema already says, so the baseline score of 3 is correct.

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 description 'Deletes specified groups' clearly indicates the action and resource, but it does not differentiate from the sibling tool 'remove_contact_groups', which may have a similar purpose. The lack of specificity about what 'groups' refers to (presumably contact groups) could cause confusion.

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 guidance is given on when to use this tool versus alternatives like 'remove_contact_groups' or other delete tools. There is no mention of prerequisites, side effects, or conditions for safe usage.

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