Skip to main content
Glama
Sign In
MNotify MCP Server

MNotify MCP Server

by Nanayeb34
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

specific_sms_delivery_report

Retrieve delivery status for a specific message in an SMS campaign using the campaign ID.

Instructions

Get the delivery status for a specific message within a campaign by campaign_id.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "specific_sms_delivery_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

No annotations exist, so description must carry burden. It indicates a read operation ('Get the delivery status'), which is straightforward. However, no additional behavioral details (e.g., no side effects, rate limits) are provided, leaving basic transparency.

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 sentence with no extraneous text. Every word adds value, and it is appropriately concise.

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?

Although an output schema exists (so return values are not required in description), the description does not clarify what 'specific message' means. Given only campaign_id is in schema, it is ambiguous whether the tool targets a specific message implicitly or if additional info is needed. This lack of completeness harms usability for a simple 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%, yet the description only restates the parameter campaign_id without explaining its meaning or format. It fails to compensate for missing schema descriptions, leaving the agent without guidance on how to provide valid input.

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 tool retrieves delivery status for a specific message within a campaign, using campaign_id. It distinguishes from sibling tools that may retrieve reports for all messages or periodically, though it could be clearer about what 'specific message' means given only campaign_id is required.

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 versus alternatives like periodic_sms_delivery_report or sms_delivery_report, nor does it mention prerequisites or context.

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