Skip to main content
Glama

MonoEsim — Travel Connectivity for AI Agents

Request a commission payout

request_payout
Idempotent

Ask MonoEsim to pay out your available commission (requires an active affiliate key, available balance at or above the minimum and the owner's completed payout setup). Creates at most one open request; MonoEsim then issues a credit note and transfers the money to the payout details the owner saved. You can never set or change payout details.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "request_payout"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare idempotentHint=true, readOnlyHint=false, and destructiveHint=false; the description goes well beyond that by explaining that at most one open request is created, that MonoEsim then issues a credit note and transfers funds to previously saved payout details, and that payout details can never be set or changed here. That is meaningful side-effect disclosure for a mutation tool.

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?

Two sentences, both front-loaded: prerequisites come first, then the downstream behavior. Every clause carries information, including the explicit scope limit on payout details.

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

Completeness4/5

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

With zero parameters and no output schema, the description supplies what an agent needs: preconditions, single-open-request semantics, and the resulting credit note and transfer. It stops short of describing failure behavior when preconditions are unmet or how to check balance first, which would round it out.

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 tool takes no parameters, so per the baseline this scores 4; the schema is empty and there is nothing further to disambiguate. The description correctly makes no attempt to describe nonexistent inputs.

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?

States a specific verb and resource ('Ask MonoEsim to pay out your available commission') and scopes it to a particular object (available affiliate commission). It is clearly distinct from sibling tools like get_affiliate, list_affiliate_sales, and list_destinations, which merely read or manage related data.

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

Usage Guidelines4/5

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

Gives explicit preconditions for calling: active affiliate key, balance at or above the minimum, and a completed payout setup by the owner. It does not name alternative tools (there appears to be no sibling that performs a payout), so the only gap is that it doesn't suggest how to verify those preconditions first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources