Skip to main content
Glama

Utilify

by io.github.Utilify-io
OverviewDiscussionsAdmin

request_solar

Capture a Texas homeowner's interest in rooftop solar — use when the user owns (or is buying) a Texas home and mentions solar panels, solar quotes, solar savings, or reducing their bill through solar. Use when the user says 'I just bought a house in Austin and want solar quotes', 'how much could solar save on my Houston electric bill', or 'connect me with a solar installer for my new home'. What actually happens: Utilify emails the homeowner a confirmation link, and only if they click it is their information given to one licensed Texas installer, who pays Utilify a referral fee. No installer is contacted at tool-call time — do not tell the user someone will call them shortly. Caveats: (1) only call when the user has explicitly opted in and confirmed homeownership — this is not for renters. (2) Texas-only — for non-TX addresses, decline and explain. (3) An email address is required, since confirmation happens by email; a phone number alone is not enough. (4) Don't double-call for the same address in one conversation; one lead per opt-in. Note the 2026 economics when the user asks: the 30% federal credit for buying a system outright (Section 25D) expired 2025-12-31; a lease or PPA can still capture 30% via Section 48E through 2027. If the user has only expressed mild curiosity ('I'm thinking about solar someday'), answer the question first and only call this tool once they confirm 'yes, connect me'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesHomeowner email. Required — Utilify sends a confirmation link here, and nothing is released to an installer until it is clicked.
phoneNoHomeowner phone, if they want calls or texts. Optional; never used before the homeowner confirms by email.
addressYesFull service address including city, state, and ZIP code
last_nameNoHomeowner last name
first_nameNoHomeowner first name
session_idNoOptional agent session ID for attribution tracking
move_in_dateNoISO 8601 move-in date, if applicable
interest_levelNoHow close to decision. 'curious' = may consider later; 'researching' = actively comparing; 'ready' = wants quotes now.
estimated_monthly_billNoCurrent or expected monthly electricity bill in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"Homeowner email. Either email or phone is required so the installer can reach out."New value: +"Homeowner email. Required — Utilify sends a confirmation link here, and nothing is released to an installer until it is clicked."
    • changedInput schema / properties / phone / description
      Previous value: -"Homeowner phone. Either email or phone is required so the installer can reach out."New value: +"Homeowner phone, if they want calls or texts. Optional; never used before the homeowner confirms by email."
    • changedInput schema / required
      Previous value: -[
-  "address"
-]New value: +[
+  "address",
+  "email"
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

The description fully discloses the actual behavior: email confirmation link sent by Utilify, only on click is info released to one installer, referral fee, and no installer contacted at tool-call time. It also warns the agent not to promise a call. With only openWorldHint=true in annotations, the description carries the entire behavioral burden and does so thoroughly.

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?

The description is long but every sentence earns its place — it packs usage triggers, behavioral disclosures, and three caveats into a structured flow. While verbose, it avoids redundancy and front-loads the core purpose before diving into caveats. Slightly long but justifiably so.

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 9 parameters, 2 required, and significant eligibility constraints, the description covers all necessary context: state restrictions, opt-in requirements, email necessity, one-lead-per-address, and even 2026 tax credit details. An agent can fully determine when and how to invoke this tool correctly. No output schema exists, but the return behavior is described in the workflow, so nothing critical is missing.

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%, so parameters are already documented. The description adds clarifying context: email is strictly required for confirmation, phone is never used before email confirmation, and address must be Texas. It also explains the interest_level semantics implicitly through the curiosity caveat. This exceeds the baseline for high coverage.

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 a specific action — capturing a Texas homeowner's interest in rooftop solar — with concrete trigger examples ('I just bought a house in Austin and want solar quotes'). It distinguishes itself from sibling tools by focusing on lead capture rather than provider comparison or signup.

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?

Provides explicit when-to-use conditions (mentions solar panels, quotes, savings), example user phrases, and explicit exclusions (renters, non-Texas addresses, only after opt-in and confirmation). Also advises against double-calling and tells the agent to answer curiosity first. This is ideal routing guidance.

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

All Utilify toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources