Skip to main content
Glama

Unread message counts

get_message_unread_counts
Read-only

Modern accounts: get unread message counts for the current and archive folders without opening messages. Independent of get_new_notifications.

Instructions

Modern accounts: get unread message counts for the current and archive folders without opening messages. Independent of get_new_notifications.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_alias": "<account_alias>"
    },
    "name": "get_message_unread_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_aliasYesLogin alias from list_accounts.

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.8.1
    • changedOutput schema / $defs / Observation / properties / observed_at / pattern
      Previous value: -"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(?:\\.[0-9]{1,6})?(?:Z|[+-][0-9]{2}:[0-9]{2})?$"New value: +"^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}(\\.[0-9]{1,6})?(Z|[+-][0-9]{2}:[0-9]{2})?$"
  2. Changed1 schema field changedv2.5.0
    • removedOutput schema / additionalProperties
      Removed value: -false
  3. Changed2 schema fields changedv2.3.1
    • addedInput schema / properties / account_alias / description
      Added value: +"Login alias from list_accounts."
    • changedInput schema / properties / account_alias / pattern
      Previous value: -"^(?:[^\\s\\x00-\\x1f\\x7f]|[^\\s\\x00-\\x1f\\x7f](?:[^\\s\\x00-\\x1f\\x7f]| )*[^\\s\\x00-\\x1f\\x7f])$"New value: +"^[^\\s\\x00-\\x1f\\x7f](?: *[^\\s\\x00-\\x1f\\x7f])*$"
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real value beyond that by noting counts are obtained 'without opening messages', implying read state is not mutated as a side effect, and by naming the folders included. It does not mention caching, staleness, or rate limits, but the output schema covers return shape.

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 with the capability front-loaded and zero padding. The dangling 'Modern accounts:' colon fragment is slightly cryptic and reads as an unexplained precondition rather than a clean qualifier, costing a point.

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 read-only, single-parameter counter with an output schema and clear annotations, the description supplies what the agent needs: the resource, the folder scope, the no-side-effect hint, and its relationship to the closest sibling. The only gap is the undefined 'modern accounts' term, which is minor for a tool this simple.

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?

There is a single required parameter (account_alias) with 100% schema description coverage pointing to list_accounts, so the schema already does the work. The description adds no further meaning about the alias, and none is needed; baseline 3 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 ('get unread message counts') plus the exact scope covered ('current and archive folders'), and explicitly differentiates itself from the sibling get_new_notifications. An agent can identify the correct tool without opening the schema.

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 'Independent of get_new_notifications' clause is a useful routing signal, telling the agent these counts are not the same data as notification state. However, the 'Modern accounts:' qualifier is never defined and no fallback is given for non-modern accounts, and no guidance distinguishes this from get_messages when an agent simply wants message listings.

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