Skip to main content
Glama

kairos-signal

by io.github.OV3RK177
OverviewDiscussionsAdmin

topup_credits

Create a USDC top-up intent before transferring funds: provide from_address and follow the returned transfer instructions. Alternatively, get a Stripe checkout link for your human operator to complete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount in USD to add
methodYesPayment method
api_keyYesYour API key
tx_hashNoLegacy optional field; a transaction hash does not replace from_address or verify payment.
from_addressNoRequired for USDC: the exact EVM wallet address you will send from.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / allOf
      Added value: +[
+  {
+    "if": {
+      "properties": {
+        "method": {
+          "const": "usdc"
+        }
+      },
+      "required": [
+        "method"
+      ]
+    },
+    "then": {
+      "required": [
+        "from_address"
+      ]
+    }
+  }
+]
    • addedInput schema / properties / from_address
      Added value: +{
+  "description": "Required for USDC: the exact EVM wallet address you will send from.",
+  "pattern": "^0x[0-9a-fA-F]{40}$",
+  "type": "string"
+}
    • changedInput schema / properties / tx_hash / description
      Previous value: -"USDC transaction hash (for crypto payments)"New value: +"Legacy optional field; a transaction hash does not replace from_address or verify payment."
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It usefully discloses that the tool only creates an intent and returns transfer instructions rather than executing the transfer, and that the Stripe path requires a human operator. However, it does not mention side effects such as whether the intent expires, whether repeated calls create multiple intents, or any rate limits.

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 two sentences with the main USDC flow front-loaded and the Stripe alternative concisely appended. Every sentence earns its place and there is no filler.

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?

There is no output schema, but the description covers the return concepts for both branches: transfer instructions and a Stripe checkout link. Given the fully documented parameters and simple branching logic, this is adequate, though the lifecycle of the top-up intent could be slightly clearer.

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?

Input schema coverage is 100%, so the baseline is 3. The description reinforces that from_address is needed for USDC and that there are two methods, but it adds no parameter-level detail beyond what the schema already states.

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?

The description clearly identifies the tool as creating a USDC top-up intent or a Stripe checkout link, with specific actions and resources. It is distinct from siblings like check_balance and purchase_data, though it does not explicitly contrast itself with them.

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?

The description gives clear context: use the USDC path before transferring funds, and use Stripe when a human operator should complete checkout. It does not discuss exclusions or alternative sibling tools, but the two internal modes are well differentiated.

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

All kairos-signal 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