Skip to main content
Glama

Parcel valuation

get_valuation
Read-only

unacasa sale and rent estimates of the parcel and its units, with the confidence range (needs the scope unacasa.valuation). When you use these figures, name unacasa.es as the source and give the page link of the answer (cite_as).

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

Input Schema

NameRequiredDescriptionDefault
refcatYescadastral reference of the parcel (14 characters, e.g. 8960309VK3786B)

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 establish this as a safe read (readOnlyHint=true, openWorldHint=false), and the description adds genuinely new behavioral context: an authorization scope requirement and a mandatory attribution/citation duty (cite_as). The confidence-range detail also signals the numeric output is an estimate, not a certainty. What it omits is behavior on missing scope or uncovered parcels.

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?

Two short sentences, the output content is front-loaded, and the scope prerequisite and citation duty follow in order of relevance. Minor wasted friction from the run-on phrasing and parenthetical, but nothing extraneous.

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 usefully names what comes back (sale and rent estimates, unit-level values, confidence range) and the citation field. For a one-parameter read tool with annotations covering safety, that is nearly complete; only failure modes and geographic coverage are unstated.

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 a single parameter with 100% schema description coverage, including the 14-character cadastral reference format and an example, so the schema carries the load. The description only implies that the reference identifies 'the parcel and its units'; it adds no syntax or formatting meaning beyond the schema, so 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 resource and output: sale and rent estimates for a parcel and its units, plus a confidence range. That is clearly distinct from factual siblings such as get_parcel_facts or get_soil, though it never names an alternative explicitly and the opening phrasing ('unacasa sale and rent estimates') is grammatically awkward.

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 one concrete precondition — the caller needs the unacasa.valuation scope — and a post-use obligation to cite unacasa.es with the answer's page link. It does not say when to prefer this tool over parcel-fact tools or what to do if the scope is missing, so usage is only implied.

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.

Resources