OpenCityRecord

Find the covered government for a place

find_city

Read-onlyIdempotent

Which city or county government OpenCity covers for a place name or a street address, and whether it is in this account's cities. Returns the city_slug the other tools take. Discovery only: it returns no meeting records and never changes which cities this account can query.

WHEN: the user names a place or gives an address and you do not have its slug ('my council is in Lehi', 'I live at 153 N 100 E, Lehi'), or asks whether OpenCity covers somewhere. WHEN NOT: the slug is already known or in the cities list above — call the tool you need directly.

An address can be inside both a city and a county government; both come back. may_serve marks a town or township in the address's county whose boundary is not known: say it may serve the address, not that it does. When in_your_plan is false, do not call other tools for that city; tell the user it is covered but outside their account.

EXAMPLES: { "name": "Lehi, UT" } { "name": "Utah County" } { "address": "153 N 100 E, Lehi, UT 84043" }

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

Input Schema

Name	Required	Description
`name`	No	A city or county name, optionally with a state: 'Lehi', 'Lehi, UT', 'Utah County'.
`state`	No	Two-letter state to narrow a name search.
`address`	No	A full street address with city and state or ZIP: '153 N 100 E, Lehi, UT 84043'.

Output Schema

Name	Required	Description
`address`	Yes	Present for an address lookup.
`matches`	Yes
`plan_note`	Yes
`nearest_covered`	Yes	When the address is not in any covered government: the closest covered ones, for context. They do NOT govern the address.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description still adds real behavioral context: returns no meeting records, never changes the account's queryable cities, an address can resolve to both a city and a county, and may_serve means 'may' not 'does'. That is exactly the nuance an agent needs to avoid overstating coverage.

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?

Front-loaded purpose sentence, then WHEN/WHEN NOT blocks, then compact example arguments. Dense but every sentence carries a decision rule; no 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?

Output schema exists, yet the description still explains the fields that drive agent behavior (city_slug, may_serve, in_your_plan). For a three-optional-parameter discovery tool, nothing needed to invoke or act on results is missing.

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 baseline is 3, but the examples and prose add semantics beyond the schema: name vs. address usage paths and the dual city/county result for addresses. The state parameter is left to the schema alone, a minor gap.

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 and resource ('Which city or county government OpenCity covers for a place name or a street address') and explicitly scopes itself as discovery-only that returns the city_slug the other tools take. This differentiates it cleanly from the search/list siblings.

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

Usage Guidelines5/5

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

Explicit WHEN clause with concrete user phrasings and WHEN NOT routing the agent to call the needed tool directly when the slug is already known. It also handles the downstream decision when in_your_plan is false, so the agent knows not to call other tools.

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

All OpenCityRecord 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?