Skip to main content
Glama

A BC lot's public-record report

parcel_report
Read-only

One lot's report by PID: for each section a status (flag = look into, clear = nothing to flag, info = for reference, gap = not covered here, error = not available yet) and a one-line answer; for the sections named, also the facts behind it, notes, and sources with licences. Sections: zoning, buildable, sun, alr, soil, flood, fire, evac, seismic, landslides, radon, fcsi, access, water, lake, minerals, habitat, nextdoor, noise, wells, septic, services, internet, climate, svt, tax, crime (the lake section only beside a sampled lake). Zoning rules are our dated summary of the bylaw. A lot nobody has looked up yet takes 10 to 20 seconds to build. No scores, valuations or owner names.

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": {
      "pid": "<pid>"
    },
    "name": "parcel_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
pidYesThe lot's 9-digit PID, with or without dashes (find_parcel gives it).
fullNoEvery section in full: about 100 KB, sent twice in the reply (as structured content and as text). Name sections instead to keep it small.
sectionsNoSections to give in full (facts, notes, sources); the others come as status and headline only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / full / description
      Previous value: -"Every section in full (about 40 KB)."New value: +"Every section in full: about 100 KB, sent twice in the reply (as structured content and as text). Name sections instead to keep it small."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the full status vocabulary (flag/clear/info/gap/error), a cost warning for uncached lots (10–20 seconds), the provenance caveat that zoning rules are a dated summary of the bylaw, and explicit exclusions (no scores, valuations, or owner names). That is unusually rich behavioral context for a read tool.

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?

Front-loaded with the core purpose, then status legend, then section list, then constraints; nearly every clause carries information. The 27-section enumeration is long but necessary, though the sentence structure is run-on and could be split for faster scanning.

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?

With no output schema, the description correctly supplies the status-code legend and output shape, plus latency and scope limits, which an agent needs to interpret results. It stops short of covering failure modes for an invalid or unknown PID, which would complete the picture for a 27-section report tool.

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 description adds meaning the schema does not: named sections yield facts, notes, and licensed sources while the rest return status plus a one-line answer, and the lake section is conditionally unavailable. Size implications of requesting everything are already in the schema, so no extra credit there.

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 ("One lot's report by PID") and then enumerates the exact sections returned, so an agent knows precisely what it gets. It is clearly distinguishable from find_parcel, which supplies the PID rather than the report.

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?

Usage is implied rather than stated: an agent learns that naming sections keeps the payload small and that the lake section only appears beside a sampled lake. There is no explicit when-to-use/when-not guidance or pointer to find_parcel as the prerequisite step (that only appears in the schema).

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