Skip to main content
Glama

link_event_task

DestructiveIdempotent

Vincula una tarea a un evento del calendario (o la desvincula): la tarea aparece en el evento y el evento en la tarea. Es lo que hace «agendar esta tarea» una vez creado el evento con create_event. action: attach (default) | detach.

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": {
      "event_id": "<event_id>",
      "task_id": "<task_id>"
    },
    "name": "link_event_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNo
task_idYesID numérico de la tarea
event_idYesID del evento (de get_events)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description adds meaningful semantics: the link is bidirectional and attach is the default action. However, it never explains what detach actually removes (link only, not task/event) or whether permissions are needed, which is the key behavioral question for a tool flagged destructive.

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?

Three sentences, front-loaded with the verb and resource, then the effect, then the create_event prerequisite and action values. No filler, though the parenthetical '(o la desvincula)' early followed by the action list at the end is slightly redundant.

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?

With no output schema and only four parameters, the description covers purpose, both modes, the default action and the ordering prerequisite, which is nearly everything an agent needs to call it. It is missing a note on the asymmetry of impact (attaching is additive, detaching mutates an existing event) and any statement of return behavior.

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 75% and the description adds the one thing the enum does not: that 'attach' is the default value when action is omitted. For task_id, event_id and workspace_id it adds nothing beyond the schema descriptions, so the gain is real but partial.

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 states a specific verb and resource pair ('Vincula una tarea a un evento') and immediately names both modes (attach and detach), plus the bidirectional effect ('la tarea aparece en el evento y el evento en la tarea'). It also positions itself relative to the sibling create_event ('una vez creado el evento con create_event'), so an agent can distinguish it without opening the schema.

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

Usage Guidelines4/5

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

It gives a concrete usage trigger — the user phrase «agendar esta tarea» — and an explicit prerequisite that the event must already exist via create_event. It does not state when to prefer this over alternatives such as add_entity_relation, nor any exclusion conditions, which keeps it below a 5.

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