kirimi-mcp

save_contact

Save a contact to your WhatsApp device. Existing phone numbers are skipped, preventing duplicates and preserving your current contact list.

Instructions

Save one contact. Numbers that already exist are skipped, not overwritten.

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": {
      "nama": "<nama>",
      "nomor": "<nomor>"
    },
    "name": "save_contact"
  }
}

Input Schema

Name	Required	Description
`nama`	Yes	Contact name
`nomor`	Yes	Phone number in international format without + (e.g. 6281234567890)
`device_id`	No	Device ID (e.g. D-XXXXX). Optional if the KIRIMI_DEVICE_ID environment variable is set.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.0Sep 20, 2026

changedInput schema / properties / device_id / description

Previous value: -"Optional device ID to associate this contact with"New value: +"Device ID (e.g. D-XXXXX). Optional if the KIRIMI_DEVICE_ID environment variable is set."

changedInput schema / properties / nomor / description

Previous value: -"Contact phone number"New value: +"Phone number in international format without + (e.g. 6281234567890)"

First observedv1.0.0Jul 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses a key trait: existing numbers are skipped, not overwritten. However, it does not mention what happens on success or failure, whether any device context is required, or what the return/result behavior is beyond the skip rule.

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 two short sentences with no filler. The primary action is front-loaded, and the important deduplication behavior is stated immediately afterward.

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

Completeness4/5

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

For a simple tool with only two required parameters, full schema coverage, and no output schema, the description is nearly sufficient. The main missing element is return/response behavior, but the deduplication rule and schema-provided parameter details give an agent enough to call the tool correctly.

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%, so the schema already documents nama, nomor, and device_id fully. The description adds context about duplicate handling for existing numbers, which relates to nomor, but it does not provide additional parameter-level meaning beyond the schema.

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

Purpose5/5

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

The description states a specific verb and resource: 'Save one contact.' It also distinguishes itself from the sibling tool save_contacts_bulk by explicitly limiting itself to a single contact, making the tool's scope immediately clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Save one contact' implies this is for single-contact use, especially given the save_contacts_bulk sibling, but it does not explicitly say when to choose this tool over alternatives or when not to use it. Usage context is present but not fully articulated.

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