Delco Plumber Now

check_coverage

Read-onlyIdempotent

Check whether Delco Plumber Now (a plumber referral service) covers a town or ZIP in Delaware County, Pennsylvania. Returns whether it is covered and the town page.

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": {
      "location": "<location>"
    },
    "name": "check_coverage"
  }
}

Input Schema

Name	Required	Description	Default
`location`	Yes	Town name or 5-digit ZIP, e.g. "Havertown" or "19083"

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.4/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 useful return context — that the result includes a coverage verdict plus a town page — which matters since no output schema exists.

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?

Two short sentences, front-loaded with the verb and scope, then the return value. No filler or repetition of schema details.

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 single-parameter read with rich annotations and a described return, this is nearly complete. A minor gap is not stating what 'not covered' yields (e.g., whether the town page is absent).

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 schema already gives format examples for the single 'location' parameter, so the baseline is 3. The description adds genuine meaning by constraining the parameter to Delaware County PA towns/ZIPs, narrowing interpretation beyond the schema.

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 ('Check whether ... covers') and resource ('Delco Plumber Now', a plumber referral service) with explicit geographic scope. It is immediately distinguishable from siblings like get_price_range or request_contact.

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 domain and geographic applicability are stated up front ('a town or ZIP in Delaware County, Pennsylvania'), giving clear context for when this tool is the right one. It stops short of explicitly naming alternatives or saying what to do when a location is outside that county.

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

All Delco Plumber Now tools Inspect

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

Need Help?