Skip to main content
Glama
Sign In
Simplepush MCP Server

Simplepush MCP Server

Official
by simplepush
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get the pick on an earlier notification

get_notification_answer

Check if a notification has been answered by passing its notification_id. Returns the selected pick, pending if unanswered, or delivered when no input was requested.

Instructions

Check whether a notification sent with send_notification and an input has been answered. Pass the notification_id it returned. Returns the pick, pending if untouched, or delivered when the notification carried no input (nothing to answer).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "notification_id": "<notification_id>"
    },
    "name": "get_notification_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
notification_idYesThe notification_id returned by send_notification.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

The description discloses return states (pick, pending, delivered) but does not mention side effects or error behavior. As a read operation, it is implicitly safe, but transparency could be improved by explicitly stating it has no side effects.

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 concise and well-structured, with the purpose stated first and sufficient detail for the single parameter.

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?

The description covers the necessary context for a simple tool: how to obtain the parameter and what the return states mean. It could be slightly clearer about the 'delivered' state, but overall it is complete for the tool's complexity.

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

Parameters5/5

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

The description and schema fully explain the notification_id parameter, including its origin (returned by send_notification). This is unambiguous and complete.

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 tool's function: checking whether a notification sent via send_notification has been answered and retrieving the answer. It identifies the resource and action without ambiguity.

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 implies when to use it (after send_notification, passing the returned notification_id) and explains result states. It does not explicitly contrast with alternative tools, but the context is sufficient for appropriate usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools