PropertyLabs

Search permits for a public address

search_address_permits

Read-onlyIdempotent

Look up the public PropertyLabs permit history for a specific civic address in a specific city. Use this for address-level construction history and activity. This follows the same public field boundary as PropertyLabs address pages and does not return applicant names, contractor names or permit numbers.

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>",
      "city": "<city>"
    },
    "name": "search_address_permits"
  }
}

Input Schema

Name	Required	Description	Default
`city`	Yes	Required PropertyLabs city slug, for example 'calgary', 'edmonton', 'toronto' or 'vancouver'.
`address`	Yes	Specific civic address, for example 8882 170 Street NW.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context by specifying the 'public field boundary' and explicitly listing excluded data (applicant names, contractor names, permit numbers), offering value beyond the annotations without contradicting them.

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 three sentences, each earning its place: the first states the action, the second gives the use case, and the third clarifies the scope of data returned. It is efficient, front-loaded, and free of 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?

With an output schema present, the description need not explain return values. It covers purpose, usage, limitations, and data scope, and is well-supported by clear annotations and parameter documentation. For a simple two-parameter read-only search tool, no significant gaps remain.

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?

The schema already provides descriptions for both parameters (address and city) with examples and coverage is 100%. The description restates 'specific civic address' and 'specific city,' but adds no new parameter-level detail beyond what the schema offers, so the baseline of 3 is appropriate.

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 verb 'Look up' and the resource 'public PropertyLabs permit history for a specific civic address in a specific city,' making the tool's purpose unambiguous. It also distinguishes itself from siblings by noting it is for address-level history and does not return applicant names, contractor names, or permit numbers, which helps an AI agent select it over get_public_permit.

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?

The description explicitly says 'Use this for address-level construction history and activity,' providing a direct usage directive. It also explains what it does not return, signaling when to prefer a different tool (e.g., when permit numbers are needed) and implicitly contrasts with get_public_permit.

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

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