Skip to main content
Glama
OnStartups

Agent.ai MCP Server

by OnStartups

meeting_followup_generate_all_artifacts

Save time by generating all meeting follow-up artifacts—coaching insights, CRM notes, tasks, email, team update—in one action using parallel LLM calls.

Instructions

OPTIMIZED: Combines coaching (F5) and artifacts (F6) into a single action with 5 parallel LLM calls. Reduces execution time by ~50%. Use this instead of separate F5 and F6 actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
transcript_analysisYesThe analysis from Analyze Transcript action (F4).{{transcript_analysis}}
user_contextNoUser context from Load Followup Context action (F2).{{followup_context}}
user_context_dataNoRaw user.context data as fallback for user name/role.{{user.context}}
enriched_eventYesThe enriched event data with meeting info from Enrich Calendar Event.{{enriched_calendar_event}}
fast_modelNoModel for CRM notes, tasks, and team update.gpt-5-mini
quality_modelNoModel for coaching and email (higher quality).gpt-5
team_channelNoSlack channel for team update.#sales-team
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 all artifacts. Also sets: coaching_insights, followup_artifacts, followup_email, crm_summary, task_list, team_update, email_subject, results_subject, strengths, improvements, recommendations.all_artifacts
Behavior3/5

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

No annotations exist, so description carries full burden. It discloses the composite nature, parallel execution, and performance improvement, but does not cover potential side effects, error handling, or output format beyond what parameter descriptions imply. Adds moderate behavioral context.

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?

Two short sentences front-loaded with 'OPTIMIZED' and key benefits. Every word earns its place with no 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?

Given 9 parameters (3 required) and no output schema, description covers high-level purpose, sibling replacement, and performance. Lacks detail on output structure, but parameter descriptions in schema fill gaps. Overall sufficient for an AI agent to understand when and why to call.

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 baseline is 3. The description itself adds no extra meaning to parameters; the optimization and combination benefit are the only additions. The output_variable_name parameter description lists set variables but is not part of the tool description.

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?

Description clearly states the tool combines coaching (F5) and artifacts (F6) into a single optimized action with 5 parallel LLM calls, reducing time by ~50%. It directly distinguishes from sibling tools (the separate F5 and F6 actions) by naming them and specifying that this replaces them.

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

Usage Guidelines4/5

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

Explicitly advises 'Use this instead of separate F5 and F6 actions,' providing clear context for when to use this tool over alternatives. Does not mention when to avoid using it, but the directive is strong enough for basic guidance.

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