Jiji MCP

jiji_whatsapp_handoff

Read-onlyIdempotent

Prepares a WhatsApp handoff for a selected seller by returning the recipient, exact listing link, and proposed availability message without sending anything.

Instructions

Prepare a handoff for WhatsApp or another authorized agent for one selected seller. Returns recipient, exact listing link and proposed availability message. Sends nothing.

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": {
      "guid": "<guid>",
      "purchase_purpose": "<purchase_purpose>"
    },
    "name": "jiji_whatsapp_handoff"
  }
}

Input Schema

Name	Required	Description	Default
`guid`	Yes
`purchase_purpose`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3Oct 29, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, and open-world behavior. The description adds important behavioral clarity by stating that it only prepares a handoff, returns recipient/listing link/proposed message, and explicitly 'Sends nothing.'

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 front-loaded sentences with no filler. It states the action, scope, return contents, and the critical non-sending constraint efficiently.

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?

Output schema coverage and annotations reduce what the description must explain, and it usefully notes the return contents and that nothing is sent. But with two required parameters at 0% schema description coverage and no parameter explanations in the description, an agent lacks the semantics needed to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two required parameters, and the description never mentions 'guid' or 'purchase_purpose.' 'One selected seller' weakly hints at guid, but the description provides no usable semantics for either parameter.

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 uses a specific verb and resource: preparing a WhatsApp/authorized-agent handoff for one selected seller. It clearly states the output and that nothing is sent, but it does not explicitly distinguish this tool from nearby siblings such as jiji_prepare_message or jiji_seller_contact.

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 'for WhatsApp or another authorized agent' gives implied usage context, and 'Sends nothing' clarifies the non-sending scope. However, it does not state when to use this instead of jiji_prepare_message, jiji_seller_contact, or other prepare/action tools.

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