Loading ToolBench
MCP server for the Meser10 email & SMS platform. Tools are generated from the live WSDL, so every API capability is covered by construction.
Critical failure: ALL 33 tools have empty input schemas (additionalProperties: false, no properties defined). This is a hard scoring rule violation, schema score must be 0 for tools with no input schema. Descriptions are present but generic and lack parameter guidance. No parameter descriptions exist anywhere. Tools combine multiple concerns (e.g., 'send_transactional_message' vs 'send_transactional_message_with_attachments' are near-duplicates). Naming is reasonable (verb_noun pattern), but without schemas and parameter docs, LLMs cannot safely invoke these tools. The server exposes 33 tools but provides zero actionable input guidance.
Calls ChangeContactEMail on the Meser10 platform. Modifies data in the account. Does not deliver anything to a recipient. SOAP operation: ChangeContactEMail.
Calls ChangeContactPhone on the Meser10 platform. Modifies data in the account. Does not deliver anything to a recipient. SOAP operation: ChangeContactPhone.
Calls ChangeContactStatusEx on the Meser10 platform. Modifies data in the account. Does not deliver anything to a recipient. SOAP operation: ChangeContactStatusEx.
Calls CreateAndSendEMail on the Meser10 platform. DELIVERS MESSAGES TO REAL RECIPIENTS and consumes account credit. Not reversible. SOAP operation: CreateAndSendEMail.
Calls CreateAndSendEMailCampaignWithAttachments on the Meser10 platform. DELIVERS MESSAGES TO REAL RECIPIENTS and consumes account credit. Not reversible. SOAP operation: CreateAndSendEMailCampaignWithAttachments.
ALL 33 tools have empty input schemas: {"type":"object","properties":{},"additionalProperties":false}. No parameters are defined, making it impossible for LLMs to know what inputs each tool accepts. Hard scoring rule: schema score = 0 for tools with no input schema.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | 2026-07-28+ | v2 |
Calls CreateAndSendSMSCampaignEx2 on the Meser10 platform. DELIVERS MESSAGES TO REAL RECIPIENTS and consumes account credit. Not reversible. SOAP operation: CreateAndSendSMSCampaignEx2.
Add one contact. Takes a list name, not a list id. Modifies data in the account. Does not deliver anything to a recipient. SOAP operation: CreateContact.
Calls AddGroup on the Meser10 platform. Modifies data in the account. Does not deliver anything to a recipient. SOAP operation: AddGroup.
Calls CreateUser on the Meser10 platform. Modifies data in the account. Does not deliver anything to a recipient. SOAP operation: CreateUser.
Calls DeleteContact on the Meser10 platform. PERMANENTLY REMOVES DATA. Not reversible. SOAP operation: DeleteContact.
Calls DeleteContacts on the Meser10 platform. PERMANENTLY REMOVES DATA. Not reversible. SOAP operation: DeleteContacts.
Calls DeleteGroup on the Meser10 platform. PERMANENTLY REMOVES DATA. Not reversible. SOAP operation: DeleteGroup.
Calls GetCampaign on the Meser10 platform. Read-only. SOAP operation: GetCampaign.
Per-recipient outcome for one campaign. Read-only. SOAP operation: GetCampaignResultDetails.
Calls GetCampaignLinkClicks on the Meser10 platform. Read-only. SOAP operation: GetCampaignLinkClicks.
Calls GetCampaignLinkClicksBetweenDates on the Meser10 platform. Read-only. SOAP operation: GetCampaignLinkClicksBetweenDates.
Calls GetCampaignResultsBetweenDates on the Meser10 platform. Read-only. SOAP operation: GetCampaignResultsBetweenDates.
Totals for one campaign: sent, opened, clicked, bounced. Read-only. SOAP operation: GetCampaignResultSummary.
Calls GetCouponStatus on the Meser10 platform. Read-only. SOAP operation: GetCouponStatus.
Calls GetGroups on the Meser10 platform. Read-only. SOAP operation: GetGroups.
How much sending quota the account has left. Check before a large campaign. Read-only. SOAP operation: GetUserSendLimitsInfo.
Calls GetSingleMessagesResultsBetweenDatesEx on the Meser10 platform. Read-only. SOAP operation: GetSingleMessagesResultsBetweenDatesEx.
Calls GetSingleMessagesResultsByIds on the Meser10 platform. Read-only. SOAP operation: GetSingleMessagesResultsByIds.
Addresses that hard-bounced. Feed these back into your own suppression list. Read-only. SOAP operation: GetBouncedAddresses.
Calls GetCampaignsBasicInfo on the Meser10 platform. Read-only. SOAP operation: GetCampaignsBasicInfo.
List the mailing lists on the account, with their ids. Start here - most other calls take a group. Read-only. SOAP operation: GetGroupsList.
Addresses that asked to be removed. Never re-add these. Read-only. SOAP operation: GetRemovedEMailAddresses.
Calls RemoveContactFromGroup on the Meser10 platform. PERMANENTLY REMOVES DATA. Not reversible. SOAP operation: RemoveContactFromGroup.
Calls RemoveContactFromList on the Meser10 platform. PERMANENTLY REMOVES DATA. Not reversible. SOAP operation: RemoveContactFromList.
Send one SMS to one number. DELIVERS MESSAGES TO REAL RECIPIENTS and consumes account credit. Not reversible. SOAP operation: SendSingleSmsMessage.
Send one transactional email or SMS to one recipient. DELIVERS MESSAGES TO REAL RECIPIENTS and consumes account credit. Not reversible. SOAP operation: SendSingleMessageEx2.
Calls SendSingleMessageWithAttachments on the Meser10 platform. DELIVERS MESSAGES TO REAL RECIPIENTS and consumes account credit. Not reversible. SOAP operation: SendSingleMessageWithAttachments.
Check that the configured API key works. Costs nothing and sends nothing. Read-only. SOAP operation: LoginUser.
No parameter descriptions exist. LLMs cannot infer what 'group_id', 'campaign_id', 'recipient_email', or other parameters mean without explicit guidance. Hard scoring rule: description score ≤ 20 when parameter docs are missing.
Multiple tools combine two concerns: 'send_transactional_message' vs 'send_transactional_message_with_attachments', 'create_and_send_sms_campaign' vs 'create_and_send_email_campaign'. These should be split into separate tools (create_campaign + send_campaign) so agents can compose them independently.
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., campaign_id, contact_id) without knowing what each tool returns.
No error handling guidance. Destructive tools (delete_contact, delete_group) and irreversible tools (send_sms, send_transactional_message) lack confirmation steps or recovery instructions. Agents cannot know whether to retry, ask the user, or abort.