mcp-server-appraisal

appraise_asset

Generate structured multi-tier asset valuations to determine liquidation floor, dealer wholesale, retail fair market, and insurance replacement values for pricing and risk decisions.

Instructions

Generates a structured multi-tier appraisal report: liquidation floor, dealer wholesale, retail fair market value, and insurance replacement value.

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": {
      "name": "<name>"
    },
    "name": "appraise_asset"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Asset name or description to appraise
`baseline_cost_usd`	No	Optional baseline or acquisition cost

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the output structure (the four valuation tiers) but says nothing about whether this is a read-only computation, what inputs drive each tier, latency, or accuracy caveats. Partial behavioral disclosure, not full.

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?

A single sentence, front-loaded with the action and then the concrete output tiers. Every clause carries information and there is no filler.

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?

With no output schema, the description correctly compensates by naming the four return tiers, and the two input params are fully covered by the schema. The only real gap is the absence of any sibling differentiation against benchmark_market_comps.

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 both parameters (name, baseline_cost_usd) are already documented in the schema. The description adds no parameter-level meaning such as how baseline_cost_usd influences each tier, so the baseline 3 applies.

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 verb ("Generates") and resource ("structured multi-tier appraisal report") and enumerates the exact tiers produced (liquidation floor, dealer wholesale, retail FMV, insurance replacement). This is far more informative than a generic "appraises an asset," though it never contrasts itself with the sibling benchmark_market_comps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus benchmark_market_comps, nor any prerequisites or exclusions. The valuation framing implies usage but an agent choosing between the two siblings gets no routing signal.

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

Deploy Server