Skip to main content
Glama

Ancorei: guia de marinas do Brasil

Buscar marinas

buscar_marinas
Read-onlyIdempotent

Busca marinas, iates clubes e garagens náuticas do litoral brasileiro por cidade, UF, serviço, texto livre, se aceitam barco visitante e se têm WhatsApp. Devolve nome, tipo, cidade/UF, telefone, link de WhatsApp e a página da marina na Ancorei.

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_marinas"
  }
}

Input Schema

NameRequiredDescriptionDefault
ufNoSigla do estado, ex.: SC, RJ, SP, BA
textoNoNome, bairro, rua ou palavra livre, ex.: iate clube, Itajaí
cidadeNoCidade, ex.: Florianópolis, Angra dos Reis, Búzios
limiteNoQuantos resultados (1 a 30, padrão 10)
servicoNoCombustível, restaurante, vestiários, segurança, rampa, guincho, Wi-Fi, energia, água, travel lift ou oficina
com_whatsappNotrue para só as que têm WhatsApp confirmado
aceita_visitanteNotrue para só as marinas que recebem barco visitante

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, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that by declaring the returned payload (nome, tipo, cidade/UF, telefone, link de WhatsApp, página na Ancorei) and the geographic coverage. It does not address empty-result behavior or result ordering.

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, both load-bearing: the first covers what is searched and by which dimensions, the second covers what comes back. No filler, and the core verb-resource pairing is front-loaded.

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?

With 7 optional parameters and no output schema, the description usefully compensates by describing the return fields and the geographic scope. What is missing is modest: behavior when no marina matches and how the limite cap interacts with total results.

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 description coverage is 100%, so every parameter is already documented with examples, making 3 the baseline. The description restates the filter dimensions at a summary level and clarifies that "serviço" and visitante/WhatsApp are true filtering axes, but adds no syntax or precedence rules 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 specific verb ("Busca") plus the resource set ("marinas, iates clubes e garagens náuticas") and constrains scope to "litoral brasileiro", then names the filterable dimensions. It does not explicitly distinguish itself from ficha_marina (single-marina detail) or listar_cidades, so it stops short of a 5.

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 implied by the enumeration of filters (cidade, UF, serviço, texto livre, visitante, WhatsApp), which tells an agent what queries are supported. However, there is no explicit when-to-use guidance and no statement about when to prefer ficha_marina or listar_cidades instead.

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