Skip to main content
Glama
dpkdhingra91

AI Interview Agents MCP Server

send_reminders

Idempotent

Send reminder emails for pending interviews, skipping completed meetings. Use idempotency key to avoid duplicate sends on retry.

Instructions

Send reminder emails for one or more pending interviews. Skips already-completed meetings. Pass the same idempotency_key on retry to avoid duplicate sends.

    ASK BEFORE CALLING if the user said "remind everyone" / "the
    no-shows" / anything that resolves to >1 meeting and you don't
    have an explicit list. Call list_meetings (filter by status) first,
    show the user the meetings you'd remind, and confirm before sending.
    Reminder emails to the wrong candidates are an embarrassing leak.

    Cap: 100 meeting_ids per call. For more, batch across multiple calls.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meeting_idsYes
idempotency_keyNo
Behavior5/5

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

Annotation idempotentHint=true is reinforced with idempotency_key explanation; describes skipping completed meetings and batch limit. No contradictions.

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?

Well-structured with clear warnings, no redundant sentences, and efficient use of whitespace.

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

Completeness5/5

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

Covers all key behaviors, retry pattern, and batching; no output schema needed for this tool.

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%, but description adds context for idempotency_key and meeting_ids cap. Lacks explicit mention of array type but adds useful semantics beyond 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?

The description clearly states it sends reminder emails for pending interviews, distinguishing it from sibling tools like list_meetings or schedule_interview.

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

Usage Guidelines5/5

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

Provides explicit guidance: ask before calling for ambiguous requests, list meetings first, confirm with user, and mentions batch cap of 100.

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/dpkdhingra91/aiia-mcp-server'

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