Skip to main content
Glama
hackle-io

hackle-mcp

Official
by hackle-io

push-message-detail

Retrieve detailed information for a specific push message using the pushMessageId to analyze and manage targeted communication campaigns effectively.

Instructions

Retrieves detailed information for a specific push message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pushMessageIdYes

Implementation Reference

  • The handler function for the 'push-message-detail' tool. It takes pushMessageId, calls WebClient.get to fetch the details from the API, stringifies the JSON response, and returns it as text content.
    async ({ pushMessageId }) => {
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(await WebClient.get(`/api/v1/push-messages/${pushMessageId}`)),
          },
        ],
      };
    },
  • Input schema for the tool, requiring a numeric pushMessageId parameter.
    {
      pushMessageId: z.number(),
    },
  • src/index.ts:143-159 (registration)
    Registration of the 'push-message-detail' tool on the MCP server using server.tool, including name, description, schema, and inline handler.
    server.tool(
      'push-message-detail',
      'Retrieves detailed information for a specific push message.',
      {
        pushMessageId: z.number(),
      },
      async ({ pushMessageId }) => {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(await WebClient.get(`/api/v1/push-messages/${pushMessageId}`)),
            },
          ],
        };
      },
    );
  • WebClient.get method called by the handler to perform the HTTP GET request to '/api/v1/push-messages/{pushMessageId}'.
    public static async get<T = unknown>(path: string, options?: Omit<RequestInit, 'method'>): Promise<T> {
      return this.request<T>('GET', path, options);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states this is a retrieval operation, implying read-only behavior, but does not disclose other traits like error handling, authentication needs, rate limits, or response format. This leaves significant gaps for a tool with no annotation coverage.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It does not cover behavioral aspects, parameter details, or return values, leaving the agent with insufficient information to use the tool effectively beyond its basic purpose.

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

Parameters2/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 compensate. It mentions 'specific push message' but does not explain the 'pushMessageId' parameter's meaning, format, or how to obtain it. This adds minimal value beyond the schema's structural definition.

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 ('Retrieves') and resource ('detailed information for a specific push message'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'push-message-list', which likely lists multiple messages rather than retrieving details for one.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as needing a specific pushMessageId, or compare it to siblings like 'push-message-list' for broader queries.

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

Related 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/hackle-io/hackle-mcp'

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