Cromanion

cromanion_mark_read

Idempotent

Mark notifications read once you have passed them on to your human. cromanion_pending returns the unread ones and nothing cleared them, so the queue grew for ever and you re-read the same items on every poll. Send a notificationId for one, or nothing to clear them all. Needs the decisions permission.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`siteId`	No	Which site this call is about. Only needed when your credential covers more than one — cromanion_grants lists them and says whether it is required. Omitting it with several is refused rather than guessed at.
`notificationId`	No	One notification, by the id cromanion_pending returned. Omit to mark every unread one read.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`note`	No
`title`	No	Present when you named one.
`marked`	Yes	How many were actually unread. Zero is a success, not a failure.

Schema Changelog

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

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / siteId

Added value: +{
+  "description": "Which site this call is about. Only needed when your credential covers more than one — cromanion_grants lists them and says whether it is required. Omitting it with several is refused rather than guessed at.",
+  "type": "string"
+}

AddedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark this as non-read-only, idempotent, and non-destructive; the description adds useful context on permission requirements and the 'one notification or all' side effect. It also explains the operational problem it solves. It does not specify the output shape, but an output schema exists to cover that.

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?

The description is compact and front-loaded: purpose, then motivation, then invocation options and permission. The 'queue grew for ever' sentence earns its place by explaining why the tool exists, and there is 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 two optional parameters, full schema descriptions, an output schema, and annotations covering idempotence/destructiveness, the description supplies the missing operational context: when to mark, which permission is needed, and how to choose one-or-all. Nothing essential 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?

Both parameters are already fully documented in the input schema (siteId disambiguation and notificationId semantics incl. omit-to-clear-all), so schema coverage is 100%. The description's parameter guidance mostly restates what the schema already says, so it adds little beyond the baseline.

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?

The description names the exact operation and object ('Mark notifications read') and adds a concrete triggering condition ('once you have passed them on to your human'). It also draws a clear line against cromanion_pending: that tool returns unread notifications, while this one clears them.

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

Usage Guidelines4/5

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

It states when to use the tool, why it is needed (otherwise the queue grows and items are re-read), and a required permission ('Needs the decisions permission'). It stops short of an explicit when-not-to-use list, but the context is clear enough for an agent to choose it correctly.

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

All Cromanion tools Inspect

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.

Resources

Need Help?