Skip to main content
Glama

Kariaa Agents

Request a payout

request_payout

Use when the person asks to cash out their Kariaa balance. Ask Kariaa to pay the whole balance. Methods: paypal, venmo, giftcard, crypto. An admin sends the money. One open request at a time, minimum 10.

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": {
      "method": "<method>"
    },
    "name": "request_payout"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
amountNoOmit, or pass the whole balance.
methodYespaypal, venmo, giftcard, or crypto
destinationNoMust match the destination saved on the profile.

Output Schema

NameRequiredDescriptionDefault
noteNoOptional note
amountNoAmount requested
methodNopaypal, venmo, giftcard, or crypto
statusNorequested
currencyNoCurrency
payout_idNoThe created payout request id
destinationNoWhere the payout will be sent
requested_atNoWhen requested

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not destructive, not idempotent), and the description adds genuinely new behavioral context: a human admin fulfills the payment, only one request may be open at a time, and there is a minimum of 10. It still leaves turnaround time and what happens if the balance is below the minimum unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger is correctly front-loaded and the sentence count is small, but 'Methods: paypal, venmo, giftcard, crypto' duplicates the enum already in the schema and burns space that could have carried the missing eligibility details. It reads as terse fragments rather than a structured definition.

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 annotations, a 75%-covered schema and an output schema, the description supplies the key operating context an agent needs to call this correctly. Gaps remain around the currency/units of the minimum and what the agent should tell a user who already has an open request.

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

Parameters3/5

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

Schema coverage is 75% and the amount and destination fields are already documented there, including the 'omit, or pass the whole balance' semantics the description echoes. The description adds no syntax or format detail beyond the enum list it repeats, so the schema still does the heavy lifting.

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?

States a specific verb and resource ('cash out their Kariaa balance', 'request a payout') so the agent knows exactly what operation is being invoked. Sibling tools are all upload/task/job related, so there is no real overlap to disambiguate against, which is why it stops short of a 5.

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?

'Use when the person asks to cash out their Kariaa balance' gives a clear trigger condition, and the definition adds real eligibility constraints (one open request at a time, minimum 10). It does not say what to do when the user is ineligible or already has an open request, so exclusions are missing.

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.