Skip to main content
Glama
Sign In

GroundQuote

by io.github.KilvingtonDigital
OverviewDiscussionsAdmin

Let the homeowner draw their fence on a map

open_quote_map
Read-onlyIdempotent

Opens one GroundQuote contractor's interactive satellite map inside the chat. The homeowner finds their property, draws the fence line, picks material and height, and sees that contractor's price from measured footage; the map asks for their name, email and phone first, and those go to that contractor when the price is shown; they can also book a site visit right in the map (the same lead the contractor gets from their website: $5 browsing, $15 with a visit, billed to the contractor only on unlock). Tell the homeowner this before opening the map. Prefer this over get_fence_estimate and over sending a website link when the homeowner is able to draw: it opens inside the chat. Use a contractor_id from the instant_quote group of find_fence_contractors. GroundQuote does not email or text the homeowner; the contractor contacts them.

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": {
      "contractor_id": "<contractor_id>"
    },
    "name": "open_quote_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
contractor_idYescontractor_id from find_fence_contractors (instant_quote group)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Adds substantial context the annotations cannot carry: contact details (name, email, phone) are collected before pricing and go to that contractor, site visit booking is possible, the lead is billed at $5 browsing / $15 with a visit to the contractor on unlock, and GroundQuote does not follow up (the contractor does). The only residual concern is a mild tension between the billable lead/booking behavior described and readOnlyHint=true, but the description discloses it openly rather than hiding it. Return format (pricing shown in-map) is covered.

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?

Front-loaded with the action and effect, and every clause carries information (behavior, disclosure duty, alternative routing, param provenance). It is a dense run-on with semicolon-chained clauses that would read better as short sentences or bullets, which costs it one point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, no-output-schema tool, nothing an agent needs to call it correctly is missing: what it does, which id to pass, what the homeowner experiences, what must be disclosed first, and when to choose it over alternatives.

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 coverage is 100% and the single parameter is self-documented, so the baseline is 3. The description earns a 4 by adding provenance semantics beyond the schema: the id must come from the instant_quote group of find_fence_contractors, implying other contractor ids are not valid.

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 and resource: 'Opens one GroundQuote contractor's interactive satellite map inside the chat,' followed by what the homeowner does in it (find property, draw fence line, pick material/height) and what they get back (that contractor's measured price). It is immediately distinguishable from get_fence_estimate and from sending a link.

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

Usage Guidelines5/5

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

Explicit routing: 'Prefer this over get_fence_estimate and over sending a website link when the homeowner is able to draw,' with the reason (opens inside the chat). It also names the upstream dependency ('Use a contractor_id from the instant_quote group of find_fence_contractors') and states the required pre-call behavior ('Tell the homeowner this before opening the map').

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

All GroundQuote toolsInspect
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