Skip to main content
Glama

Duvo MCP

by io.github.duvoai

List Notifications

listNotifications
Read-onlyIdempotent

List notifications for the authenticated user's current team, most recent first. Filter with type, unread, severity or minSeverity (mutually exclusive), important, agentRunId, or processId; paginate with limit/cursor. Pass batchId to list only the live members of a notification batch, optionally ordered by sort=importance (only valid together with batchId). Requires the Notification Center feature; returns 404 when it is not enabled for the team.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoimportance orders by type importance then severity (only valid together with batchId); default recency.recency
typeNoOnly return notifications of this type. One of: connection_broken, case_failed, critical_case_issue, case_issue, critical_eval_issue, eval_issue, job_issue, job_done, background_job, schedule_issue, config_proposal.
limitNoNumber of notifications per page (1-100, default 30).
cursorNoOpaque cursor from the previous page's nextCursor. Omit for the first page.
unreadNoIf true, only return unread notifications.
batchIdNoOnly return live members of this notification batch.
team_idNoDuvo team UUID to operate on. API keys are pinned to a single team — omit this (it falls back to the key's team) or pass that same team; a different team is rejected. OAuth callers, who can span multiple teams, should pass the target team here.
severityNoOnly return notifications with this severity. One of: info, warning, critical, success.
importantNoIf true, only return important notifications: unresolved connection_broken rows pinned until reconnected, removed, or dismissed.
processIdNoOnly return notifications about this Clarity process.
agentRunIdNoOnly return notifications about this agent run.
minSeverityNoOnly return notifications at or above this urgency. Least to most urgent: success < info < warning < critical. Mutually exclusive with severity.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Only return notifications of this type. One of: connection_broken, case_failed, critical_case_issue, case_issue, critical_eval_issue, eval_issue, job_issue, job_done, background_job, schedule_issue."New value: +"Only return notifications of this type. One of: connection_broken, case_failed, critical_case_issue, case_issue, critical_eval_issue, eval_issue, job_issue, job_done, background_job, schedule_issue, config_proposal."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "connection_broken",
-  "case_failed",
-  "critical_case_issue",
-  "case_issue",
-  "critical_eval_issue",
-  "eval_issue",
-  "job_issue",
-  "job_done",
-  "background_job",
-  "schedule_issue"
-]New value: +[
+  "connection_broken",
+  "case_failed",
+  "critical_case_issue",
+  "case_issue",
+  "critical_eval_issue",
+  "eval_issue",
+  "job_issue",
+  "job_done",
+  "background_job",
+  "schedule_issue",
+  "config_proposal"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Only return notifications of this type. One of: connection_broken, critical_eval_issue, eval_issue, job_issue, job_done, background_job, schedule_issue."New value: +"Only return notifications of this type. One of: connection_broken, case_failed, critical_case_issue, case_issue, critical_eval_issue, eval_issue, job_issue, job_done, background_job, schedule_issue."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "connection_broken",
-  "critical_eval_issue",
-  "eval_issue",
-  "job_issue",
-  "job_done",
-  "background_job",
-  "schedule_issue"
-]New value: +[
+  "connection_broken",
+  "case_failed",
+  "critical_case_issue",
+  "case_issue",
+  "critical_eval_issue",
+  "eval_issue",
+  "job_issue",
+  "job_done",
+  "background_job",
+  "schedule_issue"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / type / description
      Previous value: -"Only return notifications of this type. One of: connection_broken, job_issue, eval_issue, job_done, background_job, schedule_issue."New value: +"Only return notifications of this type. One of: connection_broken, critical_eval_issue, eval_issue, job_issue, job_done, background_job, schedule_issue."
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "connection_broken",
-  "job_issue",
-  "eval_issue",
-  "job_done",
-  "background_job",
-  "schedule_issue"
-]New value: +[
+  "connection_broken",
+  "critical_eval_issue",
+  "eval_issue",
+  "job_issue",
+  "job_done",
+  "background_job",
+  "schedule_issue"
+]
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already mark the tool read-only and idempotent, and the description adds non-trivial behavior: a 404 when Notification Center is disabled, cursor pagination, 'live members' batch semantics, and ordering guarantees. It goes well beyond the structured fields and does not contradict them.

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 sentences pack purpose, filter options, pagination, batch mode, and error behavior with no filler. The core scoping detail is front-loaded before the filter enumeration.

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?

For a 12-parameter, all-optional, no-output-schema read tool, the description plus rich schema and annotations covers what an agent needs to call it correctly: ordering, filters, pagination, batch restrictions, and failure mode. The explicit list-and-paginate semantics compensate for the absent output schema.

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 baseline is 3. The description reinforces key constraints such as mutual exclusivity and the batchId/sort coupling, but it does not add substantial new meaning beyond the schema, such as team_id fallback semantics.

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, resource, and scope ('List notifications for the authenticated user's current team, most recent first'), making the core operation unambiguous. It does not explicitly name sibling notification tools such as getNotificationFeed or getNotification, so differentiation is by implication rather than direct exclusion.

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?

The description gives clear in-tool guidance: severity and minSeverity are mutually exclusive, sort=importance is only valid with batchId, and the Notification Center prerequisite yields a 404. However, it never states when to prefer this over sibling notification tools, so usage-vs-alternatives 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.

All Duvo MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

Despite detailed descriptions, many tool names are highly ambiguous, with multiple tools covering the same conceptual actions (e.g., acceptClarityCaptureSuggestion vs. acceptClarityTeamAssignmentSuggestion, or the many deleteClarity*Interview tools). The set is so large that distinguishing between, say, listClarityFolders, listClarityProcesses, and listClarityProcessSummaries requires reading deep into descriptions, reducing agent selection accuracy.

Naming Consistency4/5

The naming convention is predominantly verb_noun (e.g., createClarityProcess, listAgents, deleteQueue), and is remarkably consistent across the 316 tools. There are only minor deviations, such as 'fileSuggestedClarityProcesses' (verb + adjective noun) and 'bulkUpdateCasePriority' (where 'bulk' could be seen as a prefix), but overall the pattern holds strongly.

Tool Count1/5

With 316 tools, this server is extremely oversized for any single agent to manage effectively. The massive number of tools suggests poor modularization—many of these tools likely belong in separate, smaller servers focused on specific domains (e.g., Clarity, Pulse, Agent management). The cognitive load for an agent to choose from 316 options is very high, leading to frequent misselection.

Completeness4/5

The tool surface covers an extraordinarily wide range of operations across the Duvo platform: agents, runs, cases, queues, Clarity processes, skills, integrations, notifications, teams, and more. Most resource types have full CRUD and lifecycle management. Notable minor gaps exist (e.g., no tools for managing specific notification batch severities dynamically, and some interview management is missing batch operations), but for the platform's scope, coverage is impressively thorough.

Resources