Skip to main content
Glama

get_followup_cadence

Retrieve country-specific follow-up cadences for APAC markets, with tailored gap patterns for Japan, Singapore, India, and others.

Instructions

Country-specific follow-up cadence (Japan slow + 14d gaps, Singapore fast + 2d gaps, India persistent + 5-10 touches).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes

Implementation Reference

  • The handler for the 'get_followup_cadence' tool: looks up the country in FOLLOWUP_CADENCES and returns the follow-up cadence data as JSON.
    case "get_followup_cadence": { const d = FOLLOWUP_CADENCES[country]; if (!d) throw new Error(`Unknown: ${country}`); return { content: [{ type: "text", text: JSON.stringify({ module: "APAC Follow-Up Cadence", country, ...d }, null, 2) }] }; }
  • Input schema for get_followup_cadence: requires a 'country' parameter with enum values from FOLLOWUP_CADENCES keys.
    { name: "get_followup_cadence", description: "Country-specific follow-up cadence (Japan slow + 14d gaps, Singapore fast + 2d gaps, India persistent + 5-10 touches).", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(FOLLOWUP_CADENCES) } }, required: ["country"] } },
  • The FOLLOWUP_CADENCES data dictionary containing per-country follow-up cadence rules (pacing, rules) for 8 APAC countries.
    const FOLLOWUP_CADENCES: Record<string, any> = {
      japan: { pacing: "Slow, formal. 7-14 day gaps. Multiple touches expected.", rules: ["Never push","Each follow-up should add value or ask permission","Long-term relationship orientation"] },
      singapore: { pacing: "Fast, 2-3 day gaps. Direct questions.", rules: ["Yes/no questions get answered","Respect time","Maximum 3-4 touches before backing off"] },
      korea: { pacing: "Patient but persistent. 5-7 day gaps. Multi-stakeholder.", rules: ["Always go through proper channels","Don't skip hierarchy","Use jeong (relational warmth)"] },
      india: { pacing: "Multiple touches (5-10) expected. 4-7 day gaps. WhatsApp follow-ups acceptable.", rules: ["Persistence is normal — not annoying","Pricing flexibility communicated","Mobile-first"] },
      australia: { pacing: "2-4 touches over 3 weeks. 5-7 day gaps. Casual.", rules: ["No corporate fluff","Respect work-life balance","Self-deprecation in follow-ups OK"] },
      hongkong: { pacing: "Fast, 2-4 day gaps.", rules: ["Numbers and references in every follow-up","Time-respect crucial","Speed signals seriousness"] },
      taiwan: { pacing: "Friendly-paced, 4-7 day gaps. LINE follow-ups acceptable.", rules: ["Maintain warmth","Reference shared meals or context","Don't pressure"] },
      indonesia: { pacing: "Slow, 7-10 day gaps. Multiple meetings expected.", rules: ["Patience over months","Build trust over deals","Religious awareness in timing"] }
    };
  • src/main.ts:171-181 (registration)
    Tool registration via ListToolsRequestSchema handler; get_followup_cadence is one of 7 tools listed.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        { name: "get_country_brief", description: "Country-specific APAC buyer psychology, communication style, what works/kills, sales cycle, compliance, optimal times, seasonal warnings.", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(COUNTRY_BRIEFS) } }, required: ["country"] } },
        { name: "get_outreach_template", description: "Country-specific outreach templates calibrated to local norms (Japanese formality, Aussie casualness, Indonesian Bapak/Ibu, etc.).", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(OUTREACH_TEMPLATES) }, channel: { type: "string", enum: ["cold_email"] } }, required: ["country", "channel"] } },
        { name: "get_followup_cadence", description: "Country-specific follow-up cadence (Japan slow + 14d gaps, Singapore fast + 2d gaps, India persistent + 5-10 touches).", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(FOLLOWUP_CADENCES) } }, required: ["country"] } },
        { name: "get_etiquette_guide", description: "Business etiquette per country: meishi protocol, gift culture, drinking culture, hierarchy norms, religious awareness.", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(ETIQUETTE_GUIDES) } }, required: ["country"] } },
        { name: "get_stakeholder_map", description: "Stakeholder navigation map by company stage. APAC-specific notes (chaebol, nemawashi, family-business dynamics).", inputSchema: { type: "object", properties: { company_stage: { type: "string", enum: Object.keys(STAKEHOLDER_MAP) } }, required: ["company_stage"] } },
        { name: "get_compliance_check", description: "Country-specific compliance: data protection framework, regulator, risks, spam law.", inputSchema: { type: "object", properties: { country: { type: "string", enum: Object.keys(COMPLIANCE_CHECKS) } }, required: ["country"] } },
        { name: "get_full_apac_pack", description: "Complete APAC pack for fine-tuning or full agent context.", inputSchema: { type: "object", properties: {}, required: [] } }
      ]
    }));
Behavior3/5

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

No annotations are present, so the description must convey behavioral traits. It describes the output (e.g., slow vs fast cadence, gap days) but does not explicitly state side effects, idempotency, or authorization needs. The 'get' prefix implies read-only, but it is not confirmed.

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?

A single, well-structured sentence that conveys the core functionality and key examples. No unnecessary words or redundancy.

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 tool with one parameter and no output schema, the description provides a good summary of what to expect. However, it does not cover all eight enumerated countries or specify the exact output format (e.g., string, object), which could be considered incomplete.

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?

The input schema has 0% description coverage, but the description compensates by providing concrete examples of expected behavior for three countries (Japan, Singapore, India), thereby adding meaning beyond the enum list. It helps the agent understand how different parameter values affect output.

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 country-specific follow-up cadence, with specific examples of behavior for Japan, Singapore, and India. The verb 'get' and resource 'follow-up cadence' are specific, and the examples distinguish it from sibling tools like get_compliance_check or get_stakeholder_map.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, nor any comparison with sibling tools such as get_outreach_template or get_etiquette_guide, leaving the agent to infer usage context.

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/apac-compliance-mcp'

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