Skip to main content
Glama
baskcart

W3 Ledger MCP Server

by baskcart

claim_sponsor_card

Claim a sponsor card to credit your DAH balance from the W3 Ledger MCP Server. Only ISSUED cards can be claimed using your public key and card verification details.

Instructions

Claim a sponsor card and credit the claimer's DAH balance. Only cards with status ISSUED can be claimed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
player_publickeyYesPublic key of the person claiming the card.
cardInfoYesSponsor card to claim (must include verification fields).

Implementation Reference

  • The handler for 'claim_sponsor_card' executes a POST request to the '/claim-sponsor-card' API endpoint using the RolledgeClient.
    case 'claim_sponsor_card': {
        const res = await client.post('/claim-sponsor-card', args);
        return toResult(res.data, !res.ok);
    }
  • The MCP tool definition and input schema for 'claim_sponsor_card', specifying required fields like player_publickey and cardInfo.
    {
        name: 'claim_sponsor_card',
        description:
            'Claim a sponsor card and credit the claimer\'s DAH balance. ' +
            'Only cards with status ISSUED can be claimed.',
        inputSchema: {
            type: 'object',
            properties: {
                player_publickey: {
                    type: 'string',
                    description: 'Public key of the person claiming the card.',
                },
                cardInfo: {
                    type: 'object',
                    description:
                        'Sponsor card to claim (must include verification fields).',
                    properties: {
                        card_id: { type: 'string', description: 'Unique sponsor card ID.' },
                        card_public_key: {
                            type: 'string',
                            description: 'Card\'s public key for verification.',
                        },
                        digital_signature: {
                            type: 'string',
                            description: 'Card\'s digital signature.',
                        },
                        message: { type: 'string', description: 'Sponsor message.' },
                        cardValue: { type: 'number', description: 'Card value.' },
                        sponsor_name: { type: 'string', description: 'Sponsor name.' },
                        status: {
                            type: 'string',
                            description: 'Must be ISSUED.',
                            enum: ['ISSUED'],
                        },
                    },
                    required: [
                        'card_id',
                        'card_public_key',
                        'digital_signature',
                        'message',
                        'cardValue',
                        'sponsor_name',
                        'status',
                    ],
                },
            },
            required: ['player_publickey', 'cardInfo'],
        },
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the mutation ('credit...balance') and validation constraint ('ISSUED' status), but omits idempotency guarantees, error scenarios, and whether claiming changes the card's state (e.g., consumes it).

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?

Two sentences with zero waste: the first states purpose and effect, the second states the validation constraint. Information is front-loaded and every sentence earns its place.

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

Completeness3/5

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

Given this is a financial mutation tool with no annotations or output schema, the description adequately covers the core operation and validation rule. However, gaps remain regarding error handling, return values, and post-claim card state.

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?

Schema coverage is 100%, establishing a baseline of 3. The description adds value by linking 'claimer' to 'player_publickey' and specifying the 'ISSUED' status constraint for 'cardInfo', though the schema already adequately documents both parameters.

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 uses specific verbs ('Claim', 'credit') and identifies the exact resource ('sponsor card') and effect ('credit the claimer's DAH balance'). It clearly distinguishes from sibling tool 'claim_gift_card' by specifying 'sponsor card'.

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

Usage Guidelines3/5

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

It provides a clear precondition constraint ('Only cards with status ISSUED can be claimed'), which implies when the tool will fail. However, it lacks explicit guidance on when to use this tool versus 'claim_gift_card' or other alternatives.

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