CleverTech MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLEVERTECH_API_KEY | No | Optional API key for higher query limits. Can also be passed as --api-key argument. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| property_searchA | Search for properties by address across 13+ Canadian cities. Returns assessment data including value, lot size, year built, and DLS coordinates. Supports sorting by assessed_value, address, year_built, community, and value range filtering. If no assessment results are found, falls back to Nominatim/OpenStreetMap forward geocoding; if the address resolves to a real location, returns a helpful message explaining why it may be missing from the assessment database (e.g. tax-exempt, new development, unit in larger parcel) instead of a plain '0 of 0'. |
| property_reportA | Get a consolidated property report — assessment data, building permits at this address, zoning information, and DLS coordinates in a single response. |
| property_by_rollA | Get a single property assessment record by its roll number. Faster than search when you already know the roll number. |
| property_topA | Get the top-N properties in a city sorted by assessed value, year built, or lot size. Perfect for finding the most expensive, oldest, or largest properties. Returns full assessment details for each result. |
| dls_convertC | Convert between GPS coordinates and Dominion Land Survey (DLS) grid system used in Western Canada. Supports GPS→DLS and DLS→GPS directions. |
| dls_batchA | Convert multiple GPS coordinates to DLS or multiple DLS strings to GPS in a single batch request. Up to 100 items per batch. |
| building_permit_searchA | Search building permits by address, contractor, applicant, or permit number across 13+ Canadian cities. Returns permit details including type, value, status, and dates. |
| building_permit_recentA | Get the most recently issued building permits for a city. Useful for monitoring new construction activity. |
| zoning_lookupA | Look up zoning district information for a GPS point or address in a Canadian city. Returns zone code, description, and district boundaries. |
| business_registry_searchA | Search the Canadian federal business registry. Find corporations by name, province, city, status, or industry act. |
| reverse_geocodeA | Convert GPS coordinates to a human-readable address, city, neighborhood, province, DLS grid reference, and — when available — the nearest property's roll number and assessed value. Works across all Canadian cities in the CleverTech database. |
| list_citiesA | List all available cities with their slugs, API capabilities, and property counts. Use this first to discover which cities are available and what services each supports. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools are clearly separated by resource and action: property search, roll lookup, permits, zoning, and DLS conversion each have distinct purposes. The only mild overlap is between property_report and the individual permit/zoning lookups, and between reverse_geocode and dls_convert, but the descriptions clarify scope well enough to avoid real confusion.
Tool names mostly follow a clear [domain]_[action] snake_case pattern like property_search, building_permit_search, and zoning_lookup. A few names like property_by_roll, property_top, and building_permit_recent deviate from the verb-oriented pattern, but the overall convention remains predictable and readable.
Twelve tools is well-scoped for a real-estate and land-data server: property data, permits, zoning, DLS conversion, geocoding, and business registry search are each represented without redundant tools. Each tool serves a distinct workflow, and the count feels proportional to the domain.
The tool surface covers the advertised domain thoroughly: property discovery, detailed reports, roll-based lookup, top listings, DLS conversion in single and batch modes, permit search and recent activity, zoning lookup, reverse geocoding, and city discovery. No obvious dead ends or missing core operations are apparent for a read-only data API.