Skip to main content
Glama

kairos-signal

by io.github.OV3RK177
OverviewDiscussionsAdmin

Add credits (card checkout link or USDC quote)

topup_credits

Add credits. Card (one call): {"method": "stripe", "amount": N} where N is $20 or $99 — returns a Stripe checkout_url already bound to your api_key, and credits post automatically once Stripe confirms payment at $1 = 1 credit. No human step and no wallet needed. USDC on Base ({"method": "usdc"}) is also accepted but requires more work: verify your sender first via POST /v1/credits/crypto/challenge and /verify with X-API-Key, sign the returned challenge with your own EOA, then pass the verified from_address and send only after a successful quote — credit requires finalized Base evidence. Instructions: https://kairossignal.com/docs/crypto.html

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesAmount in USD to add. Fixed packs only: 20 or 99. Any other value returns the available packs instead of a link.
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: your EOA address already verified to this API account through the wallet challenge flow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"Amount in USD to add"New value: +"Amount in USD to add. Fixed packs only: 20 or 99. Any other value returns the available packs instead of a link."
    • addedInput schema / properties / amount / enum
      Added value: +[
+  20,
+  99
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / from_address / description
      Previous value: -"Required for USDC: the exact EVM wallet address you will send from."New value: +"Required for USDC: your EOA address already verified to this API account through the wallet challenge flow."
  3. 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."
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the generic profile (openWorldHint=true, non-idempotent, non-destructive). The description goes well beyond that: credits post automatically once Stripe confirms, the checkout_url is bound to the caller's api_key, $1 = 1 credit, USDC credit requires finalized Base evidence, and the legacy tx_hash is called out as non-substituting.

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?

Front-loaded with 'Add credits.' and every clause carries information (pricing, flow steps, doc link). The inline JSON fragments slightly interrupt readability, but nothing is padding.

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?

For a multi-step payment tool with no output schema, the description covers both flows, the return of checkout_url for card, and the preconditions for USDC, plus an external docs pointer. It omits what a USDC quote returns and how errors surface, which leaves a small gap.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it fixes amount to the $20/$99 packs with the $1=1 credit rate and explains that from_address must be an already-verified EOA. It does not document the quote/challenge response shape, which the schema also omits.

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+resource ('Add credits') and immediately enumerates the two supported funding paths (Stripe card, USDC on Base). This cleanly separates it from siblings like check_balance (read) and purchase_data (dataset purchase), so an agent can route without inspecting the schema.

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 contrasts the two methods explicitly: card is 'one call' with 'no human step and no wallet needed', while USDC 'requires more work' with a spelled-out verify/sign/quote sequence. It gives clear selection context but states no hard exclusions or failure/retry conditions.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources