Skip to main content
Glama

Utilify

by io.utilify

get_promotions

Get current deals, coupons, and exclusive affiliate offers for utilities at a Texas address — use when the user wants the best available price, not just any provider. Use when the user says 'what's the cheapest electricity deal in Dallas right now', 'any promotions for internet at my new Houston apartment', or 'find me a coupon before I sign up for my move-in'. Returns active promotions with discount details, expiration dates, and whether each offer is exclusive to Utilify; filter by utility_types or provider_slugs to narrow. Promotions are TDU-aware for electricity — only deals from REPs that actually serve the address are returned. Always pass address (or at least the ZIP) so the filter applies; calling this without an address returns a generic statewide list that may include un-buyable offers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesFull street address including city, state, and ZIP code
utility_typesNoFilter promotions by utility type
provider_slugsNoFilter promotions by specific provider slugs

TDQS

A4.3/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. It discloses TDU-aware filtering for electricity, what is returned (discount details, expiration dates, exclusivity), and behavior without address. Adds important behavioral context beyond basic functionality.

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?

Well-structured: starts with purpose, then usage, then behavior. Every sentence adds value, though slightly lengthy. Could be more concise but still efficient for an AI.

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?

Given no output schema, the description explains return values (discount details, expiration, exclusivity). Covers filtering and address importance. Minor omission on pagination or count, but overall sufficient for this complexity.

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 description coverage is 100%, so baseline is 3. The description adds extra value by explaining consequences of not providing address and the TDU-aware behavior, which goes beyond what the schema alone provides.

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 uses specific verbs ('get current deals, coupons, and exclusive affiliate offers') and clearly identifies the resource (utilities at a Texas address). It provides concrete usage examples and distinguishes from siblings by focusing on finding the best price.

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?

Explicit when-to-use guidance with example queries. Warns about calling without an address leading to generic results. Does not explicitly list when not to use or directly compare to siblings, but the context is clear enough for an agent.

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.7/5.0
Disambiguation5/5

Each tool serves a distinct function: searching, comparing, getting details, promotions, signing up, checking status, generating checklist, and solar interest. No overlapping purposes; agents can clearly differentiate.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (e.g., search_utility_providers, get_move_checklist), making them predictable and easy to learn.

Tool Count5/5

With 8 tools, the set is well-scoped for a Texas utility assistant. It covers the essential workflows without being too sparse or overwhelming.

Completeness5/5

The tool surface covers the full lifecycle: search, compare, details, promotions, signup, status, checklist, and solar interest. There are no obvious gaps for the stated domain of Texas utility setup.

Resources