Jiji MCP

jiji_seller_contact

Read-onlyIdempotent

Retrieve contact details for one explicitly shortlisted seller when completing a genuine purchase, not for bulk contacts or lead generation.

Instructions

Retrieve contact details for one explicitly shortlisted seller for a genuine purchase. Never use for bulk contacts or lead generation.

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_seller_contact"
  }
}

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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds a genuine usage policy constraint beyond the annotations, but says nothing about whether the declared purpose is audited/validated, what happens on an invalid or unknown guid, or any rate limiting on contact retrieval.

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?

Two short sentences, both load-bearing: the first states the action and scope, the second states the prohibition. Nothing is repeated or padded.

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?

The output schema exists, so return values need not be described, and annotations cover the safety profile. However, for a tool whose second required parameter is an intent declaration with zero schema documentation, the description should clarify what purchase_purpose is for and how strictly it is enforced.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden, yet it never explains that 'guid' is the seller identifier (constrained to 8-64 alphanumerics) or what a valid 'purchase_purpose' (10-300 chars) should contain. 'Explicitly shortlisted seller' and 'genuine purchase' only faintly map to the two parameters.

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 gives a specific verb+resource ('Retrieve contact details') and a clear scope qualifier ('for one explicitly shortlisted seller'), distinguishing it from a bulk-contact capability. It does not name a specific sibling (e.g. jiji_listing_details or jiji_whatsapp_handoff), so the differentiation is implicit rather than explicit.

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

Usage Guidelines4/5

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

It states the intended condition ('for a genuine purchase') and explicit exclusions ('Never use for bulk contacts or lead generation'), which is stronger than most definitions. It stops short of naming a sibling alternative for those bulk/lead-gen cases, leaving the agent to infer where to route them.

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