Skip to main content
Glama

Faro · Imóveis de Alto Padrão

Oportunidades farejadas

oportunidades_do_faro
Read-only

Lista os imóveis que o Faro farejou: valor por m² bem abaixo da mediana de imóveis parecidos do mesmo condomínio ou bairro, com a conta completa (R$/m² do imóvel, mediana, tamanho da amostra, confiança). Use para 'oportunidades abaixo do valor de mercado em Alphaville'.

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": "oportunidades_do_faro"
  }
}

Input Schema

NameRequiredDescriptionDefault
ondeNoCondomínio, bairro ou cidade (opcional).
tipoNo
limiteNo
confiancaNo
preco_maxNo

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 declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context with no output schema present: it discloses the returned evidence set (R$/m², median, sample size, confidence), which matters because small samples change how trustworthy a result is. It does not mention ordering, defaults, or what happens when there are too few comparables.

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?

Two compact sentences plus a quoted trigger example, with the defining criterion front-loaded before the output preview. Every clause carries information and nothing is padded.

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?

With no output schema, the description usefully previews what a result contains, which covers the biggest completeness risk. However, for a 5-parameter filtering tool with 0 required parameters, it leaves the filter parameters and their interactions unexplained, so an agent still has to guess how to narrow results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% – just 'onde' is documented. Four parameters (tipo, limite, confianca, preco_max) get no explanation in either place; 'confiança' appears only as a field in the returned math, not as a filter whose levels (alta/media/qualquer) are explained, and no default limit is stated despite the 1-20 cap.

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 and resource ('Lista os imóveis que o Faro farejou') plus the exact qualifying criterion: price per m² well below the median of comparable units in the same condominium or neighborhood. The criterion itself makes it distinguishable from a generic property search sibling, though no sibling is named outright.

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?

Gives an explicit trigger phrasing ('Use para "oportunidades abaixo do valor de mercado em Alphaville"'), which tells the agent the kind of query that selects this tool. It stops short of stating when NOT to use it or naming the alternative (e.g. buscar_imoveis) for plain listings.

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