mcp-server-appraisal

benchmark_market_comps

Returns market comparability ratios and liquidity velocity grades by asset category for pricing decisions.

Instructions

Returns market comparability ratios and liquidity velocity grades for pricing decisions.

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

Input Schema

Name	Required	Description	Default
`category`	Yes	Asset category (e.g. domains, digital_real_estate, ip)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Returns' weakly implies a read-only lookup, but nothing is said about side effects, required permissions, caching or freshness of benchmark data, or how the grades should be interpreted for pricing.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though the terms 'comparability ratios' and 'liquidity velocity grades' are undefined jargon that the reader must infer.

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

Completeness3/5

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

For a one-parameter, read-only-style tool with no output schema and no annotations, the description is minimally adequate: it names the return artifacts but not their format, scale, or degree of confidence. It also omits any routing versus the sibling appraise_asset tool.

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?

There is only one parameter and schema description coverage is 100%, with the schema already documenting 'category' and offering examples like domains, digital_real_estate, and ip. The description adds no further meaning about the category parameter, 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 names a concrete verb ('Returns') and a concrete resource ('market comparability ratios and liquidity velocity grades'), so an agent knows it produces benchmark figures rather than a valuation. It does not, however, differentiate itself from the sibling appraise_asset, which could plausibly be mistaken for the same operation.

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?

The only usage signal is the trailing phrase 'for pricing decisions', which states a domain rather than a condition for choosing this tool. There is no guidance on when to prefer this over appraise_asset, no prerequisites, and no exclusions.

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

Deploy Server