Skip to main content
Glama
1msg MCP

1msg MCP

Official
by 1msg

send_payment_request

Send a regional interactive payment request via the 1msg Chat API for IN, SG, or BR, using a phone number and optional message body.

Instructions

Send a regional payment request interactive message (beta scaffold). region must be IN, SG, or BR. Payload shape follows Meta regional payments docs; verify on stage before production use. Full regional builders are not implemented yet.

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": {
      "phone": "<phone>",
      "region": "<region>"
    },
    "name": "send_payment_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
phoneYes
actionNo
regionYes
interactiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose genuinely valuable context: this is a beta scaffold, the regional builders are unimplemented, and the payload shape is only documented externally. It does not say what the tool returns, whether the message is dispatched immediately, how failures surface, or that the send is irreversible.

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?

Three short sentences, front-loaded with the core action and immediately followed by the constraint and the caveat. Minor waste in restating the region enum that the schema already encodes, but overall tight.

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?

For a 5-parameter mutation tool with two untyped nested objects, no annotations, and no output schema, the definition leaves the most consequential parts unexplained. The beta disclaimer is helpful but does not substitute for describing the `action` and `interactive` payload structure or the return behavior.

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% across 5 parameters, so the description must compensate and largely does not. It explains `region` (which the schema already enforces via const enums) but says nothing about `phone`, `body`, or the opaque nested `action` and `interactive` objects, which are exactly the parameters an agent would get wrong.

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?

"Send a regional payment request interactive message" gives a specific verb plus a specific resource type, and the regional qualifier distinguishes it from generic senders such as send_message or send_button. It stops short of naming the closest alternatives (send_order_details, send_product) so an agent still has to infer which sender applies to a payment request.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description usefully constrains `region` to IN, SG, or BR and warns to verify on stage before production use, which functions as a deployment-condition guideline. However, it never says when to pick this tool over the many other send_* siblings, nor what the prerequisites are (e.g., a valid business account or an existing conversation).

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