Skip to main content
Glama

Coline

Answer a proposed time

answer_proposed_time
DestructiveIdempotent

Accepts (moving the event) or declines a time an attendee proposed. Needs the organizer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "eventId": "<eventId>",
      "proposalId": "<proposalId>",
      "response": "<response>"
    },
    "name": "answer_proposed_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent id from list_events.
responseYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
proposalIdYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true, but the description adds the crucial reason: accepting *moves the event*, which explains the destructive flag and the consequence for attendees' calendars. The organizer requirement is an authorization detail not present in the annotations. Missing only reversibility and notification 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, action front-loaded, with the key side effect in parentheses immediately after the verb. Slightly telegraphic ("Needs the organizer" reads as a fragment) but no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema and rich annotations reduce the burden, but for a destructive mutation the definition should say where proposalId comes from and what happens to the event on accept or decline. It covers the authorization angle and the event-move side effect but leaves those procedural gaps.

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

Parameters2/5

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

Schema coverage is 50%: workspace and eventId are described in-schema, response is a self-explanatory enum, but proposalId has no description anywhere and the description does not say where to obtain it. The phrase "needs the organizer" could even mislead an agent into looking for an organizer parameter that does not exist.

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?

"Accepts (moving the event) or declines a time an attendee proposed" names a specific verb pair and resource, and the parenthetical clarifies the consequential accept behavior. It implicitly separates this from propose_new_time and list_proposed_times, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

"Needs the organizer" is a genuine prerequisite that filters out non-organizer callers, which is useful guidance. However, it never says when to prefer decline vs accept, nor points to list_proposed_times as the source of the proposal to answer.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources