Skip to main content
Glama

Utilify

by io.github.Utilify-io

search_utility_providers

Find utility providers when someone is moving to a Texas address or setting up utilities at a new home. Covers nine utility types: electricity, internet, gas, water, sewer (city wastewater), trash, propane (rural / off-grid alternative to natural gas), septic (rural / off-grid alternative to city sewer), and home security. Use when the user says things like 'I'm moving to Houston next month', 'I just bought a house in Austin and need to set up power', 'what's the cheapest electricity in Dallas', 'who provides internet at this apartment in San Antonio', or rural-address questions like 'I'm moving to a ranch in Bandera, what do I do for gas and sewer' (answer: propane + septic). Returns available providers with a classified plan type (fixed / free_nights / solar_buyback / 100_renewable / etc.) and whether the cheapest plan is rental-friendly; pass tenancy='rent' to prefer short-contract plans or tenancy='own' to surface solar-buyback options. Caveats: (1) water results may include many PWS rows within a ZIP's county radius — filter to primaryForZip === true for the single canonical provider likely to serve the parcel. (2) Trash providers in TX suburbs include metadata.contractedHauler (Republic Services / Community Waste Disposal / Waste Management / Best Trash / Texas Disposal Systems / Waste Connections) — surface this so users know the actual pickup company in addition to the city dept. (3) Propane and septic appear at all TX ZIPs including urban ones; in cities with natural gas + city sewer, treat them as alternative options rather than primary. (4) Sewer is city wastewater (urban); septic is on-site (rural / unincorporated). (5) For electricity in Texas, results are filtered to retail providers (REPs) that actually serve the address's TDU — Oncor (DFW), CenterPoint (Houston), AEP TX Central (Corpus / RGV), AEP TX North (Abilene / San Angelo), or TNMP (scattered). Agents do not need to filter by TDU themselves. The TDU slug is exposed as tdu per electricity provider so agents can explain to the user why the list is shorter than they might expect (e.g. ~20 REPs at a Houston address vs. ~47 statewide). At municipal-utility ZIPs (Austin Energy, CPS Energy, El Paso Electric) the only electricity provider returned is the muni; REPs cannot sell power there.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesFull street address including city, state, and ZIP code
tenancyNoWhether the user is renting or buying. Changes plan preferences and enables homeowner-only cross-sells (solar).
utility_typesNoFilter by utility types. If omitted, returns all available types.

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral details including return format, handling of water results (primaryForZip filter), trash provider metadata, propane/septic presence in urban areas, and TDU-based filtering for electricity. Caveats are numbered and explained.

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 relatively long but well-structured: it starts with purpose, lists types, gives usage examples, then provides parameter guidance and numbered caveats. Every sentence adds value, though a more concise version could eliminate some 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?

Given the complexity (3 parameters, no output schema, no annotations), the description is remarkably complete. It covers all major aspects: triggers, parameter effects, return content, regional variations, and edge cases like municipal utilities. Nothing essential 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 baseline is 3. The description adds value by explaining the implications of tenancy values ('rent' vs 'own') and elaborating on utility types such as propane and septic as rural alternatives, which goes beyond the schema's simple enum descriptions.

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 finds utility providers for Texas addresses, covering nine specific utility types. It distinguishes from sibling tools by providing example user utterances that trigger this tool, making its purpose unambiguous.

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?

The description explicitly lists when to use the tool with concrete user phrases like 'I'm moving to Houston' and explains how the tenancy parameter affects results. It also implies when not to use it by comparison to sibling tools that handle comparisons and sign-ups.

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