Skip to main content
Glama

Faro · Imóveis de Alto Padrão

Buscar imóveis de alto padrão

buscar_imoveis
Read-only

Busca imóveis à venda (anúncios ativos da Coelho da Fonseca) no portfólio de André Prazeres, associado à Coelho da Fonseca: casas em condomínio em Alphaville e Tamboré, apartamentos e casas em São Paulo, praia, campo, lançamentos e exterior. Use para perguntas como 'casa em Alphaville com 4 suítes até R$ 5 milhões'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buscar_imoveis"
  }
}

Input Schema

NameRequiredDescriptionDefault
ondeNoCondomínio, bairro, cidade ou região (ex.: 'Alphaville 1', 'Tamboré', 'Morumbi', 'Guarujá', 'Miami', 'praia', 'campo').
tipoNo
ordemNo
limiteNoQuantidade (padrão 8).
area_minNoÁrea mínima em m².
preco_maxNoPreço máximo na moeda do anúncio (R$ no Brasil).
preco_minNoPreço mínimo na moeda do anúncio (R$ no Brasil; padrão R$ 1 milhão).
suites_minNo
so_oportunidadesNoSó os farejados (valor por m² abaixo dos parecidos).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 usefully adds that only active listings from a specific brokerage portfolio are searched. It does not disclose the result ordering/limit behavior or defaults (e.g., default limit of 8, default preço mínimo of R$ 1 milhão), leaving meaningful operational traits unstated.

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 sentences, front-loaded with what the tool does and followed by the trigger example. The long enumeration of property types is somewhat listy but still earns its place by defining coverage.

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 9-parameter, all-optional search tool with no output schema and no annotation coverage of results, the description gives good domain scope but omits defaults, result shape, and how it differs from the launches and bargain sibling tools.

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 67%, so a baseline of 3 applies. The description does add a worked example mapping natural-language constraints to onde/tipo/suites_min/preco_max, which is genuine value, but it says nothing about ordem, area_min, limite, or so_oportunidades beyond 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?

States a concrete verb+resource ("Busca imóveis à venda") plus scope: active listings from the Coelho da Fonseca portfolio managed by André Prazeres, with the property types covered. It is clear what the tool returns, but it does not distinguish itself from overlapping siblings such as lancamentos_alphaville or oportunidades_do_faro, even while claiming to cover 'lançamentos'.

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?

Provides a trigger example ("Use para perguntas como 'casa em Alphaville com 4 suítes até R$ 5 milhões'"), which implies when to reach for it. However, there is no when-not guidance and no routing to the apparent alternatives for launches or bargain listings, so the agent must infer the boundary.

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