Skip to main content
Glama

BRAINIAC Official Property & Energy Lookups

Look up EPA radon zone by US county

property-official_epa-radon-zone-lookup
Read-onlyIdempotent

Return the EPA Map of Radon Zones zone (1–3) for a US county from the vendored EPA spreadsheet. Price $0.02 USDC. POST /api/v1/property-official/epa-radon-zone-lookup. An unpaid call returns the x402 payment terms and does not run.

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": {
      "state": "<state>",
      "county": "<county>"
    },
    "name": "property-official_epa-radon-zone-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesstate, string, length 2 to 40. Required.
countyYescounty, string, length 2 to 80. Required.

Output Schema

NameRequiredDescriptionDefault
matchesNomatches. Array.
sourcesNosources. Array.
actionLevelNoactionLevel. String.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: a $0.02 USDC price, a specific POST endpoint, and the fact that unpaid calls return x402 payment terms without running. It does not contradict the read-only, idempotent, non-destructive annotations.

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 front-loaded with purpose, then covers price, endpoint, and unpaid-call behavior in four efficient sentences. Every sentence adds operational value with no unnecessary wording.

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 simple two-parameter lookup with an output schema and rich annotations, the description covers purpose, cost, endpoint, and payment failure behavior. The main remaining gap is input formatting guidance for state and county values.

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 the schema already documents both required parameters. The description adds only that the lookup is for a US county; it does not clarify whether state should be a two-letter abbreviation or full name, or how county names should be formatted.

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?

The description uses a specific verb and resource: returning an EPA radon zone (1–3) for a US county. It is clear what the tool does, but it does not explicitly distinguish itself from sibling lookup tools beyond the different data domain.

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

Usage Guidelines3/5

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

Usage is implied by the narrow domain: look up a radon zone for a US county. The description does not state when to use this tool versus alternatives or when not to use it.

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.

Resources