Skip to main content
Glama

Coline

Propose a new time

propose_new_time
Destructive

Proposes a different time for an event the person is invited to; the organizer is told and can accept it.

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>",
      "startsAt": "<startsAt>",
      "endsAt": "<endsAt>",
      "timeZone": "<timeZone>"
    },
    "name": "propose_new_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
endsAtYes
commentNo
eventIdYesEvent id from list_events.
startsAtYesISO 8601 with a time zone offset.
timeZoneYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

The description usefully adds two things beyond the annotations: a notification side effect (the organizer is informed) and the fact that the outcome is tentative until accepted. However, destructiveHint=true and idempotentHint=false are left unexplained — the agent is not told whether an existing proposed time is replaced, whether repeated calls stack proposals, or what permission is required.

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?

A single tight sentence with the action and its consequence front-loaded and the precondition attached. Nothing is wasted and nothing needed for selection is buried.

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 exists, so return values need not be described, and the notification consequence is covered. Still, for a non-idempotent, destructive, open-world mutation the description should say what happens to any prior proposal and what state the event ends up in, which it does not.

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?

At 50% schema description coverage, eventId, startsAt and workspace are documented while endsAt, timeZone and comment are not. The description's phrase 'a different time' loosely frames the startsAt/endsAt pair but adds no meaning about timeZone handling or what the optional comment is for, so it neither compensates for the gap nor is empty.

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 gives a specific verb ('proposes') and resource ('a different time for an event'), plus the precondition that the caller is an invitee. That is enough to separate it from siblings like propose_cycle_plan (a different resource) and answer_proposed_time (the counterpart action), though it never names those siblings 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?

Usage is implied rather than stated: 'an event the person is invited to' tells the agent it must be an invitee, and 'the organizer is told and can accept it' implies this is a request, not a confirmation. There is no explicit when-to-use versus when-not, and no pointer to answer_proposed_time or accept_booking_request as the follow-up path.

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