Feature: Add Algorand ARC-4 ABI support for MCP tool generation

[corvid-agent]

Summary

UCAI currently supports EVM chains (Ethereum, Polygon, Arbitrum, Base) for generating MCP tools from smart contract ABIs. I'd like to propose adding Algorand support.

Algorand ABI Format

Algorand uses the ARC-4 ABI specification, which defines a JSON-based ABI format similar to EVM ABIs but with Algorand-specific types. Additionally, ARC-32 and ARC-56 provide application specification formats that include ABI methods, state schema, and source info.

Proposed Implementation

1. ARC-4 ABI Parser: Parse Algorand ABI JSON to extract method signatures, argument types, and return types
2. Type Mapping: Map Algorand ABI types (uint64, byte[], address, application, asset, etc.) to MCP tool parameter schemas
3. Transaction Builder: Generate Algorand application call transactions from tool inputs using the js-algorand-sdk
4. Network Support: Support MainNet, TestNet, BetaNet via algod/indexer endpoints
5. Simulation: Use Algorand's simulate endpoint for dry-run execution before signing

Example

Given an ARC-4 ABI:

{
  "name": "MyContract",
  "methods": [
    {
      "name": "transfer",
      "args": [
        {"name": "receiver", "type": "address"},
        {"name": "amount", "type": "uint64"}
      ],
      "returns": {"type": "bool"}
    }
  ]
}

This would generate an MCP tool mycontract_transfer with params receiver (string) and amount (number).

Ecosystem Context

Algorand has a growing AI/MCP ecosystem including:

• algorand-remote-mcp — comprehensive MCP server
• vibekit — AI development toolkit
• algorand-agent-skills — official agent tools

I'd be happy to help implement this if you're interested in adding Algorand support!