Skip to main content
Glama

confirm_meeting_actionable

DestructiveIdempotent

Convierte un accionable de un recap en tarea, o deshace esa confirmación: lo mismo que tildarlo en el recap de la app.

· accept (default): nace la tarea con el título, la fecha, el responsable,
  el proyecto y la organización que detectó el recap, atada al recap y
  privada de quien la confirma. Si la reunión dijo una hora, además suena
  como recordatorio. Si ya se había confirmado y se deshizo, vuelve LA
  MISMA tarea, con lo que se le haya editado.
· undo: la tarea se va y el accionable vuelve a quedar por confirmar.

Los ids salen de get_meeting_actionables. Es una escritura: se hace cuando
la persona lo pide o lo confirma.

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": {
      "actionable_id": "<actionable_id>"
    },
    "name": "confirm_meeting_actionable"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoaccept (default) crea la tarea; undo la deshace
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
actionable_idYesID del accionable (de get_meeting_actionables)

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 this is a non-read-only, destructive, idempotent write; the description goes further by naming side effects annotations cannot express: the task inherits title/date/owner/project/org, is private to the confirmer, spawns a reminder when the meeting specified a time, and undo re-creates the same edited task. That is real added value, but it omits what the call returns and what happens if the actionable is already confirmed when accept is called.

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?

Front-loaded with the verb and resource, then structured as bulleted semantics for accept and undo, ending with id sourcing and the write warning. Slightly verbose but every clause carries meaning; minor redundancy between the prose and the action enum description.

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 3-parameter mutation with annotations and no output schema, the description covers preconditions, idempotency behavior, side effects and privacy. The only meaningful gap is the return value or what the agent should report back after confirming.

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 100%, so the schema baseline is 3; the description earns a notch more by explaining the consequences behind each enum value, including that a re-accept after undo restores the original task with edits applied. The workspace_id parameter is left to the schema, which is acceptable given full coverage.

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?

States a specific verb and resource ('Convierte un accionable de un recap en tarea, o deshace esa confirmación') and pins the model with the analogy of ticking the checkbox in the recap. The accept/undo split is spelled out, so an agent knows exactly what the tool does 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?

Gives an explicit provenance rule ('Los ids salen de get_meeting_actionables') and a use condition ('se hace cuando la persona lo pide o lo confirma'), which is clear when-to-use guidance. It does not name any alternative or when-not-to-use case (e.g. dismissing instead of confirming), so it stops short of full routing guidance.

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