Metastate · Imóveis em Portugal

Property details / Ficha do imóvel

ver_imovel

Read-only

Full details of one Metastate property by reference (e.g. META-003) or slug: price, size, rooms, energy class, features, description, consultant and link. / Ficha completa de um imóvel pela referência ou slug. Example arguments: {"referencia":"META-003"}

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

Input Schema

Name	Required	Description	Default
`referencia`	Yes	Reference (META-…) or slug returned by pesquisar_imoveis

Output Schema

Name	Required	Description	Default
`url`	No
`titulo`	No
`operacao`	No
`preco_eur`	No
`referencia`	No
`preco_texto`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 28, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is fully covered. The description adds only that it returns a complete record for a single item; it says nothing about miss/not-found behavior or whether the reference must be exact. That is adequate given the annotations but not rich.

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?

Front-loaded with the purpose and the field list, with no filler. The bilingual duplication and inline example lengthen it, but both serve a genuine audience and usability need rather than padding.

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 an output schema present, the description needn't explain return structure, and the single required parameter is fully documented in both places. The only unaddressed case is a reference that matches nothing, which an agent would need to guess at.

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 coverage is 100% and the parameter already documents "Reference (META-…) or slug returned by pesquisar_imoveis". The description only repeats the accepted formats and adds a concrete example argument, which is marginal value over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Full details of one Metastate property") and enumerates the returned fields (price, size, rooms, energy class, features, description, consultant, link), which clearly separates it from the list-level sibling pesquisar_imoveis.

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 ties itself to pesquisar_imoveis as the source of the reference/slug, so an agent knows the natural call order. It never states an explicit exclusion or what to do if the lookup fails, so it stops short of the top band.

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

All Metastate · Imóveis em Portugal 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?