Skip to main content
Glama

BrokerIA Imoveis

by io.github.raklapimenta

Estimate purchasing capacity (educational, pre-search)

brokeria_capacidade_pre_search
Read-only

Estima um intervalo educacional de valor de imovel que poderia caber na renda mensal informada (criterio de comprometimento medio publico ~30%). NAO e uma cotacao, NAO e uma pre-aprovacao, NAO consulta seu historico de credito, NAO determina aprovacao. Opcionalmente conta quantos imoveis do catalogo BrokerIA cabem no intervalo na cidade informada. Use ANTES de buscar imoveis para ajudar o usuario a definir uma faixa de preco realista.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idadeYes
cidadeNoCidade de interesse (opcional). Se informada, conta quantos imoveis do catalogo cabem no intervalo.
dependentesNo
entrada_brlYesEntrada disponivel em reais
tipo_imovelNonovo
valor_fgts_brlNo
primeiro_imovelYes
renda_familiar_brlYesRenda familiar mensal em reais (max R$ 100 mil)
fgts_acima_36_mesesNo

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only and non-destructive; the description adds meaningful context: the estimate is educational only, does not check credit history, does not determine approval, and optionally counts catalog matches. This goes beyond the annotation hints without contradiction.

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?

Three sentences front-load the primary function, followed by clear limitations and usage guidance. Every sentence is informative and there is no redundant text.

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?

The description covers purpose, timing, limitations, and optional behavior, and the output shape is implied as an interval and a count. Without an output schema, a bit more detail on return format could help, but it is largely complete.

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 33%, and the description only indirectly references income and city, leaving parameters like idade, dependentes, tipo_imovel, FGTS values, and primeiro_imovel unexplained. It does not compensate for the low schema coverage.

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?

The description clearly states the tool estimates an educational property-value range based on monthly income, using a specific verb and resource. It distinguishes itself from siblings by explicitly stating it is not a quote or pre-approval and is intended for pre-search use.

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 explicitly directs use 'ANTES de buscar imoveis' and lists exclusions (not a quote, not pre-approval), but does not name alternative sibling tools. This provides clear when-to-use context with some exclusions, though not full alternative guidance.

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

All BrokerIA Imoveis toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool addresses a distinct step in the real estate journey: financial pre-qualification, property search, proximity search, detail viewing, comparison, visit scheduling, payment estimation, and neighborhood analytics. No two tools have overlapping responsibilities; even the two estimation tools focus on different questions (affordable price vs. monthly payment).

Naming Consistency3/5

Most tools follow a verb_noun pattern like buscar_imoveis and agendar_visita, but others are noun-based (detalhes_imovel, info_bairro) and one mixes English with Portuguese (capacidade_pre_search). The consistent 'brokeria' prefix mitigates this, but the varied structures and language mixing are noticeable.

Tool Count5/5

At 8 tools, the set is appropriately scoped for a real estate assistant, covering both discovery (search, nearby) and action (scheduling) without redundancy. Each tool has a clear role, and there is no excess or obvious bloat.

Completeness5/5

The tool set delivers a complete workflow: budgeting (capacidade_pre_search), searching (buscar_imoveis/imoveis_proximos), evaluating (detalhes_imovel/comparar_imoveis), contextualizing (info_bairro), and acting (agendar_visita). It also covers financing education with estimar_parcela_educacional. Missing features like listing purchases or broker contact are out of scope for a buyer-facing assistant.

Resources