Skip to main content
Glama

Tu Lugar

by com.tulugar

Open Signed-in Web Session

open_web_session

Give the signed-in user a ONE-TAP link that opens tulugar.com already logged in to their account — no code, no password. Use when a WhatsApp user needs the website: upload photos, finish a listing in the wizard, manage their account. The link is single-use and expires in 10 minutes; share it verbatim. Only works for accounts with a verified WhatsApp number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
return_toNoOptional site path to land on (e.g. "/es/account/listings"). Defaults to the account home.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false; description adds that link is one-tap, no code/password, single-use, and expires in 10 minutes. No contradiction.

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 sentences: first states the action, second provides usage context and constraints. Every sentence is necessary and front-loaded.

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?

No output schema, but description doesn't explicitly state the return value (the link). However, the tool is simple and the parameter behavior is fully covered. Minor gap.

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 already fully describes the 'return_to' parameter, including default. Description adds no additional meaning beyond what the schema provides.

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 uses a specific verb ('give') and resource ('one-tap link that opens tulugar.com already logged in'), clearly distinguishing this tool from siblings like 'share_listing_whatsapp' or 'search'.

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 ('when a WhatsApp user needs the website') and provides conditions (verified number, single-use, 10-minute expiry). No sibling does the same.

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