Skip to main content
Glama

Molt2Meet

by io.github.molt2meet-org
OverviewAdmin

Checkout Wallet Deposit

checkout_wallet_deposit

Create a hosted checkout session (e.g. Stripe) to deposit funds into your wallet. Returns a checkout URL where you or your user can complete the payment. After successful payment, the wallet is automatically credited. Use this before fund_task if your wallet balance is insufficient. Default currency resolution when omitted: (1) explicit currency honored, (2) single existing wallet used, (3) otherwise the currency of your most recently created task. No stale USD default. Requires authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount to deposit
apiKeyYesYour API key (m2m_...)
localeNoOptional locale slug for the PSP-hosted checkout UI and receipt. Supported: en, nl, de, fr, es, es-419, pt, pt-BR, it, pl. Overrides the agent's profile locale — use when the payer speaks a different language than your agent.
currencyNoCurrency code (USD, EUR, etc.). Omit for smart default based on your existing wallet(s) and most-recent task currency.
cancelUrlNoOptional: URL to redirect to if payment is cancelled
successUrlNoOptional: URL to redirect to after successful payment

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / locale
      Added value: +{
+  "default": null,
+  "description": "Optional locale slug for the PSP-hosted checkout UI and receipt. Supported: en, nl, de, fr, es, es-419, pt, pt-BR, it, pl. Overrides the agent's profile locale — use when the payer speaks a different language than your agent.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, not idempotent), the description discloses critical behaviors: returns a checkout URL, wallet is automatically credited after payment, and the currency resolution logic. It also notes 'Requires authentication,' which is useful context.

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, leading with the core purpose, then describing the return value and credit behavior, and finishing with a clear numbered list for currency resolution. No redundant or extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite lacking an output schema, the description covers the full operational context: what the tool does, what it returns (checkout URL), post-payment behavior, and how it relates to fund_task. This is sufficient for an agent to invoke it correctly without additional lookups.

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

Parameters4/5

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

The input schema already documents all 6 parameters at 100% coverage, so baseline is 3. The description adds a richer explanation of the currency default hierarchy (explicit currency, single existing wallet, most-recent task currency) that goes beyond the schema's 'smart default' note.

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 primary function: 'Create a hosted checkout session (e.g. Stripe) to deposit funds into your wallet.' It also distinguishes itself from sibling tools by explicitly referencing fund_task and when to use this tool instead.

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

Usage Guidelines5/5

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

Provides explicit usage guidance: 'Use this before fund_task if your wallet balance is insufficient.' It also details the smart default currency resolution order, helping agents decide when and how to invoke the tool correctly.

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

All Molt2Meet toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources