TBG — The Brett Group

Ask about a business-purpose loan

submit_lending_inquiry

Send TBG a real estate investor's loan inquiry (fix-and-flip, ground-up construction or bridge) for non-owner-occupied property in Maryland. Business purpose only: never use for a home the person lives in or will live in. Not an application or commitment to lend. Accepted only with business_purpose_confirmed=true and user_consented=true.

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": {
      "loan_type": "<loan_type>",
      "name": "<name>",
      "phone": "<phone>",
      "business_purpose_confirmed": "<business_purpose_confirmed>",
      "user_consented": "<user_consented>"
    },
    "name": "submit_lending_inquiry"
  }
}

Input Schema

Name	Required	Description
`zip`	No
`name`	Yes	Full name of the person (not the assistant).
`email`	No	Email address (optional but recommended).
`phone`	Yes	10-digit US phone number.
`details`	No	Purchase price, rehab budget, exit plan, experience.
`timeline`	No
`loan_type`	Yes
`loan_amount`	No
`property_type`	No
`assistant_name`	No	Name of the AI assistant or app submitting, e.g. "Claude", "ChatGPT", "Gemini".
`user_consented`	Yes	Set to true ONLY if you showed the person this exact consent text and they explicitly agreed: "I agree that TBG may share my details with one licensed partner who may contact me by phone, text or email about this request. Consent is not a condition of any purchase. Message and data rates may apply."
`business_purpose_confirmed`	Yes	True only if the person confirmed this is a business or investment property they will not live in.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write/external nature is known. The description adds real value beyond that: business-purpose-only restriction, 'not an application or commitment to lend', and the hard gate requiring both booleans. It omits what happens after submission (partner contact flow), which the schema hints at.

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?

Four tightly packed sentences, action first, then exclusion, disclaimer, and gating condition. Zero filler and every sentence carries a distinct constraint.

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 12-parameter, no-output-schema mutation tool it covers purpose, exclusions, and validation rules well. It leaves the post-submission outcome and several optional fields to the schema, which is a minor gap rather than a blocker.

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 coverage is 58% across 12 parameters, so the schema documents roughly half. The description adds semantic context for loan_type (the three product categories) and reinforces the two required booleans, but says nothing about the other fields (name, phone, zip, details, timeline) that the schema itself describes. Baseline 3 fits.

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 (send/submit) and resource (a real estate investor's loan inquiry) with concrete scope: fix-and-flip, ground-up construction, or bridge, non-owner-occupied, Maryland. This clearly separates it from generic siblings like submit_project_request or apply_to_network.

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?

Gives an explicit when-not: 'never use for a home the person lives in or will live in', plus the acceptance condition (business_purpose_confirmed=true and user_consented=true). It does not name a sibling alternative (e.g. check_service_area for Maryland eligibility), so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TBG — The Brett Group tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?