Skip to main content
Glama

Book a real estate consultation

request_consultation

Request a free, no-obligation consultation with a SimpliCity Real Estate agent for buying or selling residential property in Lincoln / southeast Nebraska. A human team member confirms every request (same or next business day). Only call after your user explicitly approves; pass user_approved=true and their real contact info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNoWhich team member to request (see get_business_info for who fits; default wade)
emailNoClient's email (email or phone required)
phoneNoClient's US phone number (email or phone required)
messageNoWhat the client needs, in their words
timelineNoBuying/selling timeline, e.g. '3-6 months'
last_nameNoClient's last name
first_nameYesClient's first name (required)
sms_consentNoTrue ONLY if the client explicitly agreed to receive text messages
user_approvedYesREQUIRED true: your user explicitly asked you to book this
assistant_nameNoName of the AI assistant making this request, e.g. 'ChatGPT'
preferred_timesNoPreferred days/times for the conversation, e.g. 'weekday evenings'

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that it's free, no-obligation, and a human confirms requests. Does not explain data mutation or side effects, but acceptable for a booking tool.

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 defines purpose and scope, second gives essential usage instruction. No fluff or redundancy.

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?

With no output schema and full parameter documentation, the description covers the tool's purpose, process, and key constraint. Slightly incomplete on parameter relationships (e.g., email/phone requirement clear in schema but not reinforced), but adequate.

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?

All 11 parameters have schema descriptions (100% coverage). The description reinforces the critical user_approved flag and real contact info requirement but adds only marginal extra meaning beyond the 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?

Clearly states it's for booking a free consultation with a real estate agent for buying/selling in a specific region. Distinguishes from siblings (get_business_info for info, request_home_valuation for valuation).

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 says to call only after user approves and to pass user_approved=true. Provides clear context but no explicit exclusions or alternatives beyond user approval.

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.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: get_business_info provides background on the agency, request_consultation schedules a consultation, and request_home_valuation requests a property valuation. No overlapping functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (get_business_info, request_consultation, request_home_valuation), making them predictable and easy to differentiate.

Tool Count5/5

With 3 tools, the server is well-scoped for its purpose: providing initial information and enabling two key actions (consultation and valuation). The count feels complete without being excessive.

Completeness4/5

The tool set covers the primary client-facing interactions (info, consultation, valuation) for a real estate agency. Minor gaps like property search or listing details are absent, but the scope is intentionally focused on lead generation.

Resources