Skip to main content
Glama

Message unread summary

bb_message_summary
Read-only

Get unread message counts for every course without opening each one, so you can check whether you have any messages to review.

Instructions

Unread message counts for every course, without opening each course. Useful for "do I have messages?" questions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered, and the description adds the useful behavioral note that it aggregates across all courses without opening each one. However, with no output schema, it does not say what the returned structure looks like (per-course counts vs. a total) or whether zero-unread courses appear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core capability, and the second sentence earns its place by giving a usage framing. 'Without opening each course' slightly restates the 'every course' scope, a minor redundancy but not wasteful.

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?

For a zero-parameter, read-only summary tool, the description conveys purpose, scope, and a usage cue, which is close to enough. The remaining gap is the shape of the returned counts, which neither an output schema nor the description supplies.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies.

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 specific verb and resource ('unread message counts for every course') with explicit scope, and the phrase 'without opening each course' signals this is a bulk aggregate rather than a per-conversation read, distinguishing it from siblings like bb_get_conversation.

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?

The description gives a concrete usage context ('do I have messages?' questions), which tells the agent this is a triage/summary call rather than a detail fetch. It stops short of naming an alternative or stating when not to use it (e.g. after a count is found, go to bb_get_conversation), so it falls below the explicit-alternatives bar.

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