Skip to main content
Glama
Sign In
MNotify MCP Server

MNotify MCP Server

by Nanayeb34
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

periodic_sms_delivery_report

Retrieve SMS campaign delivery reports for a specified date range. Input start and end dates to get delivery status updates.

Instructions

Get delivery reports for campaigns within a date range (YYYY-MM-DD).

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": {
      "from_date": "<from_date>",
      "to_date": "<to_date>"
    },
    "name": "periodic_sms_delivery_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_dateYes
from_dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are present, so the description carries full burden for behavioral disclosure. It merely states the function without detailing traits like permission requirements, rate limits, or what 'campaigns' means, leaving gaps.

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 concise sentence with no extraneous words. It is front-loaded with the verb 'Get'. However, it could include more detail without becoming verbose.

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 not required to detail return values. However, it does not explain what constitutes a 'campaign' or how this tool relates to siblings, leaving some context gaps. It is adequate for a simple retrieval tool.

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%, but the description adds only a date format hint ('YYYY-MM-DD') without explaining semantics like inclusivity, timezone, or valid range. This minimally compensates for the lacking schema descriptions.

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 action ('Get'), resource ('delivery reports for campaigns'), and scope ('within a date range'). It differentiates from sibling tools like 'sms_delivery_report' and 'specific_sms_delivery_report' by specifying the parameterization.

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 guidance is provided on when to use this tool over alternatives. Sibling tools exist for similar purposes, but the description does not explain the differences or when not to use this tool.

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