Skip to main content
Glama
PhononX

Carbon Voice

by PhononX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_my_action_items

Read-only

Find every action item you owe or created across all conversations and folders. Filter by status (todo, suggested, done) and paginate through results.

Instructions

List your action items across every conversation and folder: those assigned to you, PLUS unassigned ones you created. USE WHEN: Answering "what do I owe / what is on my plate" — but check assigned_to before calling something the user's own commitment: a null one is an item they raised that nobody has picked up. Filter by status (todo open, suggested AI-proposed, done complete). Page with starting_after. USE INSTEAD: list_action_items when you want one specific conversation or folder rather than everything of yours. EXAMPLE: {"status":"todo","limit":25} RETURNS: {results: [{id, title, status, notes_text?, assigned_to?, due_date?, container_id?, container_type?, source_message_id?, creator_id, ...}], total?, results_count?, has_more?, next_cursor?, filters?}. Keep paging while has_more is true, passing next_cursor as starting_after. NARROW: pass response_fields ["results.id","results.title","results.status","results.assigned_to","results.due_date"] unless you need more — the full payload is much larger.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoAnchor timestamp to start from. Uses updated_at. Ignored when starting_after/ending_before is provided.
limitNoNumber of items to return (min: 1, max: 100)
statusNo
directionNonewer
ending_beforeNoCursor to fetch the previous page (use value from previous_cursor).
starting_afterNoCursor to fetch the next page (use value from next_cursor).
response_fieldsNoDot-path allowlist to shrink the response, e.g. ["results.id","total"]. Omit for the full payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.10.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds rich context: return payload shape, pagination loop with has_more/next_cursor/starting_after, status value meanings, and the null assigned_to caveat. It also gives a concrete example, going well beyond structured annotations.

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?

Although long, the description is structured with clear labels (USE WHEN, USE INSTEAD, EXAMPLE, RETURNS, NARROW) and front-loads the core purpose. Every section contributes actionable guidance with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 fully specifies return fields, pagination behavior, and filtering semantics. It covers the main use case, common edge case (null assigned_to), and performance tip, making it self-sufficient for correct invocation.

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 71%, and the description compensates by explaining status enum values (todo, suggested, done), pagination via starting_after, and response_fields narrowing with a performance rationale. It doesn't repeat what schema already says about date/limit/direction, but adds meaningful value.

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: 'List your action items across every conversation and folder', with clear inclusion criteria (assigned to you PLUS unassigned ones you created). It also distinguishes itself from list_action_items by scope, so an agent can tell them apart.

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

Usage Guidelines5/5

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

Explicitly provides USE WHEN and USE INSTEAD sections. It tells the agent when to call this tool (what do I owe / what is on my plate), warns about null assigned_to semantics, and names list_action_items as the alternative for a specific conversation/folder.

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

Deploy Server

Other Tools