Skip to main content
Glama
matthewdtowles

iwantmymtg-mcp

get_unread_notification_count

Retrieves the number of unread notifications for the authenticated user. Requires an API key for access.

Instructions

Get the count of unread notifications for the authenticated user. Requires IWMM_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'get_unread_notification_count' tool definition with its handler function. The handler calls apiFetch to GET /api/v1/notifications/unread-count.
    export const getUnreadCountTool = {
      name: "get_unread_notification_count",
      description: "Get the count of unread notifications for the authenticated user. Requires IWMM_API_KEY.",
      inputSchema: z.object({}),
      handler: () => apiFetch({ path: "/api/v1/notifications/unread-count", authenticated: true }),
  • The tool schema specifies an empty inputSchema (z.object({})), meaning no input parameters are required.
    export const getUnreadCountTool = {
      name: "get_unread_notification_count",
      description: "Get the count of unread notifications for the authenticated user. Requires IWMM_API_KEY.",
      inputSchema: z.object({}),
      handler: () => apiFetch({ path: "/api/v1/notifications/unread-count", authenticated: true }),
  • The tool is imported from notifications.ts and registered in the tools array at line 85, also exported via toolsByName map at lines 90-92.
      // Notifications (auth)
      listNotificationsTool,
      getUnreadCountTool,
      markNotificationReadTool,
      markAllNotificationsReadTool,
    ];
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It correctly indicates this is a read operation ('Get') and mentions authentication. However, it does not specify the return format (e.g., an integer count) or what happens if the user is not authenticated.

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?

Two short sentences, no unnecessary words. Efficient and front-loaded.

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?

Given the tool has no parameters and no output schema, the description adequately covers purpose and authentication. It could be improved by stating the return type (e.g., an integer count), but it is still fairly complete for a simple count endpoint.

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?

There are no parameters, so the input schema is empty. The description does not need to add parameter information. Baseline 4 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?

The description clearly states the verb 'Get', the resource 'count of unread notifications', and the context 'for the authenticated user'. It is distinct from sibling tools like list_notifications which return the actual notifications.

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 description mentions the requirement for 'IWMM_API_KEY', providing a prerequisite. However, it does not explicitly state when to use this tool versus alternatives like list_notifications or mark_notification_read.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/matthewdtowles/iwantmymtg-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server