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.7/5.0
Behavior5/5

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

Discloses critical behaviors beyond annotations: link is single-use, expires in 10 minutes, requires verified WhatsApp number. No contradictions with readOnlyHint=false or destructiveHint=false.

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?

Extremely concise: two sentences front-loading the core action and adding usage guidance. Every sentence adds value with no redundancy.

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 tool with one optional parameter and no output schema, the description covers purpose, usage context, behavioral constraints, and parameter defaults completely.

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

Parameters4/5

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

Schema coverage is 100% with description for 'return_to'. The description adds the default value ('account home') which is not in schema. Provides additional context 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 provides a one-tap link for signed-in access to tulugar.com. It uses a specific verb ('give') and resource ('one-tap link') and distinguishes itself from sibling tools by focusing on session creation.

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?

Explicitly states when to use (WhatsApp user needs website). Provides use cases (upload photos, finish listing, manage account). Lacks explicit when-not-to-use or alternative tools, but context is clear enough.

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.7/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is some overlap between 'search' and 'search_listings', and between 'fetch' and 'get_listing'. However, descriptions effectively differentiate them.

Naming Consistency3/5

Naming follows multiple patterns: verb_noun (create_listing), noun (closing_costs), get_*, search_*, my_*. While each pattern is internally consistent, the mix reduces overall consistency.

Tool Count3/5

39 tools is relatively high, but they cover a broad set of real estate functionalities. The count feels slightly heavy but is justified by the domain scope.

Completeness5/5

The tool set covers the full lifecycle of listings (CRUD, promotion, sharing), account management, search with multiple filters, market data, guides, and lead management. No obvious gaps for the platform's purpose.

Resources