Skip to main content
Glama
OnStartups

Agent.ai MCP Server

by OnStartups

meeting_prep_v3_generate_meeting_sections

Generate seven meeting preparation sections in parallel using tiered AI models, integrating seller profile and cross-meeting context for personalized outcomes.

Instructions

V3: Generates 7 meeting prep sections in parallel with seller profile integration. Uses tiered models and conditional prompt injection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
processed_researchYesThe processed contact research results.{{processed_research}}
target_company_identityYesTarget company information.{{prepared_contacts.target_company}}
meeting_classificationYesThe meeting classification result.{{meeting_classification}}
topic_signalsNoTopic signals from classification.{{meeting_classification.topic_signals}}
meeting_relationshipsNoRelationship analysis results.{{meeting_relationships}}
processed_gcal_eventYesThe processed calendar event data.{{processed_gcal_event}}
user_contextNoUser context for personalization.{{user_context}}
seller_profileNoSeller profile from LoadUserContext: {has_seller_profile, seller_profile}. Sections adapt when available.
sections_to_generateNoV3: overview, attendees, company, situation, segues, questions, next_step. V2: overview, attendees, company, strategy, goals.["overview", "attendees", "company", "situation", "segues", "questions", "next_step"]
use_v4_sectionsNoWhen enabled, generates V3 sections (situation, segues, questions, next_step) instead of V2 (strategy, goals).
fast_modelNoModel for simpler sections (overview, company, questions, next_step).gpt-5-mini
quality_modelNoModel for complex sections (attendees, situation, segues).gpt-5
meeting_memories_answerNoOptional. LLM response from Query Meeting Memories action providing cross-meeting context from prior meetings in this series.{{meeting_memories_answer.llm_response}}
output_variable_nameYesVariable name to store generated sections.meeting_sections
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'tiered models' and 'conditional prompt injection' but does not explain what these entail, nor does it disclose side effects, authentication needs, rate limits, or the mutation behavior of generating sections. The behavioral traits are vague.

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 extremely concise, comprising two sentences that capture the core functionality. It is front-loaded with the key action ('Generates 7 meeting prep sections') and avoids unnecessary details.

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 complexity (14 parameters, no output schema, no annotations) and many sibling tools, the description lacks completeness. It does not explain the return value format, the integration with seller profile beyond mention, or how this tool fits into the larger pipeline. Critical context for an agent is missing.

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%, so every parameter has a description. The tool description adds some context by listing V3 vs V2 sections and mentioning model tiers, but this is already hinted in the parameter descriptions. The description does not significantly enrich understanding beyond the 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 the tool generates 7 meeting prep sections in parallel with seller profile integration. It uses specific verbs ('Generates') and distinguishes itself as 'V3', contrasting with V2 in the parameter schema. This sets it apart from sibling tools like meeting_prep_generate_meeting_sections.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It mentions 'V3' but does not explain the criteria for choosing V3 over V2 or other meeting prep tools. There are no recommendations, exclusions, or context hints.

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