helius_get_assets_by_owner
Retrieve assets associated with a specific Solana wallet address using the MCP Helius server's Helius API integration. Specify the owner address, page, and limit parameters to fetch detailed asset information efficiently.
Instructions
Get assets owned by a specific address
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| owner | Yes | ||
| page | No |
Input Schema (JSON Schema)
{
"properties": {
"limit": {
"type": "number"
},
"owner": {
"type": "string"
},
"page": {
"type": "number"
}
},
"required": [
"owner"
],
"type": "object"
}
Implementation Reference
- src/handlers/helius.ts:372-385 (handler)The handler function that implements the core logic for the 'helius_get_assets_by_owner' tool by calling the Helius RPC method getAssetsByOwner with mapped parameters.export const getAssetsByOwnerHandler = async (input: { owner: string, page?: number, limit?: number }): Promise<ToolResultSchema> => { try { // Fix the parameter name mismatch const params = { ownerAddress: input.owner, // Change owner to ownerAddress page: input.page || 1, limit: input.limit || 10 }; const assets = await (helius as any as Helius).rpc.getAssetsByOwner(params); return createSuccessResponse(`Assets by owner: ${JSON.stringify(assets, null, 2)}`); } catch (error) { return createErrorResponse(`Error getting assets by owner: ${error instanceof Error ? error.message : String(error)}`); } }
- src/tools.ts:333-345 (schema)The tool schema definition including name, description, and inputSchema for validation.{ name: 'helius_get_assets_by_owner', description: 'Get assets owned by a specific address', inputSchema: { type: 'object', properties: { owner: { type: 'string' }, page: { type: 'number' }, limit: { type: 'number' } }, required: ['owner'] } },
- src/tools.ts:577-577 (registration)Registration of the handler function in the tools handlers dictionary."helius_get_assets_by_owner": helius.getAssetsByOwnerHandler,