Skip to main content
Glama

conduyt_ai_agenda

Build a read-only daily agenda that surfaces calendar events, promised callbacks, waiting messages, overdue tasks, new leads, follow-ups, and quiet deals, with an optional AI or deterministic brief.

Instructions

The copilot's Today agenda for a user: what is on their calendar today (tenant timezone), callbacks they promised, messages waiting for a reply, overdue and due-today tasks, untouched new leads, recent-call follow-ups and deals going quiet — every visibility and opt-out rule applied — with a short brief on top (composed by the account's AI engine when available, otherwise a deterministic sentence built from the counts). Read-only.

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

Input Schema

NameRequiredDescriptionDefault
userIdNoUser UUID to build the agenda for (admins/owners only; defaults to the authenticated user)
narrativeNofalse = skip the AI-composed brief and return the deterministic one (spends no AI budget)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.71.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and mostly does: it declares 'Read-only' (safety profile), states that every visibility and opt-out rule is applied, notes the tenant timezone for calendar items, and discloses the AI-budget/fallback behaviour of the brief. It does not cover response size, pagination or limits, so gaps remain but the important behaviour is disclosed.

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?

One front-loaded sentence names the deliverable first, then the em-dash clause enumerates contents, then two short trailing clauses cover the brief and read-only status. The list is long but every item is a distinct agenda category the caller must know; nothing is filler.

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 and no annotations, the description is the only source of truth, and it adequately covers what is returned (categorised items plus a summary brief, with counts available from the categories) and the per-user scoping. Missing only return-shape specifics such as ordering, caps or whether empty categories appear.

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 explains both userId (admin/owner, defaults to authenticated user) and narrative (skip AI brief, spends no AI budget). The description reinforces the narrative semantics via the 'AI engine when available, otherwise deterministic' sentence but adds no format, constraint or edge-case detail beyond the schema.

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 a specific verb+resource (build the copilot's Today agenda for a user) and then enumerates the concrete item types included: calendar, promised callbacks, awaiting-reply messages, overdue/due-today tasks, untouched leads, follow-ups, quiet deals. That is far more specific than a generic 'get agenda', but it never names a sibling, and close ones (conduyt_ai_daily_brief, conduyt_ai_next_actions, conduyt_dashboard) are left for the agent to disambiguate on its own.

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 the 'Today agenda' framing and by 'Read-only', and the visibility/opt-out note signals it is a per-user daily view rather than a raw list endpoint. However, there is no explicit when-to-use versus when-not, no condition selecting it over conduyt_ai_daily_brief or conduyt_ai_feed, and the admin/owner restriction on userId lives only in the schema.

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