Skip to main content
Glama

Is this address in an Opportunity Zone?

lookup_address
Read-onlyIdempotent

Geocodes a US street address (Census Bureau geocoder, falling back to OpenStreetMap; tract assignment by the FCC Census Block API) and returns its 2018 Opportunity Zone status (2010 tract), its status for the 2027 designation round (2020 tract: eligible, nominated or certified, with source), the rural flags, and Census ACS tract statistics.

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": {
      "address": "<address>"
    },
    "name": "lookup_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesOne-line US address, e.g. '2 Woodward Ave, Detroit, MI 48226'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety bar is low; the description instead adds substantive behavior: three external services with a fallback chain (Census geocoder, then OpenStreetMap, then FCC Census Block API for tract assignment) and a version split between 2010-tract 2018 designations and 2020-tract 2027-round status with a source field. What is missing is failure/ambiguity behavior (failed geocode, multiple matches) and latency or rate constraints of the external services.

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?

A single sentence, front-loaded with the action and immediately followed by the return payload, with no filler. It is dense with parenthetical data-source detail, which is justified but makes it a slightly heavy read.

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?

With no output schema, the description carries the burden of explaining returns and does so concretely (both OZ vintages, source field, rural flags, ACS stats). It is nearly complete for a single-parameter lookup; only error and no-match behavior remain unstated.

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?

There is only one parameter and schema coverage is 100%, with the schema supplying the format and an example ('2 Woodward Ave, Detroit, MI 48226'). The description adds nothing about the address parameter itself (formats tolerated, whether ZIP is required, ambiguity handling), so the baseline 3 for schema-does-the-work applies.

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 (geocodes) and resource (US street address) and enumerates exactly what is returned: 2018 OZ status on 2010 tract, 2027-round status on 2020 tract, rural flags, and ACS tract statistics. This is precise enough to separate it from siblings like get_tract, lookup_coordinates, and check_qozb, which operate on tracts or coordinates rather than a full address-to-OZ join.

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 input shape: hand it a one-line US address when you need OZ status. However, the description never states when to prefer this over lookup_coordinates (geocoding only) or get_tract (tract-level lookups), nor does it mention prerequisites or exclusions such as non-US or non-street addresses.

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