Skip to main content
Glama

Taifoon coordination layer

Get a key

taifoon_register

Creates a tenant with a free key (tfr_free_…, shown once), or a free RPC key with its gateway URL and allowance. For reading an existing account use taifoon_account. Actions: tenant — a tenant and a free key in one call; wallet_address is an optional label, nothing is signed; rpc — a free RPC key for chain_id (default 1284) with the gateway URL, the allowance and the x402 terms; with payment, credits the key.

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": "taifoon_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
txNoa settled subscribe payment whose credit was not written (actions: rpc)
planNoa 30-day plan instead of a balance: builder 99 USDC (110 of use), team 199 (240), protocol 299 (380); paid and credited the same way (actions: rpc)
usdcNousdc (actions: rpc)
actionNowhat to do (default tenant): tenant | rpctenant
api_keyNoapi key (actions: rpc)
paymentNothe x402 PAYMENT-SIGNATURE header value (base64) for the accepts a previous call returned (actions: rpc)
agent_idNooptional ERC-8004 id "<chain>:<id>" (a label on your tenant) (actions: tenant)
chain_idNothe chain you want to read (default 1284 Moonbeam); the answer names its gateway URL (actions: rpc)
pay_chain_idNothe pay chain of the transfer quote; absent = Base (actions: rpc)
wallet_addressNooptional: a 0x wallet address to label your tenant with (nothing is signed; leave it out) (actions: tenant)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / plan
      Added value: +{
      +  "description": "a 30-day plan instead of a balance: builder 99 USDC (110 of use), team 199 (240), protocol 299 (380); paid and credited the same way (actions: rpc)",
      +  "enum": [
      +    "builder",
      +    "team",
      +    "protocol"
      +  ],
      +  "type": "string"
      +}
  2. Changed10 schema fields changed
    • addedInput schema / properties / action
      Added value: +{
      +  "default": "tenant",
      +  "description": "what to do (default tenant): tenant | rpc",
      +  "enum": [
      +    "tenant",
      +    "rpc"
      +  ],
      +  "examples": [
      +    "tenant"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / agent_id / description
      Previous value: -"optional ERC-8004 id \"<chain>:<id>\" (a label on your tenant)"New value: +"optional ERC-8004 id \"<chain>:<id>\" (a label on your tenant) (actions: tenant)"
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "api key (actions: rpc)",
      +  "type": "string"
      +}
    • addedInput schema / properties / chain_id
      Added value: +{
      +  "description": "the chain you want to read (default 1284 Moonbeam); the answer names its gateway URL (actions: rpc)",
      +  "type": "integer"
      +}
    • addedInput schema / properties / pay_chain_id
      Added value: +{
      +  "description": "the pay chain of the transfer quote; absent = Base (actions: rpc)",
      +  "enum": [
      +    8453,
      +    42161,
      +    5042,
      +    143,
      +    4663
      +  ],
      +  "type": "integer"
      +}
    • addedInput schema / properties / payment
      Added value: +{
      +  "description": "the x402 PAYMENT-SIGNATURE header value (base64) for the accepts a previous call returned (actions: rpc)",
      +  "type": "string"
      +}
    • addedInput schema / properties / tx
      Added value: +{
      +  "description": "a settled subscribe payment whose credit was not written (actions: rpc)",
      +  "type": "string"
      +}
    • addedInput schema / properties / usdc
      Added value: +{
      +  "description": "usdc (actions: rpc)",
      +  "maximum": 500,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / wallet_address / description
      Previous value: -"optional: a 0x wallet address to label your tenant with (nothing is signed; leave it out)"New value: +"optional: a 0x wallet address to label your tenant with (nothing is signed; leave it out) (actions: tenant)"
    • removedInput schema / required
      Removed value: -[]
  3. Changed2 schema fields changed
    • changedInput schema / properties / wallet_address / description
      Previous value: -"0x wallet address that will own the key"New value: +"optional: a 0x wallet address to label your tenant with (nothing is signed; leave it out)"
    • changedInput schema / required
      Previous value: -[
      -  "wallet_address"
      -]New value: +[]
  4. Changed1 schema field changed
    • addedInput schema / properties / agent_id
      Added value: +{
      +  "description": "optional ERC-8004 id \"<chain>:<id>\" (a label on your tenant)",
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and non-idempotent, and the description adds genuinely new behavioral facts: the key is shown only once, wallet_address is a mere label and nothing is signed, and a payment credits the key. It omits failure modes and what happens if the key is lost, but the added context is substantive.

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?

Purpose and the sibling alternative are front-loaded in the first two sentences, then the action breakdown follows. The middle sentence is dense and heavily punctuated, but nearly every clause carries a distinct fact.

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 10-parameter, dual-mode, zero-required-parameter tool with no output schema, the description covers both modes, the payment/credit flow, and the one-time key disclosure. It does not describe the returned shape for the tenant action or error behavior, which keeps it from a 5.

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 3 is the baseline, but the description goes further by grouping parameters by action (tenant vs rpc) and clarifying intent — chain_id defaults to 1284 Moonbeam, wallet_address is an optional label with no signing, payment is the x402 PAYMENT-SIGNATURE for a returned accepts. That cross-parameter routing is value beyond the schema.

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 specific verbs and resources: creates a tenant with a free key (tfr_free_…, shown once) or a free RPC key with gateway URL and allowance. It also names the sibling it is not ('For reading an existing account use taifoon_account'), so the agent can distinguish it from taifoon_account without opening either 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?

Explicitly routes the 'read an existing account' case to taifoon_account and enumerates the two modes (tenant, rpc) with what each does and which params belong to each. It lacks explicit when-not guidance for edge cases (e.g., when to use rpc with payment versus taifoon_buy), so it falls short of full alternative mapping.

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