Skip to main content
Glama
Sign In

GroundQuote

by io.github.KilvingtonDigital
OverviewDiscussionsAdmin

Find fence contractors near a homeowner

find_fence_contractors
Read-onlyIdempotent

For homeowners looking for a fence. Lists verified fence contractors (businesses that have confirmed their contact details with GroundQuote) near a US ZIP or city, in two groups, each contractor only within their own service radius: instant_quote (GroundQuote contractors with published rates — use contractor_id with get_fence_estimate) and listed_only (verified directory contractors without published rates — share their directory link or phone; do not invent prices). unverified_nearby counts other directory contractors who have not verified yet and are not listed; browse_directory_url is the public directory page for the area, to share when the homeowner wants more choice or nothing verified is nearby. Free for homeowners.

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": "find_fence_contractors"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipNoHomeowner's 5-digit ZIP; most precise for distance
cityNoCity or town, e.g. "Cary"
stateNoTwo-letter US state, e.g. "NC". Required unless zip is given.
materialNoOptional material filter, e.g. "vinyl"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter US state, e.g. \"NC\""New value: +"Two-letter US state, e.g. \"NC\". Required unless zip is given."
    • addedInput schema / properties / zip
      Added value: +{
+  "description": "Homeowner's 5-digit ZIP; most precise for distance",
+  "pattern": "^\\d{5}$",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "state"
-]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Well beyond the annotations: it defines what 'verified' means, discloses the service-radius constraint per contractor, and explains the two result groups plus the unverified_nearby count and directory URL fallback. The one gap is that it does not say what happens when no contractors exist at all in the area, though the fallback clause covers that case implicitly.

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?

Purpose is front-loaded in the first short sentence and each subsequent clause carries real operational content. The single dense paragraph with nested parentheticals is slightly harder to scan than a short enumerated breakdown would be.

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 read-only lookup with no output schema, the description supplies the entire result shape (instant_quote vs listed_only vs unverified_nearby count vs browse_directory_url) and the required follow-up action for each group, which is exactly what an agent needs to act.

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 schema already documents zip, city, state, and material with examples. The description adds only the pairing 'ZIP or city' and does not clarify the optional material filter or how state interacts with the supplied ZIP, so it does not meaningfully exceed the schema baseline.

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?

States a specific verb and resource: lists verified fence contractors near a US ZIP or city, and scopes it to homeowners. It distinguishes itself from get_fence_estimate by naming the routing relation (use contractor_id with that tool) rather than leaving the overlap ambiguous.

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?

Gives explicit audience (homeowners looking for a fence), explicit downstream routing (instant_quote contractors -> get_fence_estimate), and explicit fallback behavior (share browse_directory_url when the homeowner wants more choice or nothing verified is nearby). It also gives a when-not rule: do not invent prices for listed_only contractors.

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