Skip to main content
Glama

inbox

View unread notifications, then set read=true to mark them all as read. Use it to check for new activity that needs attention.

Instructions

Your unread notifications; read=true marks them all read.

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

Input Schema

NameRequiredDescriptionDefault
readNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key behavioral fact: read=true is a bulk mutation affecting ALL notifications, not just selected ones. It does not say whether that is reversible, whether the call still returns the notifications when reading, or what the absent-flag default returns beyond "unread".

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 short sentence, front-loaded with the resource and immediately followed by the mode switch. No filler, no restatement of the name, nothing to trim.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-optional-parameter, no-output-schema tool the description covers the essentials, but a no-annotation bulk mutation deserves at least a note on irreversibility and on what read=true returns. It is adequate rather than complete.

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 schema gives only {"read": boolean} with 0% description coverage, so the description carries the meaning: true = mark all read, absent = just list unread. That covers the only parameter's semantics, though it omits that the parameter is optional (required list is empty).

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?

"Your unread notifications" names the resource and default scope, and "read=true marks them all read" names the second mode. The verb for the primary mode is only implied, but an agent can tell this is a notifications inbox rather than a task/project tool from the sibling list.

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?

It supplies a conditional usage rule for the flag (use read=true when you want to mark them read), which is implicit mode guidance. It offers no when-to-use vs. alternatives, no exclusion, and no warning about the consequences of the flag.

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