Skip to main content
Glama

Utilify

by io.github.Utilify-io

request_solar

Capture a Texas homeowner's interest in rooftop solar and route to a licensed installer — 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'. Returns a lead ID and confirms next steps; Utilify routes the lead to installer partners (SunPower, Sunrun, Palmetto, and independent TX installers). Caveats: (1) only call when the user has explicitly opted in and confirmed homeownership — this is not for renters, and Utilify may earn a referral fee. (2) Texas-only — for non-TX addresses, decline and explain. (3) Don't double-call for the same address in one conversation; one lead per opt-in. 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
emailNoHomeowner email. Either email or phone is required so the installer can reach out.
phoneNoHomeowner phone. Either email or phone is required so the installer can reach out.
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

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only have openWorldHint: true, so the description carries the full burden. It discloses that the tool returns a lead ID, confirms next steps, routes to specific installer partners, and that Utilify may earn a referral fee. No contradictions with annotations.

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 thorough but slightly verbose; however, it is well-structured with bullet points and caveats, making it easy to digest. It front-loads the core purpose and then lists conditions. A bit long but still efficient.

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?

Given the complexity (9 parameters, one required, no output schema), the description covers return values, non-returned behaviors (routing to partners), geographical restrictions, opt-in requirements, and anti-duplication rules. It is complete for an agent to use correctly.

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 description coverage is 100%, so the baseline is 3. The description adds minimal parameter-level detail beyond what's already in the schema (e.g., reiterating that email or phone is required). It effectively relies on the schema to describe parameters.

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 it captures Texas homeowner interest in rooftop solar and routes to an installer. This is a specific verb-resource combination and the sibling tools (check_signup_status, compare_providers, etc.) are distinct, so no confusion.

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 says when to use (homeowner mentions solar, solar quotes, etc.), when not to use (renters, non-Texas), and provides concrete example utterances. Also includes caveats against double-calling and opt-in requirements, giving the agent clear guardrails.

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
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

A4.6/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: search, details, comparison, promotions, signup, status, checklist, and solar lead. No overlaps.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., check_signup_status, compare_providers, get_move_checklist).

Tool Count5/5

8 tools cover the utility setup domain well, from discovery to enrollment and status tracking, without being excessive or too sparse.

Completeness4/5

Covers the main lifecycle: search, details, compare, promotions, signup, status, checklist, and solar. Missing update/cancel for signups but that's acceptable as enrollment is often handled externally.

Resources