Skip to main content
Glama
OnStartups

Agent.ai MCP Server

by OnStartups

meeting_prep_summarize_internal_team

Summarizes internal team members attending a meeting and identifies the organizer using calendar event and attendee data.

Instructions

Generates a summary of internal team members attending the meeting, including organizer identification.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
processed_gcal_eventYesThe processed calendar event data with organizer info.{{processed_gcal_event}}
classified_attendeesYesThe classified attendees with internal_attendees list.{{classified_attendees}}
contact_research_resultsNoOptional research results for team member profiles.{{contact_research_results}}
user_emailYesCurrent user's email address.{{_google_email}}
user_nameNoCurrent user's full name.{{user.context.first_name}} {{user.context.last_name}}
use_llmNoEnable to use LLM for more detailed summaries. Slower but provides richer context.
output_variable_nameYesVariable name to store internal team summary.internal_team_summary
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'generates a summary.' It does not disclose whether the tool is read-only or destructive, nor does it mention that it may use an LLM (see use_llm parameter) or that it processes existing data without side effects.

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 sentence that is direct and free of unnecessary words. It efficiently conveys the core function.

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?

The tool has 7 parameters (4 required) and no output schema. The description does not explain the return value format, the role of each parameter, or how the summary is constructed. For a tool in a complex pipeline, this is incomplete.

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 adds limited value beyond schema: it mentions 'internal team members' and 'organizer identification,' which align with parameters like classified_attendees and processed_gcal_event, but does not elaborate on optional parameters like contact_research_results or use_llm.

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 states the tool generates a summary of internal team members and identifies the organizer. However, it could be more specific about the summary content, e.g., roles, responsibilities. It distinguishes from sibling tools like meeting_prep_classify_meeting or 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 is provided on when to use this tool versus alternatives like meeting_prep_analyze_meeting_relationships. The description omits prerequisites, such as requiring classified_attendees from a previous step, and fails to indicate that it is part of a larger pipeline.

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