Skip to main content
Glama

PolicyVera insurance quotes

Tell your lender about a new home

tell_lender_new_home
Destructive

The borrower's own way on PolicyVera to tell a lender about a home they are buying or refinancing, by its typed address: a home the person wants a loan on that is not on their account yet, for a lender the person already shares with (share_with_lender first). Without personConfirmed it answers what the lender will get. With personConfirmed: true, the person's yes, the lender's PolicyVera board shows a new deal for that address (or their open deal there with the person's intent) and their loan officer is notified on PolicyVera. Nothing is sent to anyone else.

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": {
      "lenderPartnerId": "<lenderPartnerId>",
      "address": "<address>"
    },
    "name": "tell_lender_new_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe new home, as the person typed it.
lenderPartnerIdYesFrom find_lender; sharing must already be granted.
personConfirmedNotrue only on the second call, after the person's explicit yes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, and the description adds real substance beyond them: the preview-vs-commit split, the fact that an existing open deal at that address is updated with the person's intent, that the loan officer is notified, and the scope limit 'Nothing is sent to anyone else.' It does not address reversibility or how to undo a confirmed submission, which matters for a destructive, non-idempotent write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and precondition are front-loaded, and no sentence is pure filler, but the content is delivered as one sprawling sentence with stacked parentheticals ('The borrower's own way on PolicyVera to tell a lender about a home..., by its typed address: a home the person wants a loan on that...'). The opening clause is convoluted and the preview/commit behavior could be split into separate, clearly ordered sentences.

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?

For a destructive write with a nested address object and no output schema, the description covers the prerequisite, both call modes, the downstream effects and the disclosure boundary. The main remaining gap is that the preview mode's response is only vaguely characterized ('answers what the lender will get'), with no mention of the shape of that answer or whether a confirmed deal can be withdrawn.

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: omitting personConfirmed is a preview of what the lender will get, while setting it to true performs the mutation and triggers notification. That reframes the parameter from a simple boolean into the commit switch for the operation.

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?

States a specific verb and resource (tell a lender about a home you are buying/refinancing), the concrete effect on the lender's PolicyVera board, and repeatedly ties it to the borrower's typed address. It also distinguishes the prerequisite tool by name (share_with_lender first), so an agent can tell it apart from the sharing step.

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?

Explicitly gives the precondition ('for a lender the person already shares with (share_with_lender first)') and the two-step invocation protocol: call without personConfirmed to preview what the lender will receive, then call with personConfirmed: true only after the person's explicit yes. The condition that selects each mode is spelled out rather than inferred.

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