Skip to main content
Glama

Faro · Imóveis de Alto Padrão

Falar com o André Prazeres

falar_com_andre
Read-only

Contato do corretor André Prazeres para visita, tabela, disponibilidade ou para anunciar um imóvel. Devolve o link de WhatsApp com a mensagem pronta (o usuário é quem envia).

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

Input Schema

NameRequiredDescriptionDefault
idiomaNo
assuntoNoO que a pessoa quer (ex.: 'visitar a casa 612885', 'tabela do Terrah').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the key mechanism: the tool returns a ready-made WhatsApp link and the USER performs the sending, not the tool. That is exactly the kind of behavioral detail annotations cannot convey. It does not mention whether the link expires or how the message is composed, but the essential semantics are covered.

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 sentences, zero filler, and the outcome (WhatsApp link) is stated up front before the clarification that the user sends it. Every clause carries information the agent could not get from structured fields.

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?

For a simple two-optional-parameter tool with no output schema, the definition supplies purpose, use cases, and the return mechanism. The only real gap is the unexplained 'idioma' parameter, which the description should have described in terms of message language.

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?

The listed use cases (visita, tabela, disponibilidade, anunciar imóvel) map well onto the 'assunto' parameter and reinforce its schema example. However, the 'idioma' parameter (enum pt/en) is never mentioned, leaving half the schema undocumented; with 50% coverage the description only partially compensates.

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 names a specific resource (contact with broker André Prazeres) and a concrete outcome ("Devolve o link de WhatsApp com a mensagem pronta"), which clearly separates it from siblings like buscar_imoveis or detalhes_imovel that deal with listings rather than contacting the broker. The opening noun "Contato" is slightly less crisp than a verb, but the second sentence supplies the actionable verb and result.

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 enumerates concrete triggers: visita, tabela, disponibilidade, or anunciar um imóvel, giving the agent a clear picture of when this tool is the right call. It stops short of stating when NOT to use it or naming a sibling alternative, but the enumerated use cases leave little ambiguity.

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