Skip to main content
Glama

Coline

Respond to event

respond_to_event
DestructiveIdempotent

Accepts, tentatively accepts or declines an invitation for the person.

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>",
      "response": "<response>"
    },
    "name": "respond_to_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventIdYesEvent id from list_events.
responseYesaccepted, tentative or declined; needs_action takes the answer back.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
eventYes
invitesYesWhether emails to people outside Coline went out, or wait for the person's approval in Coline.
approvalUrlYes

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?

Annotations already disclose the important traits - destructiveHint=true, idempotentHint=true, readOnlyHint=false, openWorldHint=true - so the safety profile is covered structurally. The description adds the useful scoping fact that the response is recorded "for the person" (the authenticated user, not other attendees), but says nothing about side effects like notifying the organizer or whether a prior response is overwritten.

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?

A single front-loaded sentence with no filler or redundancy. It is trimmed to the point of omitting useful context, but nothing in it is wasted.

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?

The tool is simple (3 required params, output schema present) and the description plus schema cover the mechanics well enough to invoke it. What is missing is behavioral consequence - who gets notified, whether re-responding overwrites - which matters for a destructive, open-world mutation.

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 description coverage is 100%, so baseline would be 3; the phrase "for the person" adds a sliver of meaning by clarifying that no attendee identifier is accepted and the response always applies to the caller. The four-valued response enum, including the needs_action rollback, is documented in the schema rather than the description, which is acceptable.

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 set (accepts, tentatively accepts, declines) applied to a concrete resource (an invitation) on behalf of a named actor (the person). It is clear about what the tool does, though it never names a sibling such as update_event or create_event to draw the boundary 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 only implied: an agent can infer this applies when the user has been invited and wants to RSVP. There are no explicit when-to-use/when-not conditions and no statement about prerequisites (e.g., must be an invitee), leaving selection against update_event or delete_event to the caller.

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