MICHELLE SANCHEZ · FUNCTION REGISTRY

Every function.
A clear purpose.

Business objectives, data sources, API capabilities and permissions—connected to a testable result.

These are application API functions. The copied site uses a deterministic local text guide; no LLM or voice service is connected to this registry.

4API functions available
4Need a property feed
1Delivery function off
3Proposed, not active

START WITH THE OUTCOME

What each function
is here to do.

01

Help visitors understand life here

Make it easier to explore the six featured communities using sourced local information.

Community guide and story navigation can be tested; no lead or ranking result is promised.
02

Make home information dependable

Show or compare property facts only when an authorized feed can verify them.

Every displayed property must come from an approved feed. Unavailable results remain unavailable.
03

Make the next conversation easy

Help a visitor prepare a clear inquiry for Michelle while keeping the visitor in control of sending it.

A correct contact draft is the deliverable. Draft creation is not email delivery.
04

Provide useful local content consistently

Publish source-backed Journal content and polished newsletter previews the agent can share.

Published content, sources and working links can be verified. Scheduled sends remain off.
05

Keep capabilities and approvals visible

Give every function a purpose, contract, source, permission boundary and evidence record.

Registry completeness, contract tests and dated verification evidence. No implied model connection.

THE CURRENT FUNCTION CATALOG

Available. Waiting.
Or deliberately off.

Checked against contract version 1.0.0. Evidence: Oct 27, 2026, 10:22 AM Central. A successful unavailable response does not mean live listings are connected.

get_experience_context

Understand where the visitor is

API available

Return the navigation context supplied with a request.

Business objective
Keep capabilities and approvals visible
Example question
“Which community am I looking at?”
Expected result
An ok response containing parsed context. No database read or write.
Permission & approval
Read / navigation scope. Read public or visitor-provided navigation information. No storage or outbound communication.
Verification evidence
Verified response: ok. Current contract fingerprint matches.
Data, API contract & full checklist

Data fields

ExperienceContext.chapter · ExperienceContext.community · ExperienceContext.selectedProperty · ExperienceContext.filters

Data sources

  • Current browser context · ExperienceContext
    Untrusted navigation state; never a source of verified property facts.

API capability

POST /api/live/tools · Request envelope: name, args, optional context.

Input parameters

{
  "type": "object",
  "properties": {},
  "required": [],
  "additionalProperties": false
}
  • Context is supplied outside args and is parsed separately.
  • Browser context does not establish listing facts or identity.

Output envelope & expected result

{
  "type": "object",
  "required": [
    "status"
  ],
  "properties": {
    "status": {
      "type": "string"
    }
  },
  "additionalProperties": true
}

An ok response containing parsed context. No database read or write.

Approval basis

Existing website read/navigation scope.

Checklist coverage

Function nameDocumented

Business objectiveDocumented

Sample user questionDocumented

Data sourceDocumented

API capabilitiesDocumented

Input parametersDocumented

Expected outputDocumented

PermissionsDocumented

Verification evidenceVerified for this contract

Approval statusDocumented

search_properties

Find homes using verified data

Needs property feed

Search an approved property feed using bounded location, price and bedroom filters.

Business objective
Make home information dependable
Example question
“Find homes in Grapevine under $800,000 with at least three bedrooms.”
Expected result
Verified public property records with retrieval and feed timestamps, or an explicit unavailable response with no invented records.
Permission & approval
Provider approval needed. Read only provider-approved public property fields; no confidential remarks or restricted addresses.
Verification evidence
Verified response: unavailable. Current contract fingerprint matches.
Data, API contract & full checklist

Data fields

SearchFilters.city · SearchFilters.minPrice · SearchFilters.maxPrice · SearchFilters.beds · SearchFilters.offset · Property[]

Data sources

  • Authorized property feed · Property / SearchFilters
    Not connected in this copied app. Provider display permissions and freshness must be respected.

API capability

POST /api/live/tools · Request envelope: name, args, optional context.

Input parameters

{
  "type": "object",
  "properties": {
    "city": {
      "type": "string",
      "maxLength": 80
    },
    "minPrice": {
      "anyOf": [
        {
          "type": "integer",
          "minimum": 0,
          "maximum": 100000000
        },
        {
          "type": "string",
          "pattern": "^[0-9]+$"
        }
      ],
      "description": "An integer from 0 through 100000000; numeric strings are accepted and range-checked by the existing parser."
    },
    "maxPrice": {
      "anyOf": [
        {
          "type": "integer",
          "minimum": 0,
          "maximum": 100000000
        },
        {
          "type": "string",
          "pattern": "^[0-9]+$"
        }
      ],
      "description": "An integer from 0 through 100000000; numeric strings are accepted and range-checked by the existing parser."
    },
    "beds": {
      "anyOf": [
        {
          "type": "integer",
          "minimum": 0,
          "maximum": 20
        },
        {
          "type": "string",
          "pattern": "^[0-9]+$"
        }
      ],
      "description": "An integer from 0 through 20; numeric strings are accepted and range-checked by the existing parser."
    },
    "offset": {
      "anyOf": [
        {
          "type": "integer",
          "minimum": 0,
          "maximum": 1000
        },
        {
          "type": "string",
          "pattern": "^[0-9]+$"
        }
      ],
      "description": "An integer from 0 through 1000; numeric strings are accepted and range-checked by the existing parser."
    }
  },
  "required": [],
  "additionalProperties": false
}
  • Minimum price must not exceed maximum price.
  • Active listings only; at most 12 records per page.
  • Unknown filters and out-of-range values are rejected.

Output envelope & expected result

{
  "type": "object",
  "required": [
    "status"
  ],
  "properties": {
    "status": {
      "type": "string"
    }
  },
  "additionalProperties": true
}

Verified public property records with retrieval and feed timestamps, or an explicit unavailable response with no invented records.

Approval basis

Registry documentation does not grant provider access or approve a feed.

Checklist coverage

Function nameDocumented

Business objectiveDocumented

Sample user questionDocumented

Data sourceDocumented

API capabilitiesDocumented

Input parametersDocumented

Expected outputDocumented

PermissionsDocumented

Verification evidenceVerified for this contract

Approval statusDocumented

get_property_details

Read one verified home

Needs property feed

Retrieve one authorized listing by its provider ID.

Business objective
Make home information dependable
Example question
“What are the verified details of this home?”
Expected result
One verified public listing or an explicit unavailable/not-found result.
Permission & approval
Provider approval needed. Read only provider-approved public property fields; no confidential remarks or restricted addresses.
Verification evidence
Verified response: unavailable. Current contract fingerprint matches.
Data, API contract & full checklist

Data fields

Property.id · Property.price · Property.address · Property.status · Property.retrievedAt

Data sources

  • Authorized property feed · Property / SearchFilters
    Not connected in this copied app. Provider display permissions and freshness must be respected.
  • Current browser context · ExperienceContext
    Untrusted navigation state; never a source of verified property facts.

API capability

POST /api/live/tools · Request envelope: name, args, optional context.

Input parameters

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "pattern": "^[0-9]{1,20}$"
    }
  },
  "required": [],
  "additionalProperties": false
}
  • Supply id in args or selectedProperty in context.
  • ID must contain 1–20 digits.
  • Restricted and missing fields remain hidden or unknown.

Output envelope & expected result

{
  "type": "object",
  "required": [
    "status"
  ],
  "properties": {
    "status": {
      "type": "string"
    }
  },
  "additionalProperties": true
}

One verified public listing or an explicit unavailable/not-found result.

Approval basis

Registry documentation does not grant provider access or approve a feed.

Checklist coverage

Function nameDocumented

Business objectiveDocumented

Sample user questionDocumented

Data sourceDocumented

API capabilitiesDocumented

Input parametersDocumented

Expected outputDocumented

PermissionsDocumented

Verification evidenceVerified for this contract

Approval statusDocumented

get_area_context

Explain a featured community

API available

Return a curated community description and its public guide link.

Business objective
Help visitors understand life here
Example question
“Tell me about Grapevine.”
Expected result
An ok response with the community ID, name, description and source URL.
Permission & approval
Read / navigation scope. Read public or visitor-provided navigation information. No storage or outbound communication.
Verification evidence
Verified response: ok. Current contract fingerprint matches.
Data, API contract & full checklist

Data fields

communities[].id · communities[].name · communities[].description · communities[].source

Data sources

  • Featured community catalog · communities[]
    Curated descriptions with links to Michelle’s existing local guides.
  • Current browser context · ExperienceContext
    Untrusted navigation state; never a source of verified property facts.

API capability

POST /api/live/tools · Request envelope: name, args, optional context.

Input parameters

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "enum": [
        "flower-mound",
        "lantana",
        "argyle",
        "highland-village",
        "grapevine",
        "northlake"
      ]
    }
  },
  "required": [],
  "additionalProperties": false
}
  • Supply a featured community ID in args or context.
  • No school ratings, property-specific taxes or commute guarantees are inferred.

Output envelope & expected result

{
  "type": "object",
  "required": [
    "status"
  ],
  "properties": {
    "status": {
      "type": "string"
    }
  },
  "additionalProperties": true
}

An ok response with the community ID, name, description and source URL.

Approval basis

Existing website read/navigation scope.

Checklist coverage

Function nameDocumented

Business objectiveDocumented

Sample user questionDocumented

Data sourceDocumented

API capabilitiesDocumented

Input parametersDocumented

Expected outputDocumented

PermissionsDocumented

Verification evidenceVerified for this contract

Approval statusDocumented

present_properties

Prepare verified homes for display

Needs property feed

Return provider-verified records for a small set of listing IDs and a display action.

Business objective
Make home information dependable
Example question
“Show me these homes.”
Expected result
Verified records and a present_properties action, or unavailable with an empty property list.
Permission & approval
Provider approval needed. Read only provider-approved public property fields; no confidential remarks or restricted addresses.
Verification evidence
Verified response: unavailable. Current contract fingerprint matches.
Data, API contract & full checklist

Data fields

Property.id · Property[]

Data sources

  • Authorized property feed · Property / SearchFilters
    Not connected in this copied app. Provider display permissions and freshness must be respected.

API capability

POST /api/live/tools · Request envelope: name, args, optional context.

Input parameters

{
  "type": "object",
  "properties": {
    "ids": {
      "type": "array",
      "minItems": 1,
      "maxItems": 4,
      "items": {
        "type": "string",
        "pattern": "^[0-9]{1,20}$"
      }
    }
  },
  "required": [
    "ids"
  ],
  "additionalProperties": false
}
  • Provide one to four listing IDs; duplicates are removed.
  • Every record must be available before a display result is returned.

Output envelope & expected result

{
  "type": "object",
  "required": [
    "status"
  ],
  "properties": {
    "status": {
      "type": "string"
    }
  },
  "additionalProperties": true
}

Verified records and a present_properties action, or unavailable with an empty property list.

Approval basis

Registry documentation does not grant provider access or approve a feed.

Checklist coverage

Function nameDocumented

Business objectiveDocumented

Sample user questionDocumented

Data sourceDocumented

API capabilitiesDocumented

Input parametersDocumented

Expected outputDocumented

PermissionsDocumented

Verification evidenceVerified for this contract

Approval statusDocumented

compare_properties

Compare verified property records

Needs property feed

Return authorized records suitable for a factual comparison.

Business objective
Make home information dependable
Example question
“Compare these two homes by price and bedrooms.”
Expected result
Verified records or an unavailable result. No invented ranking, recommendation or unverified comparison.
Permission & approval
Provider approval needed. Read only provider-approved public property fields; no confidential remarks or restricted addresses.
Verification evidence
Verified response: unavailable. Current contract fingerprint matches.
Data, API contract & full checklist

Data fields

Property[] · Property.price · Property.bedrooms · Property.bathrooms · Property.area · Property.status

Data sources

  • Authorized property feed · Property / SearchFilters
    Not connected in this copied app. Provider display permissions and freshness must be respected.

API capability

POST /api/live/tools · Request envelope: name, args, optional context.

Input parameters

{
  "type": "object",
  "properties": {
    "ids": {
      "type": "array",
      "minItems": 1,
      "maxItems": 4,
      "items": {
        "type": "string",
        "pattern": "^[0-9]{1,20}$"
      }
    }
  },
  "required": [
    "ids"
  ],
  "additionalProperties": false
}
  • The current API accepts one to four IDs; a useful comparison needs at least two distinct verified records.
  • If any requested home cannot be verified, no comparison is supplied.

Output envelope & expected result

{
  "type": "object",
  "required": [
    "status"
  ],
  "properties": {
    "status": {
      "type": "string"
    }
  },
  "additionalProperties": true
}

Verified records or an unavailable result. No invented ranking, recommendation or unverified comparison.

Approval basis

Registry documentation does not grant provider access or approve a feed.

Checklist coverage

Function nameDocumented

Business objectiveDocumented

Sample user questionDocumented

Data sourceDocumented

API capabilitiesDocumented

Input parametersDocumented

Expected outputDocumented

PermissionsDocumented

Verification evidenceVerified for this contract

Approval statusDocumented

prepare_inquiry

Prepare a message for Michelle

API available

Create a mailto draft for the visitor to review in their own email application.

Business objective
Make the next conversation easy
Example question
“Help me ask Michelle about a move to North Texas.”
Expected result
A draft response with subject, body and Michelle’s mailto URL; a listing-specific draft remains unavailable until the home is verified.
Permission & approval
Visitor reviews the draft. Temporary message preparation only. The visitor reviews and chooses whether to send in their email app.
Verification evidence
Verified response: draft. Current contract fingerprint matches.
Data, API contract & full checklist

Data fields

business.email · Property.id · visitor-supplied message

Data sources

  • Michelle’s published contact details · business.phone / business.email
    Published business contact data in the site dictionary.
  • Current browser context · ExperienceContext
    Untrusted navigation state; never a source of verified property facts.
  • Authorized property feed · Property / SearchFilters
    Not connected in this copied app. Provider display permissions and freshness must be respected.

API capability

POST /api/live/tools · Request envelope: name, args, optional context.

Input parameters

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "pattern": "^[0-9]{1,20}$"
    },
    "message": {
      "type": "string",
      "maxLength": 1500
    }
  },
  "required": [],
  "additionalProperties": false
}
  • Without a listing ID, a general inquiry draft can be prepared.
  • If a listing is referenced, it must first be verified through the approved feed.
  • Draft text is not sent or saved by this app.

Output envelope & expected result

{
  "type": "object",
  "required": [
    "status"
  ],
  "properties": {
    "status": {
      "type": "string"
    }
  },
  "additionalProperties": true
}

A draft response with subject, body and Michelle’s mailto URL; a listing-specific draft remains unavailable until the home is verified.

Approval basis

The existing contact flow requires visitor review; draft creation is not approval to send.

Checklist coverage

Function nameDocumented

Business objectiveDocumented

Sample user questionDocumented

Data sourceDocumented

API capabilitiesDocumented

Input parametersDocumented

Expected outputDocumented

PermissionsDocumented

Verification evidenceVerified for this contract

Approval statusDocumented

submit_inquiry

Automatic inquiry delivery

Disabled

Document the disabled delivery boundary and refuse automatic submission.

Business objective
Make the next conversation easy
Example question
“Send this inquiry for me.”
Expected result
A disabled response stating that no message was sent.
Permission & approval
Disabled by owner. No external write permitted.
Verification evidence
Verified response: disabled. Current contract fingerprint matches.
Data, API contract & full checklist

Data fields

emailPolicy.sendingEnabled · emailPolicy.scheduledSendsEnabled

Data sources

  • Owner email-off instruction · emailPolicy
    Explicit instruction to stop outgoing scheduled sends; this app has no delivery provider.

API capability

POST /api/live/tools · Request envelope: name, args, optional context.

Input parameters

{
  "type": "object",
  "properties": {},
  "required": [],
  "additionalProperties": false
}
  • No automatic delivery, database write, recipient enrollment or schedule is created.
  • A new registry entry cannot enable this function.

Output envelope & expected result

{
  "type": "object",
  "required": [
    "status"
  ],
  "properties": {
    "status": {
      "type": "string"
    }
  },
  "additionalProperties": true
}

A disabled response stating that no message was sent.

Approval basis

Owner requested email sending and scheduled sends be stopped. This remains enforced in code.

Checklist coverage

Function nameDocumented

Business objectiveDocumented

Sample user questionDocumented

Data sourceDocumented

API capabilitiesDocumented

Input parametersDocumented

Expected outputDocumented

PermissionsDocumented

Verification evidenceVerified for this contract

Approval statusDocumented

This registry is read-only documentation. It does not approve a provider connection, connect a model, send a message or restart any schedule.