Skip to main content
Glama
OnStartups

Agent.ai MCP Server

by OnStartups

meeting_prep_validate_meeting_trigger

Validates calendar event trigger data and applies filtering rules including exclusion keywords, domain filters, external-only checks, and time window constraints.

Instructions

Validates calendar event trigger data and applies filtering rules (exclusion keywords, domains, external-only, time window).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trigger_dataYesThe calendar event trigger data to validate. Usually from {{trigger_data}}.{{trigger_data}}
user_emailYesCurrent user's email address for domain detection.{{_google_email}}
company_domainsNoOptional JSON array of internal company domains. Auto-detected from user email if not provided.
settingsNoOptional settings: {external_only: bool, exclude_keywords: [], exclude_domains: [], max_days_future: int, max_days_past: int}{}
output_variable_nameYesVariable name to store validation result.validated_trigger
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It explains it validates and filters, but doesn't mention side effects, state changes, or what happens with invalid data. Adequate but minimal.

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?

Single sentence, ~20 words, front-loaded with action and key filtering rules. No redundant information.

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

Completeness2/5

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

No output schema, and description doesn't explain output format or how it fits into a workflow. Missing details about what the validated output contains, limiting completeness for an agent.

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%, with detailed parameter descriptions. The tool description adds a high-level overview but no new parameter-specific info. Baseline score of 3 is appropriate.

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 validates calendar event trigger data and applies specific filtering rules (exclusion keywords, domains, external-only, time window). This differentiates it from siblings like meeting_prep_process_calendar_event.

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 vs alternatives, prerequisites, or conditions. The description only states functionality without context for decision-making.

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/OnStartups/agentai-mcp-server'

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