Skip to main content
Glama

Somon.tj classifieds

Seller contact

reveal_contact
Idempotent

Seller's phone, WhatsApp or chat link. Call only when the user asks to contact the seller.

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": {
      "advert_id": "<advert_id>"
    },
    "name": "reveal_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
advert_idYesadvert_id from search_adverts or get_advert.

Output Schema

NameRequiredDescriptionDefault
urlYesListing page on the marketplace site.
phoneNo
messageNo
chat_urlNo
availableYes
whatsapp_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already declare destructiveHint=false and idempotentHint=true, but readOnlyHint=false is notable for what looks like a data retrieval call, suggesting a side effect such as credit consumption, logging, or seller notification. The description adds the useful detail of which contact channels are returned but does not explain that side effect, its cost, or any privacy implications.

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: the first states what is returned, the second states the restriction on calling. Nothing is redundant and the essential constraint is front-loaded within a very small footprint.

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

Completeness5/5

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

For a one-parameter reveal tool with full schema coverage, an output schema that documents the return value, and annotations covering the safety profile, the description supplies everything needed to decide when to call it. No significant gap remains.

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 coverage is 100% and the single advert_id parameter is already documented with its provenance (search_adverts or get_advert). The description adds nothing about the parameter, so the schema does all the work and the baseline 3 applies.

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 names the concrete resource returned — seller phone, WhatsApp or chat link — so an agent knows exactly what the call produces. It does not explicitly distinguish itself from get_advert, which presumably shows advert details without contact data, so it stops short of a 5.

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?

"Call only when the user asks to contact the seller" is an explicit, restrictive gating condition, which is strong guidance for a privacy-sensitive reveal. It gives no named alternative for the case where the user has not asked to contact the seller, leaving that inference to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources