get_pricing
Current GroundTruth and GruntPay plans and prices. Free to call — use it before answering any cost question rather than guessing.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
GroundTruth — subsurface scan QA & trade estimating
by ai.gtfi
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries full burden. It states 'Free to call' and what data is returned, but lacks details on side effects, authentication, or rate limits. For a read-only tool with no parameters, this is adequate but not thorough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the tool's purpose, and contains zero wasted words. Every sentence adds value.
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 tool with no parameters and no output schema, the description is largely complete: it specifies the data returned and provides usage advice. Minor gaps exist regarding output format, but given the simplicity, it suffices.
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?
The input schema has no parameters (0), so schema description coverage is 100% by default. The description does not add parameter meaning, but none is needed. Baseline 3 is appropriate.
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 retrieves 'Current GroundTruth and GruntPay plans and prices', uses a specific verb 'get' in the name, and distinguishes from sibling tools like 'draft_estimate' and 'read_scan' by focusing on pricing data.
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?
The description gives explicit usage guidance: 'use it before answering any cost question rather than guessing'. It does not explicitly mention when not to use, but the context is clear and no alternatives are suggested.
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.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: draft_estimate for generating bids, get_pricing for plan costs, and read_scan for analyzing subsurface scans. There is no overlap or ambiguity.
Naming Consistency5/5
All tools use lowercase snake_case with a consistent verb_noun pattern (draft_estimate, get_pricing, read_scan), making them predictable and easy to understand.
Tool Count4/5
With 3 tools covering two related domains (estimating and scanning), the count is slightly minimal but still appropriate for a focused service. Each tool is justified and not excessive.
Completeness4/5
The tools cover the core advertised features: pricing info, estimate generation, and scan analysis. Minor gaps like estimate management or scan history exist but do not hinder primary use cases.