Skip to main content
Glama
vechain

VeChain MCP Server

Official
by vechain
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

VeBetterDAO: list xApps with on-chain status, roles and IPFS metadata

getVeBetterDaoApps
Read-onlyIdempotent

Retrieve VeBetterDAO xApps directly from the on-chain registry, including roles, endorsement status, and IPFS metadata. Filter by app ID, category, or active voting round.

Instructions

List VeBetterDAO xApps directly from the on-chain X2EarnApps registry. For each app returns: id, on-chain name, owner (teamWalletAddress), createdAtTimestamp, roles (admin, moderators, creators, rewardDistributors), endorsement status (isEndorsed, endorsementScore vs threshold, isUnendorsed/grace period, isBlacklisted, isEligibleNow), whether the app is active in the current XAllocationVoting round, and IPFS metadata (description, website, logo, banner, social links, categories, distribution_strategy). Supports filtering to a single appId, to apps active in the current round, and by category (array of category ids, case-insensitive, OR semantics — sourced from IPFS metadata). Uses the VeChain SDK multicall for efficiency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNoOptional bytes32 app id; if provided, only that app is returned
categoriesNoOptional array of category ids to filter apps by (case-insensitive, OR semantics). Categories live in the IPFS metadata, so includeMetadata is forced to true when this is set. Known mainnet categories: nutrition, plastic-waste-recycling, fitness-wellness, renewable-energy-efficiency, sustainable-shopping, green-mobility-travel, pets, education-learning, green-finance-defi, others (deprecated: social-community-activism, carbon-footprint).
includeRolesNoFetch admin/moderators/creators/rewardDistributors per app
includeMetadataNoFetch off-chain IPFS metadata (description, logo, socials, categories...)
includeEndorsersNoFetch endorser addresses per app (extra on-chain calls)
includeUnendorsedNoInclude apps currently in grace period (lost endorsements)
metadataConcurrencyNoConcurrency limit for IPFS metadata fetches
onlyActiveInCurrentRoundNoReturn only apps included in the current round of voting

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataNo
errorNo
networkYes

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable context: using multicall for efficiency, forcing includeMetadata when categories are present, and detailing IPFS metadata fetching behavior. No contradictions.

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?

The description is thoroughly detailed yet well-structured, starting with the primary purpose, then listing returns, followed by filtering options. Every sentence adds value, and it is appropriately sized for the tool's complexity.

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

Completeness5/5

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

Given the output schema exists, the description covers all necessary behavioral details: multi-call efficiency, filtering logic, IPFS metadata handling, and parameter interactions. No gaps are apparent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning: explains categories OR semantics, concurrency limits, defaults, and the dependency between categories and metadata. It clarifies behavior beyond the schema.

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 clearly states 'List VeBetterDAO xApps directly from the on-chain X2EarnApps registry' and enumerates all returned fields. It differentiates from siblings like getB3TRAppsLeaderboard and getAppHubApps by focusing on on-chain registry data with roles and IPFS metadata.

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?

The description implies usage for listing xApps with various filters but lacks explicit when-to-use/alternatives guidance. It does not mention when not to use this tool or contrast with siblings, leaving the agent to infer from context.

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/vechain/vechain-mcp-server'

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