Skip to main content
Glama

Coline

Attach to event

attach_to_event

Attaches a file, a channel or a web page to an event, for everyone invited. 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>",
      "link": "<link>"
    },
    "name": "attach_to_event"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
linkYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare that this is a non-read-only, non-destructive, non-idempotent operation. Beyond that, the description adds meaningful behavior: the attachment is visible to everyone invited, and the caller must be the organizer. It does not explain duplicate handling or error conditions, but it adds useful auth and visibility context beyond the annotations.

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 two tight sentences with no wasted wording. The core action is front-loaded, followed by the audience and permission constraints.

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?

For a three-parameter mutation tool with an output schema and useful annotations, the description covers the non-obvious authorization requirement and visibility scope. The complex link oneOf is largely self-describing in the schema, though the description could say more about duplicate attachments or workspace-bound file/channel requirements.

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 coverage is 67%, with eventId and workspace documented in the schema while the link parameter is not described at the top level. The description identifies the three link kinds (file, channel, web page), which maps usefully onto the link oneOf variants, but it adds no detail about the nested fields, labels, or required identifiers beyond what the schema already structures.

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 states a specific verb and resource: attaching a file, channel, or web page to an event. It also clarifies the audience scope ('for everyone invited'), making the action distinguishable from unrelated attachment tools. It does not explicitly differentiate itself from the sibling remove_event_attachment or attach_to_task, so it falls short of a 5.

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?

The phrase 'Needs the organizer' gives an important prerequisite for use, but the description does not say when to choose this tool over alternatives or when not to use it. The intended usage is implied by the tool name and description rather than explicitly guided.

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