Skip to main content
Glama
pushpad

Pushpad MCP

Official
by pushpad

senders_get

Fetch details for a specific sender using its sender ID. View sender information to manage push notification settings.

Instructions

To show information about an individual sender, send a GET request to /senders/SENDER_ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sender_idYesThe ID of a sender.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoA unique identifier for each sender. This is automatically generated upon sender creation.
nameNoThe human-readable name set for the sender.
created_atNoA time value given in ISO 8601 format. It represents when the sender was created.
vapid_public_keyNoThe VAPID public key associated to the subscriptions. This is automatically generated upon sender creation. You can optionally provide it if you want to import your existing key.
vapid_private_keyNoThe VAPID private key used to sign notifications. This is automatically generated upon sender creation. You can optionally provide it if you want to import your existing key.
Behavior2/5

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

With no annotations, the description must carry the burden of behavioral disclosure. It only states the HTTP method and endpoint, without explaining idempotency, error handling, or what happens if the sender_id is invalid. This is insufficient for a mutationless tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently conveys the action. It is front-loaded and avoids unnecessary words, but it lacks structure and additional helpful context.

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 presence of an output schema, the description is minimally adequate for a simple retrieval tool. However, it does not provide context about the data structure or error scenarios, so it feels incomplete.

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?

The input schema already describes the sender_id parameter fully (100% coverage). The description adds no additional meaning beyond referencing the ID in the URL path, so it does not improve parameter understanding.

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 states 'show information about an individual sender' and specifies the HTTP GET method and endpoint, making the purpose clear. However, it does not explicitly differentiate from senders_list, which lists all senders.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives like senders_list, nor does it mention any prerequisites or context.

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/pushpad/pushpad-mcp'

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