Skip to main content
Glama

Get published prices and cost statistics

get_pricing
Read-onlyIdempotent

Published AtlantFlow prices (diagnostic, emergency call fee, tune-up, maintenance plan, financing) plus historical invoice statistics by job type (median and middle-half range, number of jobs). Only groups with 20+ jobs are published; no per-city prices. Statistics describe past invoices, not a quote.

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_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceNoOptional keyword to filter historical job statistics, e.g. 'replacement', 'leak', 'drain', 'thermostat', 'capacitor'. Omit to list everything.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: a 20-job minimum threshold before a group is published, the absence of per-city granularity, and the explicit warning that figures are historical invoice statistics rather than a quote. That threshold detail is the kind of constraint an agent could not infer from 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?

Three sentences with the deliverable front-loaded and scope caveats immediately after; every sentence carries information. The parenthetical enumerations are dense but functional rather than padded.

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?

With no output schema, the description does the work of describing returns (median, middle-half range, number of jobs), which is the key detail. Remaining gaps are minor: no pagination or result-size behavior and no statement of expected empty results when a service has fewer than 20 jobs.

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 'service' parameter is fully documented in the schema with examples. The description only restates the grouping dimension ('by job type') and adds no syntax, matching behavior, or edge-case guidance, so baseline 3 applies.

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 concrete verb-and-resource pair ('Published AtlantFlow prices ... plus historical invoice statistics by job type') and enumerates the price categories covered, so the agent knows exactly what comes back. It also implicitly separates itself from estimate_replacement_cost by stating 'Statistics describe past invoices, not a quote,' though it never names a sibling tool.

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

Usage Guidelines3/5

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

Usage is only implied through the scope statements ('no per-city prices', 'Statistics describe past invoices, not a quote'), which do tell the agent what this tool is not for. There is no explicit when-to-use instruction or pointer to alternatives such as estimate_replacement_cost or get_membership_and_financing, so routing still requires inference.

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