Skip to main content
Glama

Buy a 7-day pass

buy_pass
Read-onlyIdempotent

Builds the unsigned Base Mainnet transactions that buy a 7-day pass (5 USDC) for a wallet: a USDC approve, only if its allowance is below 5 USDC, then paySubscription() on the escrow contract. Use it when check_pass shows no active pass. Calling it is free and changes nothing: the wallet signs and sends the returned transactions itself (gas in ETH on Base); AgentSLA holds no keys and moves no funds. Buying while a pass is active extends it by 7 days from its current expiry. Returns the ordered transactions (to, data, value, chainId) and warnings such as an insufficient USDC balance.

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": {
      "walletAddress": "<walletAddress>"
    },
    "name": "buy_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletAddressYesBase Mainnet wallet that will sign, pay for and own the pass, e.g. "0x1234...abcd".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / walletAddress / description
      Previous value: -"Base Mainnet wallet (0x...) that will sign, pay and own the pass"New value: +"Base Mainnet wallet that will sign, pay for and own the pass, e.g. \"0x1234...abcd\"."
    • addedInput schema / properties / walletAddress / pattern
      Added value: +"^0x[0-9a-fA-F]{40}$"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial context beyond the readOnlyHint/idempotentHint/openWorldHint annotations: the call is free, mutates nothing, the wallet signs and sends, gas is ETH on Base, and AgentSLA holds no keys or funds. It also discloses the conditional approve on allowance < 5 USDC and the returned warnings. Consistent with readOnlyHint=true since it only builds unsigned payloads.

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-loads the core action and the two composed transactions, then layers on the safety note, extension semantics and return shape — no filler sentences. Slightly dense with parentheticals and multi-clause sentences, but each clause carries distinct information.

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

Completeness5/5

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

Despite having no output schema, the description names the returned fields (to, data, value, chainId) plus warnings such as insufficient USDC balance, and explains the gas/fee model and key custody. Nothing an agent needs to call and interpret this tool is missing.

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?

Only one parameter at 100% schema description coverage, so the schema already carries its meaning, including the address pattern and the sign/pay/own role. The description reiterates rather than adding new semantics, which is adequate but not additive.

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 ("Builds the unsigned Base Mainnet transactions that buy a 7-day pass") and enumerates the exact calls composed (USDC approve, then paySubscription() on the escrow contract). A reader can distinguish it from check_pass and the escrow siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit routing condition: "Use it when check_pass shows no active pass," naming the sibling that gates this tool. It also covers the non-obvious edge case of buying while a pass is active (extends from current expiry), so the agent knows the outcome rather than guessing.

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