Skip to main content
Glama

Find address districts

find_address_districts
Read-onlyIdempotent

Use this when the user wants congressional district by address, state legislative district by address, or census tract by address with downloadable Excel and CSV files. US addresses only; up to 100 rows and 200,000 characters. Do not use for elected representative names or contact details.

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": {
      "addresses": "<addresses>"
    },
    "name": "find_address_districts"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressesYesUS addresses, one per line, or CSV with an Address or Street header; up to 200,000 characters. Example: 1437 Bannock St, Denver, CO 80202.

Output Schema

NameRequiredDescriptionDefault
countsYes
errorsYes
sourceYes
previewYes
downloadsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds practical constraints beyond annotations: US-only addresses, a 100-row cap, a 200,000-character cap, and downloadable Excel/CSV output. It does not discuss authentication or rate limits.

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 two sentences, front-loaded with the usage trigger and then the constraints and exclusion. Every sentence carries operational information with no filler.

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 one-parameter read-only lookup with an output schema and rich annotations, the description covers scope, exclusions, geographic limits, batch limits, and file outputs. The main remaining gap is the relationship to the sibling geocode_addresses tool.

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%, so the schema already explains the addresses field, line/CSV format, character limit, and example. The description adds a 100-row limit that is not present in the schema, which is useful. It adds no further address-format detail beyond that.

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 names the specific resources returned: congressional district, state legislative district, and census tract, all keyed by address. It also notes downloadable Excel/CSV files. It is clear, but it does not explicitly distinguish itself from the sibling geocode_addresses tool, so an agent must infer 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 Guidelines4/5

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

It gives a clear usage trigger (user wants district or tract by address) and an explicit exclusion (not for elected representative names or contact details). It also states US-only. It stops short of naming geocode_addresses as the alternative for coordinate lookup.

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