Skip to main content
Glama

Faro · Imóveis de Alto Padrão

Detalhes de um imóvel

detalhes_imovel
Read-only

Ficha de um imóvel pelo código da Coelho da Fonseca (ex.: 612885): local, área, suítes, vagas, preço pedido, a conta do Faro quando houver e os links.

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": {
      "codigo": "<codigo>"
    },
    "name": "detalhes_imovel"
  }
}

Input Schema

NameRequiredDescriptionDefault
codigoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 goes beyond that by enumerating the payload an agent will get back (local, área, suítes, vagas, preço pedido, conta do Faro, links), which matters because there is no output schema. It still does not say what happens when the code does not exist.

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?

A single sentence, front-loaded with the verb and the keying parameter, followed by the returned fields. Dense but every clause carries information; no filler.

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 one-parameter read-only lookup with no output schema, the description covers the input identity, an example value, and the shape of the result. Only the not-found behavior is unaddressed, a minor gap at this complexity.

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

Parameters4/5

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

Schema coverage is 0% and the schema only declares an untyped string 'codigo'. The description compensates by identifying it as the Coelho da Fonseca property code and giving a concrete example (612885), which is real semantic value 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?

Says exactly what it does: returns the ficha (record sheet) of a single property identified by the Coelho da Fonseca code. Specific verb+resource, so it is distinguishable from a search tool, but it does not explicitly name or contrast with buscar_imoveis.

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?

Usage is only implied: the reader infers this is a lookup-by-known-code tool and that a search tool would be used first to obtain that code. There is no explicit when-to-use, when-not, or prerequisite statement.

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