Skip to main content
Glama

get_etiquette_guide

Obtain business etiquette guidelines for LATAM countries covering meeting protocols, gift culture, food customs, and communication norms for effective cross-cultural interactions.

Instructions

Business etiquette: meeting protocols, gift culture, food culture, communication norms per LATAM country.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes

Implementation Reference

  • Handler for 'get_etiquette_guide' tool — looks up the country in ETIQUETTE_GUIDES and returns a JSON payload with business etiquette data (meeting protocols, gift culture, food culture, communication norms).
    case "get_etiquette_guide": { const d = ETIQUETTE_GUIDES[country]; if (!d) throw new Error(`Unknown: ${country}`); return { content: [{ type: "text", text: JSON.stringify({ module: "LATAM Business Etiquette", country, ...d }, null, 2) }] }; }
  • Input schema for 'get_etiquette_guide' tool — expects a single required 'country' parameter, validated against keys of ETIQUETTE_GUIDES object.
    { name: "get_etiquette_guide", description: "Business etiquette: meeting protocols, gift culture, food culture, communication norms per LATAM country.", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(ETIQUETTE_GUIDES) } }, required: ["country"] } },
  • src/main.ts:142-142 (registration)
    Registration of 'get_etiquette_guide' tool in the ListToolsResponse — provides the name, description, and input schema.
    { name: "get_etiquette_guide", description: "Business etiquette: meeting protocols, gift culture, food culture, communication norms per LATAM country.", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(ETIQUETTE_GUIDES) } }, required: ["country"] } },
  • ETIQUETTE_GUIDES data object — contains the raw business etiquette data for all 6 LATAM countries (Mexico, Brazil, Colombia, Argentina, Chile, Peru).
    const ETIQUETTE_GUIDES: Record<string, any> = {
      mexico: { meeting_protocol: "Handshake firm. Use of usted (formal you) until invited otherwise. Family chat first.", gift_culture: "Modest gifts when visiting offices. Wine, sweets work. Avoid alcohol if Catholic family.", food_culture: "Comida (1-3pm) is sacred. Long lunches build deals.", communication: "Indirect 'no'. Read between lines." },
      brazil: { meeting_protocol: "Warm handshake or hug. First names quickly. Personal questions normal.", gift_culture: "Modest. Wine, foreign chocolates. Avoid green-yellow combo (national colors, looks weird).", food_culture: "Cafezinho (espresso) meetings. Lunch 12-2pm sacred.", communication: "Expressive, lots of overlap in conversation." },
      colombia: { meeting_protocol: "Handshake + light kiss on cheek for women in social. Formal in business.", gift_culture: "Coffee, flowers acceptable. Avoid white roses (funeral).", communication: "Polite, indirect. Catch implicit cues." },
      argentina: { meeting_protocol: "One kiss on cheek (even men in some contexts). Informal vos.", gift_culture: "Wine, mate accessories appreciated.", food_culture: "Long lunches + dinners. Asado (BBQ) social weight.", communication: "Direct + intellectual. Long debates expected." },
      chile: { meeting_protocol: "Firm handshake. More formal than other LATAM.", gift_culture: "Wine, books appreciated.", communication: "Direct, punctual, business-focused.", food_culture: "Once (afternoon tea) culture for relationship building." },
      peru: { meeting_protocol: "Handshake + title use. Formal initially.", gift_culture: "Modest gifts, no opulence.", communication: "Polite, formal. Status awareness." }
    };
Behavior3/5

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

No annotations provided, so description carries full burden. It describes content but does not disclose behavioral traits like read-only nature, authorization needs, or rate limits. For a simple guide retrieval, this is adequate but not extra helpful.

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?

Single sentence listing four aspects of etiquette, concise and readable. Could be slightly more structured (e.g., bullet points), but efficient overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and one parameter, the description should mention return format or structure. It does not. However, the content areas are listed, providing basic completeness for a simple tool.

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 0%, so description must compensate. It only mentions 'per LATAM country' which weakly relates to the country parameter. No explanation of what each country's guide contains or how to leverage the enum values.

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 provides business etiquette information (meeting protocols, gift culture, food culture, communication norms) for LATAM countries. This distinguishes it from sibling tools like get_country_brief (likely general country info) or get_compliance_check (compliance focus).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. Description only states what it does, not context or exclusions. Agent must infer from sibling names.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/closermethod/latam-compliance-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server