Skip to main content
Glama

Check A Consented Property

fairpath_check_property

Look up a homeowner-provided address and return bounded property context. This requires explicit address consent, creates a private audit record, and may create or reuse short-lived scoped session and consent records. It does not expose owner, payment, or raw county records or change an external system.

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>",
      "addressConsentGranted": "<addressConsentGranted>",
      "consentedAt": "<consentedAt>",
      "consentEvidenceId": "<consentEvidenceId>"
    },
    "name": "fairpath_check_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe homeowner-provided property address to check.
contextNo
consentedAtYesWhen the homeowner explicitly approved this address lookup.
consentEvidenceIdYesOpaque, non-PII id for the client-side consent event. FairPath stores only its hash.
addressConsentGrantedYesMust be true only after the homeowner explicitly consents to address lookup.

Output Schema

NameRequiredDescriptionDefault
dataYes
redactionYes
sourcesUsedYes
directAnswerYes
evidenceGapsYes
countyCaveatsYes
confidenceLevelYes
complianceFooterYes
informationPostureNoTransitional compatibility field: current broker responses include it, while older broker deployments may omit it during the coordinated rollout.
countyKnowledgeDensityNo
nextAvailableFairPathActionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations flag readOnlyHint=false and destructiveHint=false but don't explain why a lookup writes; the description fills that gap by disclosing that it creates a private audit record and may create or reuse short-lived scoped session and consent records. The statement that it does not change an external system corroborates openWorldHint=false. It stops short of describing failure modes when consent evidence is rejected.

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?

Two sentences, with the positive purpose front-loaded and the write side effects and exclusions following in the same breath. No filler and nothing that restates the title or annotations verbatim.

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 annotations, a rich input schema and an output schema present, the definition covers the consent contract, the write side effects, and what data is withheld. The remaining gap is behavioral edge cases, such as what the tool returns or raises when consent evidence is invalid or the address cannot be resolved.

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?

Schema description coverage is 80%, so field-level documentation is already doing the heavy lifting for address, consentedAt, consentEvidenceId, and addressConsentGranted. The description adds no meaning beyond that for any parameter and says nothing about the nested context object (source, sessionId, countyHint), which is entirely undocumented by both surfaces.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Look up a homeowner-provided address and return bounded property context" gives a specific verb (look up) and resource (consented property address) plus an explicit scope bound ("bounded property context"). It is clear on its own, but never positions itself against the two sibling tools, so the agent must infer the split from names alone.

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 establishes a hard precondition ("requires explicit address consent") and a negative boundary (does not expose owner, payment, or raw county records), which tells the agent when this tool is and isn't appropriate. It offers no explicit routing to fairpath_explain_evidence_packet or fairpath_get_county_requirements, so usage guidance is implied rather than 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