Skip to main content
Glama
OnStartups

Agent.ai MCP Server

by OnStartups

meeting_prep_v3_run_optimized_pipeline

Prepares a personalized meeting briefing using calendar event data, seller profile, and past meetings to generate custom sections.

Instructions

V3: Full meeting prep pipeline with seller profile integration. Generates personalized sections when seller profile is available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
raw_eventYesThe raw calendar event data from Google Calendar API.{{enriched_calendar_event}}
user_emailYesCurrent user's email address.{{_google_email}}
user_dataNoUser profile data including optional seller_profile for personalization.{{user.context}}
company_domainsNoOptional company domains. Auto-detected if not provided.
meeting_historyNoOptional past meetings for relationship analysis.{{past_calendar_events}}
contact_researchNoOptional pre-fetched contact research results.{{contact_research_results}}
meeting_sectionsNoOptional pre-generated sections (skips Phase 6 LLM calls).
include_htmlNoGenerate HTML email output (Phase 7).
use_v4_sectionsNoGenerate V3 sections (situation, segues, questions, next_step) instead of V2.
settingsNoOptional settings for trigger validation.{}
output_variable_nameYesVariable name to store pipeline result with timing breakdown.pipeline_result
Behavior2/5

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

With no annotations, the description must convey behaviors. It only mentions generating personalized sections but omits side effects, authentication needs, data processing flow, or output format. The agent cannot infer whether this pipeline is read-only or modifies state.

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?

The description is a single, front-loaded sentence that efficiently conveys the core purpose without unnecessary words. It earns its place.

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?

Given the tool's complexity (11 parameters, no output schema, no annotations), the description is insufficient. It lacks explanation of what the pipeline outputs, how to use the result, and any constraints or dependencies.

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%, so the schema already describes all 11 parameters. The description adds no extra meaning beyond that, making it baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as a V3 meeting prep pipeline with seller profile integration, generating personalized sections. This distinguishes it from similar tools (e.g., v2 pipeline and sub-tools) by highlighting the version and seller profile feature.

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 pipeline vs. other meeting prep tools (e.g., v2 or individual v3 sub-tools). The agent has no information about prerequisites or alternatives.

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