Skip to main content
Glama
baskcart

W3 Ledger MCP Server

by baskcart

create_sponsor_card

Create a location-based sponsor card by debiting the sponsor's DAH balance with dual signatures, enabling users near the sponsor location to claim it.

Instructions

Create a location-based sponsor card by debiting the sponsor's DAH balance. Requires dual signatures. The card can be claimed by users near the sponsor location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sponsor_public_keyYesPublic key of the sponsor funding the card.
cardInfoYesSponsor card details.
sponsor_locationYesGPS coordinates where the card can be claimed.
signatureYesSponsor transaction signature (EVM personal_sign).
distributionSignatureYesDistribution account co-signature for dual signing.
timestampYesISO 8601 timestamp of the transaction.

Implementation Reference

  • The implementation of the tool 'create_sponsor_card' in the executeTool function, which sends a POST request to the '/sponsor-card' endpoint.
    case 'create_sponsor_card': {
        const res = await client.post('/sponsor-card', args);
        return toResult(res.data, !res.ok);
    }
  • The schema definition and registration for the 'create_sponsor_card' tool.
    {
        name: 'create_sponsor_card',
        description:
            'Create a location-based sponsor card by debiting the sponsor\'s DAH balance. ' +
            'Requires dual signatures. The card can be claimed by users near the sponsor location.',
        inputSchema: {
            type: 'object',
            properties: {
                sponsor_public_key: {
                    type: 'string',
                    description: 'Public key of the sponsor funding the card.',
                },
                cardInfo: {
                    type: 'object',
                    description: 'Sponsor card details.',
                    properties: {
                        sponsor_name: {
                            type: 'string',
                            description: 'Name of the sponsor (max 100 chars).',
                        },
                        message: {
                            type: 'string',
                            description: 'Sponsor message (max 500 chars).',
                        },
                        cardValue: {
                            type: 'number',
                            description: 'Value in DAH tokens (max 10,000).',
                            minimum: 0.01,
                            maximum: 10000,
                        },
                    },
                    required: ['sponsor_name', 'message', 'cardValue'],
                },
                sponsor_location: {
                    type: 'object',
                    description: 'GPS coordinates where the card can be claimed.',
                    properties: {
                        lat: {
                            type: 'number',
                            description: 'Latitude (-90 to 90).',
                            minimum: -90,
                            maximum: 90,
                        },
                        lng: {
                            type: 'number',
                            description: 'Longitude (-180 to 180).',
                            minimum: -180,
                            maximum: 180,
                        },
                    },
                    required: ['lat', 'lng'],
                },
                signature: {
                    type: 'string',
                    description: 'Sponsor transaction signature (EVM personal_sign).',
                },
                distributionSignature: {
                    type: 'string',
                    description: 'Distribution account co-signature for dual signing.',
                },
                timestamp: {
                    type: 'string',
                    description: 'ISO 8601 timestamp of the transaction.',
                },
            },
            required: [
                'sponsor_public_key',
                'cardInfo',
                'sponsor_location',
                'signature',
                'distributionSignature',
                'timestamp',
            ],
        },
        access: 'write',
    },
Behavior4/5

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

With no annotations provided, the description carries full burden and effectively discloses critical behavioral traits: dual signature requirement (security), DAH balance debit (financial impact), and location-proximity claiming mechanism. Minor gap in not describing failure modes or validation errors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly constructed sentences with zero waste. Front-loaded with action and cost (DAH debit), followed by critical requirement (dual signatures), then outcome (claiming mechanics). Every sentence earns its place.

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 6-parameter financial/crypto tool with nested objects and no output schema, the description adequately covers the core transaction model, security requirements, and claiming behavior. Could be improved by noting validation requirements or error conditions, but the essential complexity is addressed.

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?

While schema has 100% coverage, the description adds valuable semantic context not present in structured data: explicitly linking 'signature' and 'distributionSignature' as 'dual signatures' (workflow context), and explaining the DAH economic model that justifies the 'sponsor_public_key' parameter.

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?

Description uses specific verb 'Create' with clear resource 'location-based sponsor card'. It distinguishes from sibling 'create_gift_card' by specifying sponsor-specific mechanics: DAH balance debit, dual signatures, and location-based claiming.

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?

Provides clear context for when to use (sponsor funding location-based cards requiring dual signatures and DAH debit). While it doesn't explicitly name 'create_gift_card' as an alternative, the sponsor/DAH/location specificity makes the appropriate use case distinct.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/baskcart/w3ledger-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server