Skip to main content
Glama
zeph-to

@zeph-to/mcp-server

by zeph-to

zeph_dismiss

Idempotent

Dismiss a push notification by ID, marking it as read and removing it from the user's feed.

Instructions

Dismiss (mark as read) a specific push notification by ID. Use after processing a notification to clear it from the user's feed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pushIdYesPush ID to dismiss (e.g., "push_01HX...")

Implementation Reference

  • The handler function for zeph_dismiss tool. Accepts a pushId string, calls client.dismissPush(pushId), and returns the result.
      async ({ pushId }) => {
        try {
          await client.dismissPush(pushId);
          return textResult({ dismissed: true, pushId });
        } catch (err) {
          return formatToolError(err);
        }
      },
    );
  • Input schema for zeph_dismiss: requires a pushId string parameter. Also includes description and annotations.
    {
      description:
        'Dismiss (mark as read) a specific push notification by ID. Use after processing a notification to clear it from the user\'s feed.',
      annotations: {
        readOnlyHint: false,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: true,
      },
      inputSchema: {
        pushId: z.string().describe('Push ID to dismiss (e.g., "push_01HX...")'),
      },
    },
  • Registers the zeph_dismiss tool via server.registerTool(name, schema, handler). Exported as registerDismissTool.
    export const registerDismissTool = (server: McpServer, client: ZephApiClient) => {
      server.registerTool(
        'zeph_dismiss',
        {
          description:
            'Dismiss (mark as read) a specific push notification by ID. Use after processing a notification to clear it from the user\'s feed.',
          annotations: {
            readOnlyHint: false,
            destructiveHint: false,
            idempotentHint: true,
            openWorldHint: true,
          },
          inputSchema: {
            pushId: z.string().describe('Push ID to dismiss (e.g., "push_01HX...")'),
          },
        },
        async ({ pushId }) => {
          try {
            await client.dismissPush(pushId);
            return textResult({ dismissed: true, pushId });
          } catch (err) {
            return formatToolError(err);
          }
        },
      );
    };
  • src/index.ts:63-64 (registration)
    Registration call: registerDismissTool(server, client) invoked in createServer().
    registerDismissTool(server, client);
    registerDismissAllTool(server, client);
  • The dismissPush method on ZephApiClient that performs the API call POST /pushes/{pushId}/dismiss.
    async dismissPush(pushId: string): Promise<DismissResponse> {
      return this.request<DismissResponse>('POST', `/pushes/${encodeURIComponent(pushId)}/dismiss`);
    }
Behavior3/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds 'mark as read' and 'clear from feed', which is useful but doesn't add significant behavioral detail beyond the annotations. No contradictions with annotations.

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 sentences, no filler. Front-loaded with the action and resource, followed by usage context. Every sentence earns its place.

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 simple one-parameter tool without output schema, the description adequately covers purpose, usage context, and parameter meaning. Slightly less complete for return value, but not critical.

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 100% with an example for pushId. The description does not add additional parameter semantics; baseline of 3 is appropriate.

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 'Dismiss' and the resource 'specific push notification by ID'. It distinguishes from the sibling 'zeph_dismiss_all' by specifying 'specific' and 'by ID'. The purpose is unambiguous.

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 provides clear when-to-use guidance: 'Use after processing a notification to clear it from the user's feed.' It implies this is for single notifications, contrasting with 'zeph_dismiss_all', though it could explicitly mention not to use for bulk dismissal.

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/zeph-to/mcp-server'

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