Skip to main content
Glama

Find a lot in British Columbia

find_parcel
Read-only

Find the titled lot (ParcelMap BC parcel) for a BC street address, a PID, the plan in a legal description ("Lot 5, Plan KAP12345", or the old form with its land district, "KDYD, Plan 1234"), or a point. Returns each lot's PID (for parcel_report), plan, mapped area and report page. Only an exact civic address match is one lot (an address matched only with a fault or a tie lists its candidates instead, and one on a strata building lists the building, whose units each have their own PID); a street, block or point between lots lists the lots around the spot, nearest first, and a plan lists its lots (the open parcel map carries no lot numbers, so pick by plan and size, or on the page).

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_parcel"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoLatitude, with lon, instead of a query.
lonNo
queryNoStreet address with its town ("1234 Main Rd, Horsefly"), a PID ("026-022-109"), or a legal description or its plan number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only and closed-world annotations, it discloses important matching semantics: exact address matches return one lot, fault/tie cases list candidates, strata addresses return the building, and street/block/point searches list nearby lots nearest first. It also explains what a plan search returns and why lot selection may require plan and size.

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 key purpose and accepted inputs are front-loaded, and the dense parentheticals carry real matching and return-value details. The single long paragraph is information-rich but somewhat hard to scan, especially the nested address-match explanation.

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 lookup tool with no output schema, the description explains both the return fields (PID, plan, mapped area, report page) and the main matching edge cases. Annotations already cover safety behavior, and the description supplies the remaining operational context an agent needs.

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?

The description adds useful meaning to the query parameter by giving address, PID, legal-description, and old land-district plan forms, and clarifies that lat/lon form a point input. The schema already covers much of this, and lon itself receives no description, so it falls short of full parameter clarification.

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 states a specific verb and resource: find the titled ParcelMap BC parcel for a BC address, PID, legal description/plan, or point. It also names the sibling parcel_report in connection with the returned PID, helping distinguish downstream use.

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 input contexts and explains matching behavior for addresses, streets, blocks, points, and plans. It does not explicitly state when to choose this tool versus parcel_report, so guidance is strong but not fully comparative.

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