Skip to main content
Glama

dismiss_meeting_actionable

DestructiveIdempotent

Descarta un accionable de un recap: sale de la lista y no vuelve a proponerse. Si ya se había convertido en tarea, esa tarea se borra también. Es lo mismo que la cruz del recap en la app. Pedí confirmación antes.

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": "dismiss_meeting_actionable"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral detail beyond them: the item is suppressed from future proposals, and a previously converted task is also deleted — a cascade effect the agent must know. It does not cover permissions or the response shape.

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?

Four short sentences, each carrying a distinct fact: effect, suppression, cascade deletion, UI analogy, confirmation requirement. The primary consequence is front-loaded and nothing is 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?

For a destructive single-target mutation with no output schema, the description covers what is destroyed, the secondary deletion, and the confirmation requirement. It leaves out error cases and the return value, but nothing essential to calling it correctly is missing.

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 description coverage is 100%, with both parameters documented, including the pointer to get_meeting_actionables as the source of actionable_id. The description adds no further meaning about the parameters themselves, so the baseline of 3 applies.

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 ('Descarta un accionable de un recap') and immediately spells out the effect: it leaves the list and won't be proposed again. That is enough for an agent to distinguish it from confirm_meeting_actionable, which keeps the item rather than removing it.

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 anchors usage to a concrete UI affordance ('la cruz del recap en la app') and imposes a prerequisite: ask for confirmation before calling. It stops short of naming when NOT to use it or pointing at the sibling confirm_meeting_actionable, so the alternative-selection guidance is implied rather than explicit.

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