Skip to main content
Glama

get_action_items

Lists action items from recent meetings with saved corrections and status applied, prioritizing overdue and soon-due work. Resolves due phrases to dates only when unambiguous.

Instructions

List action items extracted from recent meetings, with the user's saved corrections and status applied. Overdue and soon-due work comes first. Due phrases are resolved to a date only when unambiguous (due_date); otherwise only the spoken phrase is returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_action_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoMeetings from the last N days (default 30, maximum 365). Ignored with meeting_id.
limitNoMaximum action threads (default 50, maximum 200).
ownerNo"me" for the user's own commitments, "others", or a participant name substring. Default: anyone.
statusNoactive (default: open or deferred), open, deferred, done, or all.
meeting_idNoOptional short id or full UUID to limit results to one meeting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses ordering (overdue and soon-due first), that user corrections and status are already applied, and the ambiguity rule for due-date resolution. It omits that the operation is read-only-safe and says nothing about pagination beyond the schema's limit.

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?

Three short sentences, each front-loaded with the most decision-relevant information: what is listed, how results are ordered, and how due dates are resolved. No filler or redundancy.

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 five-parameter read tool with no annotations and no output schema, the description supplies the behavioral context an agent needs: ordering, correction application, and due-date resolution semantics. It could go slightly further on result shape or pagination, but nothing essential for correct invocation 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%, so the schema already documents days, limit, owner, status and meeting_id, setting the baseline at 3. The description mentions due_date and ordering, which is output-side semantics rather than added meaning for the input parameters, so it does not exceed the baseline.

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 opens with a specific verb and resource ("List action items extracted from recent meetings") and adds scope detail about corrections and status being applied. It is clearly distinct from siblings like list_meetings or search_meetings, though it never names them to reinforce the contrast.

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 implied by "recent meetings" and the default 30-day window, but there is no explicit when-to-use guidance, no statement of when to prefer search_meetings or get_meeting, and no exclusions. An agent can infer the purpose but not the routing rules.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.