Skip to main content
Glama

Request a home valuation

request_home_valuation

Request a professional (human-prepared) market valuation of a property in Lincoln or southeast Nebraska. Requires the property address plus the client's name and contact. Only call after your user explicitly approves (user_approved=true).

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'
property_addressYesFull address of the property to value (required)

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It correctly flags the request as human-prepared and requires explicit approval, but does not mention side effects, authorization beyond user_approved, or what happens after the request (e.g., confirmation, timeline).

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?

The description is three sentences, each adding value: purpose, requirements, and condition. It is front-loaded and concise with no wasted words.

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

Completeness3/5

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

Given 12 parameters, no output schema, and no annotations, the description covers core purpose and prerequisites but omits what the user can expect after the request (e.g., response format, follow-up). It adequately describes how to invoke but not the full interaction.

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 12 parameters have schema descriptions (100% coverage), so the baseline is 3. The description reiterates the key required parameters but adds no new semantic detail beyond the schema. It provides context like geographic scope, but that is not parameter-specific.

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 verb 'Request' and the resource 'professional market valuation of a property', with a specific geographic scope (Lincoln or southeast Nebraska). It distinguishes from sibling tools by focusing on valuation rather than general info or consultation.

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?

The description explicitly says to only use this tool after user approval (user_approved=true), and lists required inputs (property address, client name/contact). It implies usage context but does not mention alternatives or when not to use it.

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