Skip to main content
Glama

read_notification

Mark a notification as read in Habitica by providing its unique notification ID.

Instructions

Mark a notification as read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notificationIdYes

Implementation Reference

  • Tool definition / input schema for 'read_notification'. Declares the tool name, description, and input schema requiring 'notificationId' (string).
    name: "read_notification",
    description: "Mark a notification as read.",
    inputSchema: {
      type: "object",
      properties: { notificationId: { type: "string" } },
      required: ["notificationId"],
    },
  • Handler implementation for 'read_notification'. Sends a POST request to /notifications/{notificationId}/read via the Habitica API and returns a success message.
    read_notification: async ({ notificationId }) => {
      await api("POST", `/notifications/${notificationId}/read`);
      return ok(`Marked notification ${notificationId} read.`);
    },
  • index.js:482-492 (registration)
    Generic tool call routing via CallToolRequestSchema. Looks up the handler by name in the 'handlers' object and invokes it with the provided arguments.
    server.setRequestHandler(CallToolRequestSchema, async (req) => {
      const { name, arguments: args = {} } = req.params;
      const fn = handlers[name];
      if (!fn) throw new McpError(ErrorCode.MethodNotFound, `Unknown tool: ${name}`);
      try {
        return await fn(args);
      } catch (err) {
        if (err instanceof McpError) throw err;
        throw new McpError(ErrorCode.InternalError, err?.message ?? String(err));
      }
    });
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only states 'Mark as read', which is a mutation, but does not disclose whether the operation is idempotent, what happens to the notification (e.g., disappear, change state), or any permission requirements.

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?

The description is a single sentence with no fluff. It is appropriately sized for the tool's simplicity, and every word is necessary.

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?

Given the simple nature of the tool (one parameter, no output schema), a minimal description might suffice, but the lack of parameter explanation and return value information makes it incomplete. An agent needs to know what to expect after execution.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must explain the parameter. It does not mention 'notificationId' at all, leaving the agent unsure of its meaning, origin, or format beyond the type 'string'.

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 clearly states the verb 'Mark' and the resource 'notification', indicating the action to mark a notification as read. It distinguishes from 'get_notifications' which lists notifications, but does not explicitly contrast with other sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, such as needing a valid notification ID from 'get_notifications', or when it is appropriate to mark as 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/leon-jarvis1/habitca_mcp'

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