Clearwater Capital Group

Make the owner's review link

create_review_link

Read-only

Checks the answers the business owner gave you and returns the one link they open on clearwatercapitalgrp.com to review every answer, add their own identity details, consent and sign. Stores nothing and sends nothing. Get the owner's OK on their answers first. Never include a Social Security number, date of birth, or bank login.

Input Schema

Name	Required	Description
`dba`	No	Doing-business-as name, if different.
`ein`	No	The business's 9-digit Employer Identification Number (EIN). Never a Social Security number. Required unless the entity_type is "Sole Prop" and the business has no EIN.
`notes`	No	Anything underwriting should know: why now, a slow season, a big contract.
`timing`	No	Required. How soon the owner needs the funds: same_day (within 24 hours), this_week (2-5 days), one_two_weeks, thirty_days (30+ days).
`website`	No	Business website.
`industry`	No	Required. What the business does, in a few words (for example "Plumbing" or "Restaurant").
`entity_type`	No	Required. How the business is registered.
`owner_email`	No	Required. Owner's email address.
`owner_phone`	No	Required. Owner's 10-digit US mobile number.
`owner_title`	No	Required. Owner's title (for example Owner, CEO, Managing Member).
`business_zip`	No	Required. 5-digit ZIP code.
`primary_bank`	No	Required. Bank that holds the main business checking account.
`use_of_funds`	No	Required. What the money is for.
`business_city`	No	Required. Business city.
`business_state`	No	Required. 2-letter US state code.
`owner_home_zip`	No	Required. Owner's 5-digit home ZIP code.
`business_street`	No	Required. Business street address.
`funding_history`	No	Required. Anything that has ever happened with a business lender or cash advance. "none" for a clean history, otherwise any of the other options. In a review link, separate with commas.
`owner_home_city`	No	Required. Owner's home city.
`owner_last_name`	No	Required. Business owner's last name.
`amount_requested`	No	Required. Dollars the owner wants, as a whole number (for example 75000).
`owner_first_name`	No	Required. Business owner's first name.
`owner_home_state`	No	Required. 2-letter US state code of the owner's home.
`owner_home_street`	No	Required. Owner's home street address.
`ownership_percent`	No	Required. Percent of the business the owner holds, 1 to 100.
`merchant_processor`	No	Card processor, if the business takes cards (for example Square or Stripe).
`business_legal_name`	No	Required. Legal name of the business, as registered.
`monthly_card_volume`	No	Monthly credit card sales in dollars, if any.
`business_start_month`	No	Required. Month and year the business opened, as YYYY-MM.
`estimated_credit_score`	No	Required. Owner's best guess at their personal credit score, 300 to 850. A guess is fine.
`open_advances_or_loans`	No	Required. Every merchant cash advance or business loan the business pays today. "none" if none. Otherwise a list of { "lender", "balance", "payment", "frequency" } (frequency: daily, weekly, bi-weekly, monthly). In a review link, write each as "Lender, balance, payment, frequency" separated by semicolons.
`average_monthly_revenue`	No	Required. Average monthly deposits into the business bank account, in dollars.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that the tool stores nothing and sends nothing, explains that the link is for the owner to review and sign, and adds sensitive-data constraints. This is substantive behavioral context for a tool whose name says 'create'.

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 sentences, front-loaded with the action and result, followed by the no-storage guarantee and safety constraints. Every sentence contributes necessary information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 32-parameter tool with rich schema coverage and no output schema, the description covers the essential behavior: validation, output link, no storage or sending, owner review flow, and sensitive-data prohibitions. The remaining parameter detail is appropriately delegated to the schema.

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 100%, so the parameter schema already carries the detailed semantics and the baseline score is 3. The description adds a useful global constraint about never including SSNs, dates of birth, or bank logins, but does not add field-specific meaning beyond the schema.

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?

The description states a specific action (checks the owner's answers) and a concrete output (returns the one review link on clearwatercapitalgrp.com). It is clear what the tool does, but it does not explicitly distinguish this from the sibling get_funding_application.

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?

It gives a prerequisite (get the owner's OK first) and a sensitive-data exclusion, which provides some usage guidance. However, it does not state when to use this tool instead of get_funding_application, nor does it describe when not to use it.

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

All Clearwater Capital 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?