Skip to main content
Glama

Ancorei: guia de marinas do Brasil

Ficha de uma marina

ficha_marina
Read-onlyIdempotent

Todos os dados públicos de uma marina a partir do id devolvido por buscar_marinas: endereço, coordenadas, serviços, canal VHF, telefone, WhatsApp, site, Instagram, página na Ancorei e como reservar.

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": {
      "id": "<id>"
    },
    "name": "ficha_marina"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid da marina (slug), ex.: marina-laguna-marechal-deodoro

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds the useful 'dados públicos' qualifier and a field inventory, but says nothing about error behavior for an invalid id or about response shape/pagination.

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?

One front-loaded sentence: scope first, then provenance of the id, then the field inventory. Zero filler and nothing redundant for a simple lookup tool.

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 no output schema, the explicit field list (address, coordinates, services, VHF, contacts, socials, booking) is exactly what the agent needs to judge relevance. Missing only edge-case guidance, such as what happens for an unknown or ambiguous slug.

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 coverage is 100% and the single id parameter is already documented with a slug example in the schema. The description adds provenance (the id comes from buscar_marinas), which is genuinely useful, but no format or normalization guidance beyond the schema.

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?

States a specific verb (retrieve all public data) and resource (a marina) with explicit scope: 'Todos os dados públicos de uma marina a partir do id'. It also enumerates the returned fields, so an agent knows exactly what it gets without opening anything else.

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?

Explicitly ties the required input to its source — 'a partir do id devolvido por buscar_marinas' — telling the agent to call the search tool first. It lacks an explicit exclusion or fallback for what to do when an id is unknown, so it stops short of a 5.

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