azeth_update_service
Update service metadata in the trust registry to modify endpoints, descriptions, capabilities, or other attributes after initial registration.
Instructions
Update metadata for your registered service on the trust registry.
Use this when: You need to change your service endpoint, description, capabilities, or other metadata after initial registration with azeth_publish_service.
Supported metadata keys: "endpoint", "description", "capabilities", "name", "entityType", "pricing". For capabilities, provide a JSON array string (e.g., '["translation", "nlp"]').
Note: Catalogs are off-chain and served from your endpoint. Update your catalog by updating the response at your endpoint, not via this tool.
Returns: Confirmation with transaction hash.
Note: Your account must already be registered on the trust registry. This requires a transaction (gas cost). Only the account owner can update metadata.
Example: { "key": "endpoint", "value": "https://api.example.com/v2" }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | Target chain. Defaults to AZETH_CHAIN env var or "baseSepolia". Accepts "base", "baseSepolia", "ethereumSepolia", "ethereum" (and aliases like "base-sepolia", "eth-sepolia", "sepolia", "eth", "mainnet"). | |
| key | Yes | Metadata key to update. | |
| value | Yes | New value. For "capabilities", provide a JSON array string like '["translation", "nlp"]'. |
Implementation Reference
- src/tools/registry.ts:600-650 (handler)Tool registration and handler implementation for azeth_update_service. It calls `client.updateServiceMetadata` to perform the on-chain update.
server.registerTool( 'azeth_update_service', { description: [ 'Update metadata for your registered service on the trust registry.', '', 'Use this when: You need to change your service endpoint, description, capabilities,', 'or other metadata after initial registration with azeth_publish_service.', '', 'Supported metadata keys: "endpoint", "description", "capabilities", "name", "entityType", "pricing".', 'For capabilities, provide a JSON array string (e.g., \'["translation", "nlp"]\').', '', 'Note: Catalogs are off-chain and served from your endpoint. Update your catalog by', 'updating the response at your endpoint, not via this tool.', '', 'Returns: Confirmation with transaction hash.', '', 'Note: Your account must already be registered on the trust registry.', 'This requires a transaction (gas cost). Only the account owner can update metadata.', '', 'Example: { "key": "endpoint", "value": "https://api.example.com/v2" }', ].join('\n'), inputSchema: z.object({ chain: z.string().optional().describe('Target chain. Defaults to AZETH_CHAIN env var or "baseSepolia". Accepts "base", "baseSepolia", "ethereumSepolia", "ethereum" (and aliases like "base-sepolia", "eth-sepolia", "sepolia", "eth", "mainnet").'), key: z.enum(['endpoint', 'description', 'capabilities', 'name', 'entityType', 'pricing']).describe( 'Metadata key to update.', ), value: z.string().min(1).max(2048).describe( 'New value. For "capabilities", provide a JSON array string like \'["translation", "nlp"]\'.', ), }), }, async (args) => { let client; try { client = await createClient(args.chain); const txHash = await client.updateServiceMetadata(args.key, args.value); return success({ key: args.key, value: args.value, message: `Service metadata "${args.key}" updated successfully.`, }, { txHash }); } catch (err) { return handleError(err); } finally { try { await client?.destroy(); } catch { /* M-10 */ } } }, );