Skip to main content
Glama

Babelii-Diofis Account

Notifikasi saya

account_notifications
Read-onlyIdempotent

The account's notifications, newest first (title and message, whether read). Set unread_only to see only unread ones. Read only.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
unread_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the description's 'Read only' repeats structured data. It does add the useful ordering guarantee ('newest first') and the shape of the returned records, but does not mention pagination or what limit bounds.

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?

Three short, front-loaded sentences with no wasted wording; ordering and default behavior come first. Slight redundancy in restating 'Read only' that annotations already provide.

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?

A simple two-optional-parameter read tool with a full annotation set and an output schema, so it needn't explain return values. The only real gap is the undocumented limit parameter, which has a default and type in the schema and is unlikely to block a correct call.

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?

Schema description coverage is 0%, so the description must carry parameter meaning; it explains unread_only's effect and implies the default returns everything. The limit parameter is never mentioned, leaving half the parameters undocumented in both schema and description.

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?

The description names a specific resource (the account's notifications) and even the returned fields (title, message, read status), so an agent knows exactly what it gets. It lacks an explicit verb like 'list' and offers no sibling differentiation, but no other notifications tool exists in the catalog, so a 4 is fair rather than a 5.

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 states 'Set unread_only to see only unread ones', implying the default is the full list, and 'Read only' signals safe usage. There is no explicit when-to-use vs alternatives guidance, though no true alternative exists among the siblings, leaving usage only implied.

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.

Resources