Skip to main content
Glama
zeph-to

@zeph-to/mcp-server

by zeph-to

zeph_list

Read-only

Retrieve your recent push notifications to review history, avoid duplicates, or reference past messages.

Instructions

List recent push notifications. Use this to check notification history, avoid duplicates, or reference previous messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of pushes to return (default: 5, max: 20)
typeNoFilter by push type

Implementation Reference

  • The handler function that executes the 'zeph_list' tool logic. It calls client.listPushes({limit, type}) and returns a summary array of pushes (pushId, type, title, body truncated to 100 chars, createdAt) along with total count and pagination status.
    async ({ limit, type }) => {
      try {
        const result = await client.listPushes({ limit, type });
        const summary = result.data.map((p) => ({
          pushId: p.pushId,
          type: p.type,
          title: p.title,
          body: p.body?.slice(0, 100),
          createdAt: p.createdAt,
        }));
        return textResult({ pushes: summary, total: summary.length, hasMore: result.pagination.hasMore });
      } catch (err) {
        return formatToolError(err);
      }
    },
  • Input schema definition for 'zeph_list'. Defines a 'limit' param (number, 1-20, default 5) and optional 'type' param (enum: note/link/file/clipboard/hook). Includes annotations (readOnlyHint: true).
    {
      description:
        'List recent push notifications. Use this to check notification history, avoid duplicates, or reference previous messages.',
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
        openWorldHint: true,
      },
      inputSchema: {
        limit: z
          .number()
          .min(1)
          .max(20)
          .default(5)
          .describe('Number of pushes to return (default: 5, max: 20)'),
        type: z
          .enum(['note', 'link', 'file', 'clipboard', 'hook'])
          .optional()
          .describe('Filter by push type'),
      },
    },
  • src/tools/list.ts:6-46 (registration)
    The registerListTool function that registers the 'zeph_list' tool on the MCP server via server.registerTool('zeph_list', ...).
    export const registerListTool = (server: McpServer, client: ZephApiClient) => {
      server.registerTool(
        'zeph_list',
        {
          description:
            'List recent push notifications. Use this to check notification history, avoid duplicates, or reference previous messages.',
          annotations: {
            readOnlyHint: true,
            destructiveHint: false,
            openWorldHint: true,
          },
          inputSchema: {
            limit: z
              .number()
              .min(1)
              .max(20)
              .default(5)
              .describe('Number of pushes to return (default: 5, max: 20)'),
            type: z
              .enum(['note', 'link', 'file', 'clipboard', 'hook'])
              .optional()
              .describe('Filter by push type'),
          },
        },
        async ({ limit, type }) => {
          try {
            const result = await client.listPushes({ limit, type });
            const summary = result.data.map((p) => ({
              pushId: p.pushId,
              type: p.type,
              title: p.title,
              body: p.body?.slice(0, 100),
              createdAt: p.createdAt,
            }));
            return textResult({ pushes: summary, total: summary.length, hasMore: result.pagination.hasMore });
          } catch (err) {
            return formatToolError(err);
          }
        },
      );
    };
  • src/index.ts:62-62 (registration)
    Registration call site: registerListTool(server, client) is invoked during server setup in the main entry point.
    registerListTool(server, client);
  • The listPushes method on ZephApiClient that makes the GET /pushes HTTP request with optional query params (limit, type). Returns PushListResponse.
    async listPushes(params?: { limit?: number; type?: string }): Promise<PushListResponse> {
      const query = new URLSearchParams();
      if (params?.limit) query.set('limit', String(params.limit));
      if (params?.type) query.set('type', params.type);
      const qs = query.toString();
      return this.request<PushListResponse>('GET', `/pushes${qs ? `?${qs}` : ''}`);
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds context about history and duplicate avoidance but does not disclose any additional behavioral traits like pagination or rate limits. It adds moderate value beyond 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 wasted words. The first sentence states the core action, and the second provides usage guidance. Highly efficient and front-loaded.

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 tool's simplicity and the presence of annotations, the description is adequate for most use cases. However, it lacks any mention of the output format or return value structure, which could help an agent understand what to expect. The parameter descriptions are complete in the schema, but the tool's overall description could be slightly more complete.

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?

Input schema has 100% description coverage for both parameters (limit and type). The tool description does not add any additional meaning or context for parameters beyond what the schema provides. Baseline score 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?

Description clearly states 'List recent push notifications' with a specific verb and resource. It also provides use cases (check history, avoid duplicates, reference) that distinguish it from sibling tools like zeph_broadcast or zeph_dismiss.

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?

Includes 'Use this to check notification history, avoid duplicates, or reference previous messages,' which gives clear context for when to use. It does not explicitly mention when not to use or name alternatives, but the provided sibling list implies other tools for different actions.

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