TBG — The Brett Group

Check service area

check_service_area

Read-onlyIdempotent

Checks whether TBG serves a Maryland ZIP code or town for home projects, and which office issues building permits there.

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

Input Schema

Name	Required	Description	Default
`zip`	No	5-digit ZIP code of the property.
`town`	No	Town name, e.g. "Severna Park".

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful scope context (Maryland-only, home projects, returns permit office), but says nothing about what an out-of-area or invalid input yields.

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?

A single front-loaded sentence that states the domain constraint first and the return value second. Zero filler.

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 two-optional-parameter read-only lookup with no output schema, the description covers scope, geography, and the shape of the answer. The remaining gap (out-of-area behavior) is minor against annotations that already carry the safety profile.

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%, so both parameters are already documented; baseline 3 applies. The description adds a mild either/or hint ('ZIP code or town'), but does not state precedence when both are supplied or what happens if neither is provided.

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?

Clear specific verb+resource: checks service coverage for a Maryland ZIP/town and returns the permitting office. It is distinguishable from most siblings, though the permit-office component overlaps conceptually with get_local_permit_guidance and the description does not clarify the boundary.

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

Usage Guidelines2/5

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

No explicit when-to-use, prerequisites, or alternatives are stated. Usage (e.g., verifying coverage before submit_project_request) is only implied, and nothing tells the agent when this tool is the wrong choice versus get_local_permit_guidance.

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

All TBG — The Brett Group 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?