Skip to main content
Glama

SENTINEL Washington Real Estate

Compare Washington seller proceeds

wa_compare_seller_scenarios
Read-only

Compare multiple proposed sale prices using explicit seller cost assumptions. Return itemized proceeds for each scenario and the difference between them. Prices are supplied scenarios, not valuations. The result includes an 'attributions' array (upstream source lines and the NWMLS/DOR/county non-affiliation line) and a professional-advice disclaimer — pass both through to end users.

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": {
      "county": "<county>",
      "scenarios": "<scenarios>"
    },
    "name": "wa_compare_seller_scenarios"
  }
}

Input Schema

NameRequiredDescriptionDefault
countyYes
scenariosYes

Output Schema

NameRequiredDescriptionDefault
countyYes
deltasYes
scenariosYes
disclaimerNoNot legal, tax, or financial advice. Verify with licensed professionals and source records.
assumptionsYes
attributionsYes
fully_comparableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds valuable behavioral detail beyond annotations: it returns an 'attributions' array and a professional-advice disclaimer, and instructs that both must be passed through to end users.

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

Conciseness4/5

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

Four sentences, front-loaded with the core purpose and return behavior. The disambiguation and compliance sentences each add useful information; no filler is present.

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?

Because an output schema exists, the description need not explain return values in detail, but it still highlights the attributions and disclaimer requirements. The main gap is parameter guidance for county and scenarios, though the schema itself supplies structure and nested field constraints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Top-level schema description coverage is 0%: neither 'county' nor 'scenarios' is explained in the description. The description vaguely references 'explicit seller cost assumptions' but does not clarify what county should contain or how scenario fields relate, leaving the reader to rely entirely on 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 uses a specific verb ('Compare') and resource ('multiple proposed sale prices' / seller scenarios), and says it returns itemized proceeds plus the difference between scenarios. It distinguishes itself from valuation tools by stating 'Prices are supplied scenarios, not valuations,' though it does not explicitly contrast with sibling tools like wa_net_sheet or wa_compare_offers.

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?

It gives a clear usage context: compare proposed sale prices under explicit seller cost assumptions. It adds a helpful exclusion ('not valuations'), but does not name alternative tools or say when another sibling would be more appropriate.

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.