Skip to main content
Glama

List HVAC services

get_services
Read-onlyIdempotent

List the HVAC services AtlantFlow offers (AC repair, replacement, maintenance plan, heating, mini-splits, thermostats, indoor air quality, commercial HVAC and refrigeration, emergency service) with a short description and page URL for each.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional filter: residential, commercial or emergency. Omit for everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's one addition beyond that is the return shape — each entry carries a short description and page URL — which is genuinely useful since no output schema exists, but it says nothing about ordering, empty results, or volume.

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?

One front-loaded sentence with the resource and the returned fields stated immediately. The long parenthetical service list is slightly heavy but earns its place by letting an agent match user phrasings like 'mini-splits' or 'thermostats' without another call.

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?

For a one-optional-param, read-only listing tool with full annotation coverage, this is close to complete: it says what is listed and what each item contains. The gaps are minor — no mention of the category filter behavior or result ordering — but nothing critical for correct invocation is missing.

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 coverage is 100% and the single optional 'category' parameter is fully documented with enum values and a default in the schema. The description adds no filtering semantics of its own — it never mentions the category filter — so it only reaches the baseline for full schema 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?

Specific verb ('List') plus a precisely scoped resource ('the HVAC services AtlantFlow offers'), with the full service catalog enumerated so an agent knows exactly what comes back. That enumeration also separates it from catalog-adjacent siblings like get_pricing or check_service_area, which pull different data.

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?

There is no statement of when to use this over alternatives, and no exclusions or prerequisites. The one bit of routing guidance that exists ('Omit for everything') lives in the schema, not the description, so the agent must infer the use case purely from the tool name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources