Skip to main content
Glama

Tu Lugar

by com.tulugar

Share Listing on WhatsApp

share_listing_whatsapp
Read-only

Generate a ready-to-send WhatsApp message for one of the authenticated agent's OWN listings: a polished, WhatsApp-tuned caption + a one-tap wa.me link (optionally pre-addressed to a client phone) + the property's main photo to attach. Use whenever the agent wants to send, share, or forward a listing to a client (or to their WhatsApp status). Pass listing_id (from my_listings); optionally client_phone to pre-address the chat. After calling, you can personalize the message for a specific client and rebuild the wa.me link yourself (URL-encode the new text into https://wa.me/?text=...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeNoMessage language (default es)
listing_idYesID of the agent's own listing (from my_listings)
client_phoneNoOptional client phone, international format (e.g. +595981234567), to pre-address the WhatsApp chat

TDQS

A4.7/5.0
Behavior4/5

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

Annotations include readOnlyHint=true and description confirms generation without side effects. Adds useful behavioral context: message is ready-to-send, includes one-tap link, and photo attachment. No contradictions.

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?

Two well-structured sentences front-load the core purpose. The second sentence is dense but logical. Could be slightly more concise but overall efficient.

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?

Covers all essential aspects: what it generates, required/optional parameters, usage scenario, and post-processing instructions. No missing details given no output schema.

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

Parameters5/5

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

Schema coverage is 100% but description adds meaning: listing_id is from my_listings, client_phone in international format pre-addresses chat, locale defaults to es. Explains how parameters affect behavior beyond 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 clearly states the tool generates a WhatsApp message with caption, wa.me link, and photo for the agent's own listings. It distinguishes from sibling tools like send_whatsapp_verification by specifying it's for listings and requires authentication.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'whenever the agent wants to send, share, or forward a listing to a client'. Provides context that it's for OWN listings and suggests alternative personalization approach after calling.

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

All Tu Lugar toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes covering account management, listings, search, financials, etc. However, `fetch` and `get_listing` both retrieve full listing details, creating potential confusion. Also, `search` and `search_listings` overlap but are differentiated by free-text vs. filtered search.

Naming Consistency5/5

All tool names follow a consistent `verb_noun` pattern in snake_case (e.g., `create_listing`, `publish_listing`, `connect_account`). The naming is predictable and clear throughout.

Tool Count3/5

At 39 tools, the server is quite large for a real estate domain. While it covers many aspects, some tools like `fetch` and `get_listing` are redundant. The count feels excessive and could be streamlined to around 25-30 without losing functionality.

Completeness4/5

The tool set covers listing CRUD, various search types, agent/company profiles, financial calculators, inquiries, saved searches, and account management. Minor gaps exist, such as lack of bulk operations or advanced analytics, but core workflows are well-supported.

Resources