Mark all notifications as read
crm_mark_all_notifications_readClear the CRM notification badge by marking everything read.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Vendo AI
by com.vendo-ai
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the transparency burden. It clearly discloses the primary behavioral effect: all notifications are marked read and the badge is cleared. It does not discuss irreversibility or response behavior, but for this simple state-change operation the stated effect is the core behavior.
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 sentence with no filler. It front-loads the action ('Clear the CRM notification badge') and immediately provides the mechanism ('marking everything read'), making it efficient and scannable.
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 zero-parameter, no-output-schema operation, the description is complete: it states purpose, scope, and effect. Nothing essential is missing for an agent to decide to invoke it correctly.
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?
The input schema has zero parameters and 100% schema description coverage, so there are no parameter details to clarify. The rubric baseline for zero-parameter tools applies, and the description introduces no misleading parameter information.
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 concrete verb and resource: 'marking everything read' to 'Clear the CRM notification badge.' The name and description emphasize 'all' vs. the sibling crm_mark_notification_read, so an agent can tell them apart without extra context.
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 use case is implied by the title and description: use this when you want to clear the whole badge rather than mark a single notification read. However, there is no explicit mention of when-not-to-use or a direct pointer to crm_mark_notification_read as the alternative.
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.
TDQS
B3.1/5.0
Disambiguation2/5
Despite consistently detailed descriptions, several tool pairs have unclear boundaries: `get_subscription_limits` and `get_agent_plan_limits` describe essentially the same agent-slot check, `crm_get_conversation` and `crm_communication_thread` both claim to return the full message thread, and `get_credit_usage_by_agent` vs `get_credit_usage_for_agent` differ only by preposition. At 149 tools, an agent will regularly misselect between these near-duplicates.
Naming Consistency4/5
The dominant pattern is verb_noun with domain prefixes (`crm_*`, `sdr_*`) and a consistent `preview_*` family that maps cleanly to destructive/expensive actions. Deviations are minor but real: CRM deletes use the inverted `delete_crm_*` form while other CRM ops use `crm_*`, and credit-usage tools mix `by_agent`/`for_agent` prepositions.
Tool Count1/5
149 tools is nearly three times the 50+ threshold the rubric treats as extreme, even though the platform genuinely spans agents, campaigns, audiences, CRM, SDR, billing, and connections. Many could be consolidated without losing capability — e.g. the 11 balance/credit-usage tools, the two LinkedIn-account listers, and the 15+ preview variants.
Completeness5/5
The surface is remarkably complete: full CRUD/lifecycle coverage for agents, campaigns, audiences, CRM leads/stages, and SDR searches, plus billing, analytics, and connection management. Destructive or costly operations all have preview/approval counterparts, so there are no dead ends. If anything the risk is over-coverage rather than gaps.