Skip to main content
Glama

respondToProposal

Record each participant's accept or reject response to a meeting proposal, specifying a preferred time slot when accepting. Call once per participant; after all accept, the proposal is confirmed.

Instructions

Use this tool to record one participant's response (accept or reject) to a meeting proposal. This must be called once per participant — if a proposal has 3 participants, you must call this tool 3 separate times, once for each participantId. Call getProposal first to see which participants have not yet responded (check the responses array). When accepting, the participant can indicate a preferredSlotId from the proposal's candidateSlots. Once every participant has responded and all accepted, the proposal automatically becomes "accepted" and you can then call createBooking (proposal-based mode) to confirm the meeting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
proposalIdYesUUID of the proposal being responded to.
participantIdYesUUID of the participant submitting their response.
statusYes"accepted" to agree to the proposal, "rejected" to decline.
preferredSlotIdNoUUID of the participant's preferred slot within the proposal (only used when status is "accepted").
noteNoOptional message to include with the response (e.g. reason for rejection).
Behavior4/5

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

No annotations, so description carries full burden. It discloses that the tool must be called per participant, the auto-acceptance condition, and the follow-up action. Lacks details on error states but sufficient for a recording action.

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?

Three sentences, each with purpose. Front-loaded usage guide, no wasted words. Efficiently conveys necessary workflow.

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?

Covers the workflow fully, mentions pre-step (getProposal) and post-step (createBooking). Missing error handling (e.g., duplicate responses) but complete for typical use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. Description adds context: preferredSlotId only for 'accepted', participantId per participant, and linking to candidateSlots. Adds value beyond 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 it records a participant's response to a meeting proposal, specifying the verb 'record' and the resource. It distinguishes from siblings like createProposal and getProposal by focusing on the response action.

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

Usage Guidelines5/5

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

Explicitly states when to use: after calling getProposal, once per participant. Provides a step-by-step workflow and mentions the follow-up call to createBooking after all accepted. Clear distinction from 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/nicholasemccormick/mcp-meetsync'

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