Charlotte-Mecklenburg MCP Server

by Lavoiedavidw

Overview Schema Related Servers Score Discussions

Python

Local

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.0
Disambiguation4/5
Most tools target distinct datasets (parcels, zoning, crime, planning, transportation), but the crime tools (crime_near, violent_crime_near, homicides_near) and planning tools (area_plans_at, get_planning_area) overlap in purpose and could cause misselection. Descriptions are detailed enough to resolve ambiguity.
Naming Consistency4/5
Names mostly follow a predictable pattern: [subject]_near for radius searches, [subject]_at for point-in-polygon lookups, and verb_noun (get_, lookup_, search_) for direct lookups. Minor deviations exist (geocode, get_planning_area vs area_plans_at) but the mixed conventions are still readable and consistent within their categories.
Tool Count4/5
21 tools is slightly heavy but justified by the wide scope of municipal data (geocoding, parcels, zoning, crime, transit, environment). Each tool covers a distinct dataset, so the count feels appropriate for the server's purpose.
Completeness4/5
The tool surface covers a broad range of civic data with read-only queries, and list_datasets helps discover additional layers. Minor gaps exist (e.g., no generic query tool for arbitrary layers, no parks or building permits) but agents can work around these for most core workflows.
Average 4.6/5 across 21 of 21 tools scored. Lowest: 4/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 19 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.
If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.
MCP servers without a LICENSE cannot be installed.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosing behavior. It does add useful interim behavior: 'Queries both the point layer ... and the line layer ... and merges the results,' and it describes the return dict. However, it does not mention potential error conditions, geocoding dependency for addresses, result ordering, or limits. For a read-only search tool, this is acceptable but not comprehensive.
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?
The description is front-loaded with the core purpose, followed by a concise layer-merging detail and a compact Args list. The format is a bit longer than strictly necessary but every sentence earns its place; the Args contributions clarify parameter semantics not present in the schema. No unnecessary fluff or repetition.
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?
Given the absence of an output schema and annotations, the description compensates by explicitly listing the return fields (resolved location, project list, summary) and the two-layer behavior. It covers the primary usage modes and parameters. It lacks edge-case handling (e.g., what happens with no results or invalid coordinates), but for a relatively simple spatial search tool, this is nearly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Even though the schema coverage is 0%, the description's Args section fully explains each parameter. It states that address is used instead of lat/lon, clarifies the mutual exclusivity ('Provide this OR lat/lon'), and gives the default for radius_m. This adds significant semantic meaning beyond the bare schema types and defaults, making parameter usage unambiguous.
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?
The description opens with 'Find CATS (Charlotte Area Transit System) capital projects near an address or coordinate,' which clearly names the specific resource (CATS capital projects) and the action (find near location). It also explicitly notes that it queries both point and line layers, further distinguishing it from sibling tools like cip_projects_near or crime_near. This is a specific verb+resource+scope statement.
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?
The description implies when to use the tool (for CATS projects near a location) and explains the address-or-coordinate input modes, but it does not explicitly contrast it with alternatives such as cip_projects_near or mention any exclusions. Usage context is clear enough for an agent to select it for transit-related proximity searches, but direct guidance against using other tools is absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden. It discloses the output structure (resolved location, lists under 'ramps', 'parking', 'signals', and a 'summary' sentence) and the address/lat-lon exclusivity. Yet it omits behavioral edge cases such as no-results behavior, invalid address handling, or rate limits, leaving some gaps.
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 well-structured: a one-sentence summary, a coverage note, a clearly labeled Args section, and a Returns section. Every sentence contributes meaningful information without redundancy, and key details are front-loaded.
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 read-only search tool, the description is largely complete: it covers purpose, parameters, and return format. The return structure is explicitly described because no output schema exists. Minor omissions include error handling and geocoding caveats, but these do not significantly hinder usability.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, so the description's 'Args' section fully compensates. It explains each parameter's meaning and constraints: address is free-form and mutually exclusive with lat/lon, radius_m has a default of 400 meters, and feature_type enumerates its allowed values. This adds semantic depth beyond raw names and types.
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?
The description opens with a specific action: 'Find ADA pedestrian infrastructure near an address or coordinate.' It names the exact resource (ADA infrastructure) and lists covering curb ramps, accessible parking, and accessible signals, which clearly distinguishes it from sibling tools like crime_near or bike_lanes_near.
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?
The description communicates when to use the tool: when ADA pedestrian infrastructure near a location is needed. It provides clear usage context by explaining address vs. lat/lon ('Provide this OR lat/lon') and the feature_type option. However, it does not explicitly name alternatives or state when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the scope of projects (stormwater, active/completed) and the return structure ('resolved location, a list of CIP projects...and a summary'), which is useful. However, it does not mention potential errors, rate limits, or confirm read-only behavior, leaving some gaps.
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 well-structured and appropriately concise: a clear opening sentence, a supportive scope sentence, a neatly formatted Args list, and a Returns section. No redundant text; every part contributes to understanding.
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 read-only geospatial query tool with 4 parameters and no output schema, the description covers the necessary input and output essentials. It could elaborate on coordinate format or error handling, but it is largely complete for this simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, but the description explicitly defines all four parameters in the Args section, including the relationship between address, lat/lon, and the radius_m default. This fully compensates for the schema's lack of descriptions, providing clear semantic meaning.
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?
The description clearly states the tool's function: 'Find Mecklenburg County Capital Improvement Projects (stormwater) near an address or coordinate.' It uses a specific verb ('Find') and resource ('CIP projects') with geographic and thematic context, distinguishing it from siblings like crime_near or homicides_near.
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?
The description provides clear usage context by explaining the two input modes ('Provide this OR lat/lon') and the default radius. It does not explicitly mention alternatives or when not to use the tool, but the instructions for address vs. coordinate input are a practical usage guideline.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses the underlying geocoder (Esri World), the output structure (matched address, lat, lon, match score, and a summary), and gives an example. It does not mention error handling or edge cases, but for a read-only lookup tool, this is adequate transparency.
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 concise and well-structured: a one-sentence purpose, followed by Args and Returns sections. Every sentence serves a purpose, and the main functionality is front-loaded.
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?
Given the tool is a simple one-parameter geocoder with no annotations or output schema, the description is complete: it explains what the tool does, the input format, and the return structure. No additional information is needed for an agent to select and invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides only a title for the single 'address' parameter (0% description coverage). The description compensates fully with an 'Args' section explaining it is a free-form address string and provides a concrete example ('2437 Remount Rd, Charlotte, NC'), adding meaningful value beyond the schema.
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?
The description clearly states the tool geocodes a free-form address to lat/lon using the Esri World geocoder, specifying both the action and the resource. This distinguishes it from sibling tools which are all data lookups (e.g., lookup_parcel, crime_near) rather than address-to-coordinate conversion.
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?
The description implies usage through its purpose statement ('Geocode a free-form address to lat/lon'), and the example shows a typical input. However, it does not explicitly state when to prefer this over alternatives or provide any exclusions, so guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It transparently explains that it runs a point-in-polygon query, that overlapping boundaries can yield multiple matches, and that all matches are returned. It also lists return fields. It does not mention error conditions or data freshness, but for a read-only query tool, this is strong disclosure.
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 well-structured: a lead sentence stating purpose, a sentence about input alternatives, a behavior explanation, and a structured Args/Returns section. Every sentence contributes useful information without redundancy or fluff.
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?
The description covers input constraints, query behavior, overlapping boundary handling, and return fields. Since an output schema exists, it needn't detail return values, but it does anyway. It lacks explicit error handling or permission info, but for a point-query tool with this level of explanation, it is nearly complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, but the description fully compensates by documenting each parameter: address is a free-form string, lat and lon are used together if address is not given. This clarifies the relationship among parameters and their intended usage, going well beyond the schema's simple nullability.
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?
The first sentence clearly states the verb and resource: 'Find adopted area/small-area plan boundaries containing a point.' This distinguishes it from sibling tools by focusing specifically on plan boundaries and using a point query. The mention of overlapping boundaries adds specificity.
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 provides clear context for when to use the tool: when you need to identify which area plans cover a point. It also gives input alternatives (address vs. lat/lon). However, it does not explicitly name alternatives or exclusion scenarios, so it lacks the direct 'when-not-to-use' guidance of a top-tier description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It discloses that address input 'will be geocoded', that lat/lon must be used together, and specifies the return shape: 'Dict with parcels (list of parcel attribute dicts), count, and a summary string.' This exceeds a minimal lookup description, though it omits edge-case behavior such as error handling or ambiguous match resolution.
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 the core purpose and then organized into Args and Returns sections. Every sentence is informative, with no filler or repetition. It is appropriately sized for a tool with five optional parameters.
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?
Given no annotations and no output schema, the description covers the essential aspects: purpose, all parameter semantics, mutual-exclusion rule, geocoding behavior, and return structure. Minor gaps exist (e.g., no mention of failure modes or what happens if multiple parcels match), but overall it is complete enough for an agent to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides only names, types, and defaults with 0% description coverage. The description fully compensates with per-parameter details: free-form address examples, WGS84 coordinate system, the lat/lon mutual requirement, 8-digit PID format, and example values for pid and nc_pin. This adds substantial meaning beyond the raw schema.
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?
The description opens with a specific verb and resource: 'Look up Mecklenburg County parcel(s) from the ParcelStatus layer.' It clearly distinguishes itself from siblings by focusing on parcel lookup via multiple identifiers (address, lat/lon, pid, nc_pin), which differentiates it from geocoding and proximity tools.
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?
The description gives explicit usage guidance: 'Provide exactly one way to locate the parcel' and lists the four mutually exclusive input methods with their required counterparts (e.g., lat requires lon). It does not explicitly name alternative sibling tools or state when not to use this tool, but the context is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the multi-geography stacking, the selection of finest level as 'primary', the inclusion of all matched levels under 'by_geography', and the preference for Neighborhood Profile Area. It also specifies input modes and return structure, providing substantial behavioral detail beyond the bare schema.
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?
The description is front-loaded with a concise summary, followed by focused Args and Returns sections. It is somewhat lengthy due to the detailed return field list, but each section serves a purpose and the structure aids readability. Earns a high score, though not perfectly minimal.
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 tool with three parameters, no annotations, and a known output schema, the description fully covers input constraints, output structure, data source, and selection logic. It provides enough context for an agent to select and invoke the tool correctly without ambiguity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides no descriptions (0% coverage), but the description compensates with an Args section explaining 'address' as free-form, and 'lat'/'lon' as used together if address is absent. This adds meaning beyond the nullable/default schema properties, clarifying the mutual exclusivity and usage.
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?
The description opens with a specific verb and resource: 'Get tree canopy stats for the area containing a location.' It clearly states the point-in-polygon query against a named layer, distinguishing it from sibling tools that handle other data types like watershed or area plans.
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?
The description provides clear input guidance ('Provide either address or both lat/lon') but does not explicitly discuss when to prefer this tool over alternatives or when not to use it. Usage context is implied by the data source description, but no exclusions or sibling comparisons are made.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of describing behavior. It discloses the default radius, the option to supply coordinates or an address, and the return structure including a resolved location and summary sentence. While it does not explicitly label the tool as read-only, the 'Find' wording makes that clear, and the detailed return description adds useful behavioral context.
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 well-structured with separate Args and Returns sections, and the opening sentence immediately states the purpose. Every sentence adds value, explaining parameters or expected output without unnecessary fluff.
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?
Given that there are no annotations and no output schema, the description is remarkably complete. It covers all four parameters, explains the input alternatives, and describes the return structure with specific segment fields. This is sufficient for an agent to invoke the tool and interpret the result appropriately.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It does so thoroughly by explaining each parameter: address, lat/lon, and radius_m with its default value. It also clarifies the OR relationship between address and lat/lon, which is not obvious from the schema alone.
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?
The description begins with a specific verb and resource: 'Find bike lanes near an address or coordinate.' This clearly identifies the tool's function and differentiates it from the many sibling 'near' tools by focusing on bike lanes as the subject. The location input options are also stated upfront.
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?
The description provides clear context: it is for finding bike lanes near a user-specified location, and it explains how to provide that location (either address or lat/lon). It does not explicitly mention alternatives or when-not-to-use, but the context is unambiguous and sufficient for an agent to select this tool for bike lane queries.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It explains that the tool queries a recorded points layer, the input modes, and the return structure including resolved_address and summary. It does not cover potential error cases or rate limits, but for a straightforward read-only query this is adequate.
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 well-structured with a summary sentence, a context sentence, an Args block, and a Returns block. Every sentence adds value; there is no fluff. The docstring format makes it easy to parse quickly, and the most important information (purpose) is front-loaded.
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?
Although the output schema is marked as present, the description's Returns section fully enumerates the response fields, making the tool self-contained. It covers geocoding implications via resolved_address, radius default, and the county scope. For a tool with 4 parameters and a clear purpose, this description is complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It does so thoroughly: each parameter (address, lat, lon, radius_m) is explained with examples and defaults. The crucial constraint that address is mutually exclusive with lat/lon is clearly stated, adding substantial meaning beyond the flat schema.
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?
The opening sentence 'Find recorded brownfield sites within a radius of a location' uses a specific verb ('Find'), a clear resource ('recorded brownfield sites'), and a scope ('within a radius'), which fully distinguishes it from the many other 'near' sibling tools. It also specifies the geographic context (Mecklenburg County), leaving no ambiguity about what the tool does.
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?
The description provides explicit usage instructions: 'Provide either ``address`` or both ``lat``/``lon``.' This clearly explains how to invoke the tool, but does not explicitly mention when to choose this tool over alternatives like crime_near or homicides_near. Since the resource type is obvious from the name and purpose, this is a minor gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full transparency burden. It explains the underlying method (point-in-polygon query against the City of Charlotte Solid Waste polygon layer) and the output structure (per-stream day, provider, route, recycling week). It does not mention error handling or edge cases, but this is a solid disclosure.
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 well-structured with Args and Returns sections. Every sentence adds value: describing the query method, parameter options, and return fields. It is appropriately sized for the tool's complexity without extraneous information.
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?
Given the tool has an output schema and the description already explains the return dict, parameters, and data source, the description is complete for an agent to select and invoke the tool correctly. No significant gaps are present.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage, but the description fully compensates. Each parameter (address, lat, lon) is clearly defined, including examples and the relationship between them (address vs lat/lon). This is exactly what parameter semantics should provide.
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?
The description opens with a specific verb and resource: 'Look up garbage, recycling, and yard waste collection schedule.' It clearly distinguishes this from sibling tools (crime, zoning, projects, etc.) and even specifies the City of Charlotte context in the second sentence.
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?
The description provides explicit usage instructions: 'Provide either address or both lat and lon,' with details on how each parameter is used. It does not explicitly name alternative tools, but given the unique focus on trash schedules, the usage context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently explains that the tool first resolves the parcel against ParcelStatus if pid is not supplied, then performs the zoning lookup. It also warns that zoning may be None and mentions dependencies like 'Requires lon' for lat. This gives a solid understanding of the tool's internal behavior, though it stops short of detailing error handling.
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 well-structured and appropriately sized. It front-loads the purpose, then explains the resolution process, followed by a concise Args section and Returns section. Every sentence adds value without unnecessary fluff or repetition.
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?
The description is contextually complete for a tool with 4 optional parameters, no annotations, and no output schema. It explains the return format (dict with zoning, pid, summary), covers all parameters, and describes the lookup workflow. This gives an agent everything needed to invoke it correctly and interpret results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Given that the input schema has 0% description coverage, the description fully compensates by explaining each parameter in detail: address example, coordinate system for lat/lon, the dependency between lat and lon, and the meaning of pid. This goes well beyond the schema's bare type definitions, providing essential usage semantics.
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?
The description opens with a specific verb and resource: 'Get zoning classification for a parcel from Parcel_Zoning_Lookup.' This clearly identifies the tool's function and distinct purpose compared to siblings like lookup_parcel or get_planning_area. It also explains the resolution process, further clarifying its role.
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?
The description provides clear usage context by explaining the three accepted input methods (address, lat/lon, or pid) and the resolution workflow. It does not explicitly state when not to use this tool or name alternative tools, but the context is clear enough for an agent to decide to use it when a zoning classification is needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden and does well by disclosing that this is a genuine point+radius spatial query with a DATE_REPORTED where-clause, and that data is public per victim since 2015. It does not mention potential rate limits or error cases, but the disclosed spatial/behavioral details are substantial.
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 longer than average but every sentence earns its place: it explains the layer's nature, the query approach, why defaults are wider, and provides structured Args/Returns sections. It is well-organized, front-loaded with purpose, and free of fluff.
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?
Given the tool's complexity (point query with two alternative input modes, spatial and temporal filters), the description is complete. It covers inputs, defaults, output structure, and notable behavioral differences. The explicit Returns section and mention of breakdown/weapon counts satisfy what the agent needs to know.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It does so thoroughly with an Args section explaining each parameter, including defaults, the address example, and the lat/lon pairing requirement. This adds meaning far beyond the raw schema.
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?
The description opens with a specific verb+resource: 'Homicide incidents near a point, from the point-level CMPD_Homicide layer.' It clearly distinguishes itself from aggregate crime tables by noting 'CMPD_Homicide is a real point Feature Layer', which differentiates it from sibling tools like crime_near and violent_crime_near.
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?
The description gives clear usage context: 'Provide either address (free-form string) or both lat and lon' and explains why defaults are wider ('Homicides are rare'). It implicitly contrasts with aggregate crime tables, but does not name explicit alternative tools or state when not to use this tool, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description details search semantics (case-insensitive substring across service/layer/field names), source filters, and return structure including the 'broken' field. Since no annotations are provided, this thorough explanation covers the behavior well, but it could explicitly state read-only or note pagination/error behavior.
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 well-structured with a one-sentence purpose, a usage note with examples, and labeled Args/Returns sections. Every sentence contributes information without redundancy.
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 discovery tool with three optional parameters and a structured output, the description covers all necessary semantics, workflow context, and return shape. It's self-sufficient even without the output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema coverage, the description fully compensates by explaining each parameter: keyword's substring matching and omission behavior, source's allowed values, and limit's default. This adds meaning beyond the bare schema.
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?
The description uses a specific verb 'Search' and names the resource 'Charlotte/Mecklenburg ArcGIS endpoint registry'. It clearly distinguishes itself from sibling spatial/attribute tools by positioning itself as a precursor step to discover the correct layer.
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 provides explicit guidance to use this tool 'before calling a spatial/attribute tool', with concrete examples. This establishes proper workflow context, though it doesn't name specific alternative tools or include 'when not to use' exclusion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full disclosure burden. It effectively discloses the lack of an open/closed status field, the internal field observation proxy, the 'most recent first' ordering, and the point+radius query mechanism. It does not cover edge cases like the precedence if both address and lat/lon are provided, and there is no mention of permissions or rate limits, but for a read-only query tool the disclosed behaviors are significant.
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 concise yet complete, leading with a one-sentence summary of the tool's purpose, then clearly separating Args and Returns. Every sentence adds value: the note about the missing status field, the parameter explanations, and the output structure are all essential. No filler or repetition.
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?
Given the tool's complexity (6 optional parameters with conditional requirements), no annotations, and no schema-level descriptions, the description provides a thorough overview. It explains the input alternatives, the return payload fields, and the subtle field semantics. The presence of an output schema reduces the need to dive deeper into exact return types, but the description still covers the key behavioral context. The description is complete enough for an agent to select and use this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides almost no descriptions (0% coverage), so the description must fully compensate. It does: 'address' is explained as a free-form string with an example, 'lat'/'lon' are described as a pair used when address is not given, 'radius_m' has a default and meaning, 'days' is explained, and 'limit' is explained. This goes far beyond the schema's raw types and defaults.
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?
The description opens with '311 service requests near a point, from the point-level ServiceRequests311 layer,' which clearly states a specific verb, resource, and scope. It distinguishes itself from sibling 'near' tools by clearly targeting 311 service requests and noting the spatial query type.
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?
The description gives clear context on how to invoke the tool: the address vs lat/lon alternatives, the radius, days filter, and limit. It also notes the absence of a status field, which guides result interpretation. However, it does not explicitly name alternative tools or state when not to use this tool, so it misses the full 'explicit exclusions/alternatives' bar.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It clearly states this is a read-only lookup ('Look up', 'Point-in-polygon query') and describes the exact input alternatives and return fields. It does not mention error conditions or rate limits, but for a simple lookup tool the disclosure is strong.
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 well-structured with a one-sentence summary, a concise mechanism explanation, then Args and Returns sections. Every part adds value without redundancy. The front-loaded summary quickly tells the agent what the tool does.
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?
The description covers the full workflow: what the tool finds, which layer it queries, the geographic coverage, how to provide inputs, and what the return dict contains. Given the low parameter count and presence of an output schema, this is complete and ready for an agent to use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, but the description fully compensates by explaining each parameter's role and the mutually exclusive relationship: 'Provide either ``address`` or both ``lat``/``lon``.' It also specifies address format with an example and clarifies that lat/lon are used only if address is not given.
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?
The description opens with a specific verb phrase 'Look up the named watershed/basin containing a location' and identifies the exact data layer ('City of Charlotte "Watershed Basins" layer'). It clearly distinguishes this from sibling 'at' tools like area_plans_at or tree_canopy_at by naming the resource and the point-in-polygon mechanism.
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?
The description gives explicit usage context: 'Provide either ``address`` or both ``lat``/``lon``.' It also states the geographic coverage ('covers all of Mecklenburg County'), which helps the agent decide if the tool is appropriate. It does not explicitly list alternative tools, but the context is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully discloses important behavioral traits: the data source is the county recycling drop-off layer, the results are not battery-specific kiosks but multi-material sites, and only five sites exist countywide, justifying the large default radius. This goes well beyond the schema's structured information.
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 well-structured and appropriately sized: a crisp one-line summary, a brief limitation note, then organized Args and Returns sections. Each sentence contributes necessary information without redundancy.
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?
The tool is complete in context: it explains the conditional input requirements, the data limitations, the default behavior, and what the return dictionary contains. Since an output schema exists, the explicit Returns summary is a helpful supplement, and the conditional logic is fully addressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, but the description compensates by explaining every parameter: address is free-form, lat/lon are used together when address is absent, and radius_m has a default with a reason. This adds meaning that the bare schema properties completely lack.
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?
The description uses a specific verb and resource: 'Find battery/household-hazardous-waste recycling drop-off sites near a location.' It also differentiates from sibling tools by clarifying this queries the Mecklenburg County recycling drop-off centers point layer and that there is no battery-specific kiosk layer, making the tool's exact scope clear.
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 clearly states when to use the tool: provide either an address or both lat/lon. It also gives practical context by explaining the default radius and the sparsity of sites. However, it does not explicitly mention a sibling alternative or when not to use this tool, though the caveat that batteries are only one of several accepted materials serves as a partial exclusion.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does so thoroughly. It discloses the data aggregation methodology, the NPA resolution via 311 request density, and the exact computation (sums CALL_COUNT by CALL_DESCRIPTION) — information that goes far beyond a simple read operation and gives the user a clear mental model of behavior.
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 long but every sentence earns its place: a one-line summary, a necessary methodological caveat, a concise Args list with defaults, and a Returns summary. It is well-structured and front-loaded with the most essential fact first.
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?
The tool has 6 parameters, no required ones, and an output schema, but the description still provides complete context: it explains the data's nature, the resolution strategy, parameter meanings, and return fields. Even without the output schema, an agent would know what to expect. No gaps remain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, yet the description explains every parameter in Args, including defaults and special behaviors (e.g., 'the breakdown totals cover all matching months, not just the returned records' for limit). This fully compensates for the schema's lack of descriptions.
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?
The first line states the exact purpose: 'CMPD calls-for-service (patrol + domestic violence) near a point.' This clearly distinguishes it from sibling tools like homicides_near or service_requests_near by specifying the dataset and the spatial query nature.
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?
The description gives explicit input guidance: 'Provide either address or both lat and lon.' It also explains the underlying data limitation (no incident-level geometry, monthly aggregate by NPA) which tells the user when this tool is appropriate. However, it does not explicitly mention when not to use it or name alternatives, so it falls short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states that it runs a point-in-polygon query, returns None if no polygon covers the point, and describes the resolved_address and summary fields. This goes beyond the input schema to explain what happens during execution and what the user can expect in return.
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 well-structured and appropriately sized. It opens with a clear one-sentence summary, followed by an Args section and a Returns section. Every sentence contributes useful information, with no filler or repetition of schema details. The layout is easily scannable.
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?
The tool has an output schema, but the description still explains the return fields (planning_area, planning_region, lat, lon, resolved_address, summary) and provides context about the layers (e.g., 'one of Charlotte's 15 named community planning areas'). This makes the tool fully self-contained for an agent to invoke correctly without external knowledge.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. The Args section adds meaning to each parameter: address is a free-form string with an example, lat and lon are used together when address is not given. This fully clarifies the schema fields, which only provide types and defaults without descriptions.
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?
The description clearly states the tool's purpose: 'Look up the community planning area (and CCW planning region) at a point.' It uses a specific verb and resource, names the exact layers queried, and distinguishes itself from sibling tools like lookup_parcel and get_zoning by specifying its unique point-in-polygon query against Community_Planning_Areas and Center_Corridor_Wedge.
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?
The description provides clear usage context: 'Provide either address (free-form string) or both lat and lon.' It explains the input alternatives and the underlying query mechanism. However, it does not explicitly mention when not to use this tool or name alternatives, though the specificity of the purpose makes usage inferable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully carries the transparency burden. It explicitly discloses the layer name, the Decision='App' filter, the surprising fact that the layer also contains deferred/withdrawn petitions despite its name, and the sort order (most recently approved first). This is rich behavioral detail beyond a simple 'find' statement.
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 a one-sentence summary, followed by well-structured Args and Returns sections. Every sentence adds value, including the example address and the caveat about deferred/withdrawn petitions, with no redundant or filler content.
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?
Even though an output schema exists, the description goes beyond it by enumerating the exact fields returned in each rezoning dict and the top-level response keys. It covers the alternate input modes, defaults, and layer filtering nuances, making it fully self-contained for an agent to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero descriptions (0% coverage), so the description must compensate. It provides thorough per-parameter meaning: address is a free-form string with an example, lat/lon are used together only when address is absent, radius_m defaults to 1600 meters (~1 mile), and limit defaults to 25. This fully clarifies the ambiguous optional parameters.
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?
The description opens with a clear verb ('Find') and specific resource ('approved rezoning petitions near a point'), immediately distinguishing itself from sibling 'near' tools by focusing on approved rezonings and explicitly filtering to Decision='App'. It also names the exact underlying layer, leaving no ambiguity about the tool's scope.
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?
The description provides clear usage context by explaining the two location input modes (address vs. lat/lon), the radius default with an approximate mile equivalent, and the limit default. However, it does not mention alternative tools or state when not to use this tool, so it lacks explicit exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It fully discloses matching semantics (case-insensitive substring for nhood, exact for zip/status), the limiting behavior via 'limit', and a known data-quality issue (status nulls) with reassurance that it's not a client bug. This is exemplary transparency.
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 well-structured: a one-sentence purpose, brief operational notes, a caveat, a concise Args list, and a Returns line. Every sentence adds value; there is no fluff or redundancy.
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?
Given the tool's complexity (4 optional filter params, no output schema, no annotations), the description is complete: it explains matching semantics, default behavior, data caveats, and return value shape. An agent has enough to invoke it correctly and interpret results.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides zero description coverage, but the description includes an Args section that defines each parameter with type examples, default behavior, and matching rules. This fully compensates for the schema's lack of semantic information.
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?
The description opens with 'Search active Mecklenburg County tax foreclosures,' using a specific verb and resource, clearly indicating the tool's purpose. The scope ('active', county-specific) distinguishes it from sibling parcel/lookup tools like lookup_parcel.
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 states that all filters are optional and combined with AND, and explains the default behavior when omitting all filters. It also provides a concrete note about the status field data gap and its impact on filtering, though it does not explicitly name alternative tools or when to choose them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for behavioral disclosure. It thoroughly explains the aggregated nature of the data, the resolution mechanism via 311 density, the summation logic, and the output structure. This gives users a clear understanding of the tool's limitations and behavior.
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 well-structured with a clear opening summary, an Args section, and a Returns section. It is front-loaded with the primary purpose. Each sentence adds substantive detail, and the formatting makes it easy to scan. No wasteful repetition.
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?
The description covers all essential aspects: the tool's purpose, input modes, data caveats, parameter roles, and return keys. Despite the existence of an output schema, the description adds valuable context about data aggregation and resolution that a schema cannot convey. It is sufficiently complete for an agent to select and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must fully compensate. It does so by providing detailed explanations for every parameter: address (with example), lat/lon (with conditional usage), radius_m, days, and limit (including its effect on records vs breakdown). This exceeds the schema's minimal property names and defaults.
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?
The description clearly states the tool's function: 'CMPD violent-crime offense counts (Homicide/Rape/Robbery/Assault/...) near a point.' This specifies the verb (counts), resource (violent-crime offenses), and scope (near a point), effectively distinguishing it from siblings like crime_near and homicides_near.
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?
The description provides clear usage context, explaining the input modes ('Provide either address or both lat and lon') and the data limitations. It references the sibling tool crime_near, but does not explicitly state when to use this tool versus alternatives such as crime_near or homicides_near, so it stops short of a perfect score.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![Charlotte-City-MCP MCP server](https://glama.ai/mcp/servers/Lavoiedavidw/Charlotte-City-MCP/badges/card.svg)](https://glama.ai/mcp/servers/Lavoiedavidw/Charlotte-City-MCP)

Score Badge

Copy to your README.md:

[![Charlotte-City-MCP MCP server](https://glama.ai/mcp/servers/Lavoiedavidw/Charlotte-City-MCP/badges/score.svg)](https://glama.ai/mcp/servers/Lavoiedavidw/Charlotte-City-MCP)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Lavoiedavidw/Charlotte-City-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server