RetailHardHat

List Utility Connections

list_utility_connections

Read-onlyIdempotent

Use this when working with RetailHardHat field_operations records in the connected organization. Read utility connections at a site. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteId": "<siteId>"
    },
    "name": "list_utility_connections"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`search`	No
`siteId`	Yes

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful caveat that approvals are configurable by the org admin and business workflow approvals always apply, but it says nothing about pagination behavior or what a 'utility connection' record contains. With annotations carrying the safety burden, this is adequate but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only three sentences and reasonably short, but the actual purpose is buried in the middle, behind a boilerplate 'Use this when working with...' lead and ahead of an approvals disclaimer. Front-loading the verb+resource would make it markedly better.

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?

An output schema exists, so return values need not be described, and the tool is a simple read with one required identifier. The main remaining gaps are undocumented paging/search parameters and no routing guidance versus get_utility_connection, which keeps it short of full completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and it does not. It implies the site scoping of siteId but leaves limit, offset and search completely unexplained — an agent gets no hint that paging defaults to 50/0 with a max of 100, or what 'search' filters on.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read utility connections at a site'), which is enough to separate it from mutation siblings like create_utility_connection or update_utility_connection. It does not explicitly distinguish itself from get_utility_connection (single record) or list_utility_companies, so sibling differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening sentence ('Use this when working with RetailHardHat field_operations records in the connected organization') is generic domain boilerplate that likely applies to every tool in this server, so it doesn't tell the agent when this list tool is preferred over get_utility_connection. No when-not conditions or alternatives are named.

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

All RetailHardHat tools Inspect

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

Need Help?