Skip to main content
Glama

get_meeting_actionables

Read-onlyIdempotent

Los accionables de un recap: lo que la IA sacó de la reunión y todavía no es una tarea.

Es una lista VIVA, no un resultado congelado: cada ítem está en
`pending` (propuesto, nadie lo confirmó), `materialized` (ya se convirtió
en tarea, y `task_id` dice cuál) o `dismissed` (descartado, no vuelve).

Los descartados no salen salvo que los pidas. `relevance` y
`action_clarity` son las dos notas con que el extractor se juzga a sí
mismo: sirven para entender por qué un ítem quedó abajo en la lista.

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": {
      "meeting_id": "<meeting_id>"
    },
    "name": "get_meeting_actionables"
  }
}

Input Schema

NameRequiredDescriptionDefault
meeting_idYesID del recap (campo 'id' de get_meetings)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada
incluir_descartadosNoSumar los dismissed (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description does add real value by disclosing the live state model (pending / materialized with task_id / dismissed) and that dismissed items are filtered out by default. It still says nothing about ordering, pagination, or volume limits on a 'living' list.

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 resource definition, then the state model, then the filtering caveat, then the score fields — a sensible order with no filler. The explanation of relevance/action_clarity is slightly indirect but still earns its place.

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, the description carries the burden of explaining return values and does so for the most important ones (task_id, relevance, action_clarity, state). What is missing is minor: other returned fields, list ordering, and whether results are paginated.

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 100%, so meeting_id, workspace_id and incluir_descartados are already fully documented, including the cross-workspace default for workspace_id. The description's note that dismissed items only appear if requested restates the schema's default rather than adding new syntax or constraint meaning.

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?

States the specific resource (actionables from a meeting recap) and scopes it precisely as AI-extracted items that are not yet tasks, which implicitly separates it from task-listing siblings. It never names an alternative tool, so the differentiation is inferential rather than explicit.

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: the reader infers this is the read step before confirm_meeting_actionable or dismiss_meeting_actionable, but no when-to-use or when-not-to-use guidance is stated. The one concrete routing rule ('descartados no salen salvo que los pidas') is about a parameter, not about choosing between tools.

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