Skip to main content
Glama
Sign In
Agentic AQUA

Agentic AQUA

Official
by AquaWallet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wapupay_provision_account

Provision a WapuPay API key through a logged-in JAN3 account so WapuPay tools can run when no key is configured; it stores the key locally and skips setup if one already exists.

Instructions

Provision a WapuPay API key via the user's JAN3 account so the other WapuPay tools work. Use when the user wants WapuPay but has no API key set. Requires a prior JAN3 login for the email (either flow: jan3_login then jan3_verify, or jan3_login_start then jan3_login_complete); calls the AQUA backend with that session, then stores the returned key locally (0o600) for all wapupay_* tools — the raw key is never returned, only a masked preview. The AQUA backend issues a fresh key on every call and invalidates the previous one (no grace period), so this only calls the backend when no key is configured yet: if one already exists (env var or stored) it is a no-op (already_configured=true) and never invalidates a working key.

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": {
      "email": "<email>"
    },
    "name": "wapupay_provision_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesLogged-in JAN3 account whose session authorizes the call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Given no annotations, the description fully discloses behavior: it calls the AQUA backend, stores the key locally (0o600), never returns the raw key, only a masked preview. It also explains idempotency (no-op if key exists) and the backend's key invalidation policy. This provides comprehensive behavioral understanding.

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?

The description is comprehensive and front-loaded with the purpose. It is somewhat lengthy but every sentence adds value, covering prerequisites, behavior, and edge cases. It could be slightly more structured (e.g., bullet points), but remains clear and efficient.

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?

Given the complexity (setup tool with prerequisites, idempotency, security) and no output schema, the description covers all essential aspects: what it does, when to use, prerequisites, behavioral details, and return format (masked preview). It is complete enough for an agent to use correctly.

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?

The schema covers the email parameter (format email, description about session authorization). The description adds context that the email must be from a completed JAN3 login flow, which is valuable beyond the schema. This enhances the agent's understanding of the parameter's role.

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?

The description clearly states the verb 'Provision' and the resource 'WapuPay API key', and distinguishes from sibling tools by noting that this is a prerequisite for other wapupay tools. It also explains the link to the user's JAN3 account.

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 explicitly says when to use ('when the user wants WapuPay but has no API key set') and details prerequisites (prior JAN3 login). It also indicates that calling when already configured is a no-op, implying it's unnecessary. However, it does not explicitly list alternative tools or when not to use beyond the no-op case.

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

Deploy Server

Other Tools