Tools (95)

• Cancel operation handoff

  Cancel a pending offchain operation handoff. This never cancels already signed or submitted chain transactions.

• Cancel XDaLa bundle deploy handoff

  Cancel a pending XDaLa bundle deploy handoff. This is offchain metadata only and never cancels chain transactions.

• Cancel XDaLa session start handoff

  Cancel pending xDaLa session start handoff metadata only. This preparation/read-only MCP tool does not sign, submit, execute, or cancel on-chain work.

• Create operation handoff

  Create an offchain human-in-the-loop operation and return a browser URL. The MCP never signs or submits transactions; the user executes locally with a browser wallet on the operation page. Do not use this tool to start, run, launch, execute, or queue XDaLa sessions. Do not use this tool for xgr_validateDataTransfer, SessionPermit, Manage Sessions imports, xgr-session-start@1, XDaLa session start handoffs, or starting a deployed XRC-729 workflow. For these intents, use create_xdala_session_start_handoff. If create_xdala_session_start_handoff is unavailable, report that the session-start tool is unavailable instead of falling back to create_operation_handoff.

• Create XDaLa bundle deploy handoff

  Store a validated xgr-multi-bundle@1 bundle offchain under an unguessable bearer handle and return an XDaLa Workbench import URL. The MCP does not sign, submit, or execute transactions.

• Create XDaLa session start handoff

  Prepare and store a read-only xgr-session-start@1 handoff for xDaLa Workbench. Use this tool whenever the user wants to start, run, launch, execute, queue, or prepare an XDaLa session. Use this tool for starting an existing deployed XRC-729/XRC-137 workflow, starting from a runtime XRC-729 orchestration, starting from a bundle deploy result, or importing a canonical xgr-session-start@1 request into xDaLa Manage Sessions. When explaining required input to users, use canonical xgr-session-start@1 terminology: sessions[].orchestration, sessions[].ostcId, sessions[].stepId, sessions[].payload, sessions[].maxTotalGas. Do not ask users for entryStepId; entryStepId is not the Workbench Session Start field. For deployed XRC-729 workflows, first inspect the runtime, identify ostcId and the likely entry step, resolve that step's XRC-137 rule, derive required payload fields from the XRC-137 payload schema, treat fields with defaults as optional, and present required and optional/default fields before creating a handoff. Do not call this tool with guessed payload values. If required start payload fields are missing, first present the required fields to the user and ask for values or explicit permission to use demo values. Only use demo/dummy/example/default values when the user explicitly asks or accepts them. This tool returns a Workbench xdalaUrl such as https://xdala.devnet.xgr.network/session-start/ss_... . The agent must show the returned xdalaUrl to the user. Do not replace the xdalaUrl with a generic /operations/op_... link. The MCP does not sign, submit, or execute. xDaLa Workbench performs local signing and calls xgr_validateDataTransfer. Do not describe the XRC-729 contract owner as the owner of a not-yet-started session; owner()/getOwner() and getExecutorList() identify start-authority roles only. Use sessions[].starterAddress only as an intended starter when explicitly set, and use terminal result data such as result.results[].owner/sessionId/pid for the actual session owner/starter after Workbench start.

• Create XGR purchase order

  Use when the user specifies an exact integer amount_xgr. Call get_xgr_purchase_options first, use payment_assets[].key, collect user-supplied identity and wallet fields, require explicit terms acceptance, and create one live reservation. Pay only from the returned payment_instruction.

• Create XGR purchase order by budget

  Use when the user specifies a maximum USDC/USDT payment amount rather than an XGR quantity. Call get_xgr_purchase_options first, use payment_assets[].key, collect user-supplied identity and wallet fields, require explicit terms acceptance, and create one live reservation. Pay only when payment_approved=true and next_action=external_crypto_payment; otherwise do not pay.

• Estimate XDaLa rule gas

  Use this to estimate XDaLa/XRC-137 rule gas. Returns validation gas, branch gas, grant fees and worst-case totals from xgr_estimateRuleGas.

• Expand XGR address graph neighbors

  Read-only progressive expansion of one address by exactly one graph level. Use this instead of requesting a larger graph when exploring interactively.

• Find latest XDaLa session

  Use this when the user asks for the latest XDaLa session but does not provide owner and sessionId. This read-only tool resolves the newest indexed XDaLa session from the Explorer database and can optionally include final receipt payload data.

• Find reusable XRC-137 rules

  Read-only metadata-assisted search for existing owner XRC-137 contracts that could be reused instead of redeployed.

• Find startable XDaLa workflows

  Read-only discovery of deployed XRC-729 workflows that a given address can start as owner, executor, or wildcard executor. Use this whenever the user provides an address and asks which sessions/workflows they can start. This tool does not create session-start handoffs.

• Get account live state

  Use this for live EVM account state. Returns balance, nonce and contract code for an address.

• Get account transactions

  Read-only chain-wide Explorer DB transaction lookup for one account as sender, recipient, or both. Use this instead of XDaLa session tools for account-wide transaction history.

• Get XGR address relation graph

  Read-only bounded graph of indexed native XGR transfers around an address. Returns aggregated on-chain relations, verified Explorer labels, depth and truncation metadata. A relation proves only that transactions occurred between addresses; it does not imply common ownership or identity.

• Get block transactions

  Read-only list of transactions in a specific indexed block, latest indexed block, or latest indexed block minus latestOffset.

• Get XGRChain status

  Use this for live XGRChain status. Returns chain id, latest block number and gas price from JSON-RPC, plus official XGR.Network entry points for the connected mainnet.

• Get latest block

  Use this when the user asks for the latest EVM block details from XGRChain.

• Get latest XDaLa session payload

  Use this when the user asks for the payload of the latest XDaLa session. This read-only tool resolves the latest indexed session without requiring owner plus sessionId, then returns payload, apiSaves, contractSaves and extras from the final receipt.

• Get operation status

  Return the current status of an operation handoff. Use this after the user opens the operation page and signs or cancels local wallet transactions.

• Get recent value transfers

  Read-only shortcut for recent native XGR value transfers from the Explorer transaction index. Native value transfer means transactions.value > minValueWei and does not include gas fees.

• Get recent XDaLa sessions

  Use this to list recent indexed XDaLa sessions from the read-only Explorer database, especially when the user does not know owner and sessionId. Supports optional owner filtering, time windows, result limits and payload enrichment.

• Get transactions behind an XGR graph relation

  Returns the indexed native XGR transactions represented by one directed graph edge, with the same minimum-value and time filters used by the relation graph.

• Get XDaLa session receipt logs

  Use this to inspect what an XDaLa session actually did. Returns decoded engine receipt data such as input payload, API saves, contract saves, execution contract, rule contract, valid flag, inner gas usage and optional raw receipt logs. Do not use this for a simple transaction timeline; use get_session_transactions instead.

• Get live XDaLa session status

  Use this to check live session status from XGR RPC. Returns xgr_sessionAlive for a session owner and session id.

• Get XDaLa session transactions

  Use this to list the blockchain transactions belonging to an XDaLa session. This returns the timeline of transaction hashes, blocks, fees and iteration steps. It does not return full engine payloads, API saves or contract read results.

• Get XDaLa sessions overview

  Use this for high-level indexed XDaLa session analytics from the Explorer API.

• Get transaction evidence

  Use this when the user asks what happened in a specific transaction. Combines indexed Explorer transaction data, receipt data and live RPC fallback if available.

• Get transaction receipt

  Use this for receipt logs, status and gas usage of a transaction. Prefers Explorer decoded receipt data.

• Get transaction stats

  Read-only compact chain transaction statistics from the Explorer transaction index, with optional block or block-timestamp window filters.

• Get unused XRC-137 rules

  Read-only list of owner XRC-137 rules with no observed tx_receipts engine_rule_contract usage.

• Get XDaLa active sessions timeseries

  Use this when the user asks for active/concurrent XDaLa sessions over time.

• Get XDaLa authoring rules

  Use this before creating, modifying or reviewing XRC/XDaLa artifacts.

• Get XDaLa bundle deploy handoff

  Return stored metadata, bundle JSON, and any recorded deployed result/artifact for an XDaLa bundle deploy handoff handle.

• Get XDaLa bundle deploy result

  Return the stored XDaLa bundle deploy result, canonical deployed artifact, and audit events for a handoff handle. This is read-only and never signs, submits, or executes transactions.

• Get XDaLa payload field value statistics

  Use this when the user asks which values occurred for a specific payload field, for example “which DocumentType values occurred?” or “top values for ReasonCategory”.

• Get XDaLa payload key statistics

  Use this when the user asks which payload fields/keys occurred, how often payload fields appeared, or which payload fields were empty/non-empty. For “last 14 days”, pass windowHours=336.

• Get XDaLa payload term statistics

  Use this when the user asks for payload terms, payload words, payload Begriff statistics, or a statistic over all payload terms in a time range. For “last 14 days”, pass windowHours=336. Do not sample sessions for this task.

• Get XDaLa process Mermaid

  Render an XDaLa XRC-729 process graph from runtime, bundle, or bundle handoff data as Mermaid flowchart text. Read-only; does not sign, submit, or execute transactions.

• Get XDaLa session detail

  Use this when the user asks for details, timeline, steps, payloads, or evidence for a concrete XDaLa session with owner and sessionId.

• Get XDaLa session start handoff

  Read stored xDaLa session start handoff metadata, canonical request, authority, derived sessionOwnership role summary, validation, lean result summary, and terminal result. Read-only; does not sign, submit, or execute. Use sessionOwnership to avoid confusing the XRC-729 contract owner with the actual session owner/starter before Workbench completion.

• Get XDaLa session start result

  Return terminal xDaLa session start result, lean result summary, and audit events. Read-only preparation/result lookup only; the MCP does not sign, submit, or execute, and users sign locally in Workbench/wallet/local signer. For completed handoffs, prefer result.results[].owner/sessionId/pid over XRC-729 contract owner facts when identifying the actual session owner/starter.

• Get XDaLa session statistics

  Use this when the user asks for aggregate XDaLa session statistics, for example “statistics for the last 2 weeks”, “success/failure counts”, “average session duration”, “average steps per session”, “top errors”, or “how many sessions ran recently”. For “last 2 weeks”, pass windowHours=336.

• Get XDaLa session timeseries

  Use this when the user asks for XDaLa sessions over time, for example “sessions per day”, “daily sessions last 2 weeks”, “monthly session trend”, or “success/fail per day”. For “last 2 weeks by day”, pass windowHours=336 and bucket="day".

• Get XDaLa start payload history

  Read-only indexed history of payload values used when starting a specific XRC-729 OSTC entry step. Reads Explorer PGRO through the MCP gateway only, selects the first matching entry-step receipt per owner/session, and returns compact scalar value statistics for UI pickers.

• Get XDaLa step statistics

  Use this when the user asks for step-level XDaLa statistics, for example “how many steps were valid”, “invalid steps”, “failed steps”, “step gas totals”, or “step stats for a session”.

• Get XGR circulating supply

  Use this to retrieve circulating supply information exposed by xgr_getCirculatingSupply.

• Get XGR core addresses

  Use this to retrieve XGR core protocol addresses exposed by the xgr_getCoreAddrs RPC method.

• Get XGR documentation topic

  Retrieve canonical Markdown documentation for an XGR/XDaLa topic.

• Get XGR MultiBundle reference

  Retrieve canonical xgr-multi-bundle@1 Markdown documentation.

• Get XGR MultiBundle schema

  Retrieve canonical XGR MultiBundle schema.

• Get official XGR.Network information

  Use this when the user asks what XGR.Network, XGRChain or XDaLa is, or requests official XGR URLs, chain metadata, RPC, Explorer, MCP, testnet faucet, documentation, XRC standards, source repositories or ecosystem entry points. Returns canonical project metadata and links; use get_chain_status for live chain state.

• Get XGR purchase options

  Call this first for every XGR purchase. Read live price, stock and payment assets; use payment_assets[].key exactly as payment_asset and inspect requires_sender_wallet before creating an order.

• Get XGR Session Start schema

  Retrieve canonical Workbench xgr-session-start@1 handoff schema.

• Get XGR standard example

  Retrieve a concrete JSON example for XRC-137 or XRC-729.

• Get XGR standard reference

  Use this before drafting XRC-137 or XRC-729 artifacts.

• Get XGR standard schema

  Retrieve machine-readable JSON schema for XGR standards.

• Get XGR starter gas options

  Check whether free native XGR starter gas is available for a low-balance EVM address. Use this before deployments, session starts, contract calls or other on-chain actions when the address lacks gas. Returns the fixed 1 XGR grant policy and the tool to call next.

• Get XRC-729 authority

  Read-only authority lookup for one XRC-729 orchestration contract. Reads owner()/getOwner() and getExecutorList(), detects zero-address executor wildcard, and never signs, submits, executes, or creates a handoff.

• Get XRC-729 OSTC state

  Read-only list of indexed OSTC state entries for an XRC-729 contract.

• Get indexed XRC contract

  Read-only lookup of one indexed XRC contract by address.

• Get indexed XRC contract events

  Read-only list of all indexed XRC events for one contract.

• Get XRC failure stats

  Read-only invalid/failure statistics associated with an XRC-137 rule or XRC-729 OSTC/process filters.

• Get XRC owner summary

  Compact read-only summary of XRC-137/XRC-729 assets and recent XRC events for an owner.

• Get XRC session usage

  Read-only usage statistics from Explorer PGRO tx_receipts for XRC-137 rules or XRC-729 OSTC/process filters.

• List recent operations

  List recent offchain operation handoffs. Secrets and browser execution tokens are never returned by this tool.

• List open XDaLa wake-up targets by address

  Use this to list WAITING XDaLa runtime steps that the given wallet or Safe address is allowed to wake via RPC. This is read-only and calls xgr_listWakeupTargetsByAddress, then enriches public/plain XRC rule payload metadata via eth_call when available.

• List XDaLa session IDs grouped by owner

  Use this when the user asks for session IDs. Always returns session IDs grouped by owner because session IDs are only unique together with owner.

• List XDaLa session owners

  Use this when the user asks which owners had XDaLa sessions, asks for the owner list, or when aggregate results show uniqueOwners but the concrete owner addresses are needed. For “last 3 weeks”, pass windowHours=504.

• List XDaLa sessions

  Use this when the user asks to list XDaLa sessions, enumerate recent sessions, or discover owner/sessionId pairs. This returns concrete owner + sessionId pairs and supports keyset pagination. For “last 3 weeks”, pass windowHours=504.

• List XGR documentation topics

  List canonical Markdown documentation topics served by the MCP knowledge base.

• List XGR standard examples

  List available example artifacts for a standard.

• List XGR standards

  List agent-readable XGR and XDaLa standards available in the MCP knowledge base.

• List XRC-729 contracts by executor

  Read-only Explorer lookup for active XRC-729 executor relations of one address. This is index-backed, does not scan contracts, and returns Explorer pagination metadata.

• List indexed XRC contracts

  Read-only list of indexed XRC-137/XRC-729 contracts globally or filtered by owner/type.

• List indexed XRC events

  Read-only list of XRC events globally or by owner, contract, type/action, tx hash, or block range.

• List XRC process sessions

  Read-only list of sessions associated with an XRC-729 OSTC id/hash.

• Quote XGR purchase budget

  Use only when the user specifies a maximum USDC/USDT payment budget. Call get_xgr_purchase_options first, pass payment_assets[].key, and treat this result as planning only: it creates no order and is not a payment instruction.

• Read XRC-137 rule JSON

  Read-only eth_call to XRC137.getRule(), returning the runtime rule JSON string.

• Read XRC-729 OSTC JSON

  Read-only eth_call to XRC729.getOSTC(ostcId), returning the runtime OSTC JSON string.

• Request XGR starter gas

  Use this tool when a user or agent needs native XGR to pay transaction fees on the configured XGR network. It sends one fixed 1 XGR grant from a dedicated server-controlled funding wallet to an eligible low-balance EVM address. Use it before deployments, session starts, contract calls or other on-chain actions when the address lacks gas. One confirmed grant per address; client-IP request limits apply; no repayment is required. The service never requests, receives or stores user or third-party private keys and cannot sign on behalf of users.

• Resolve XDaLa wake-up payload schema

  Use this to resolve payload fields for one currently WAITING wake-up target. It reads XRC-729.getOSTC(step -> XRC-137) and XRC-137.getRule() via eth_call for plain JSON rules. Encrypted rules are not decrypted server-side.

• Resolve XRC-729 process graph

  Resolve deployed XRC-729 OSTC runtime JSON and linked indexed XRC-137 rule contracts without mutating chain state.

• Search transactions

  Read-only chain-wide Explorer DB transaction search. Use for general transaction, native XGR value, from/to address, hash, input, session id, validity/execution, and block/time-range questions; do not sample XDaLa sessions for chain-wide transaction questions.

• Search native XGR transactions for flow analysis

  Find indexed native-XGR transactions using time, value and address filters before choosing a transaction for Relation Graph or Value Flow analysis. Typical use: all native transfers in the last 24 hours above a given XGR/wei amount. Results are read-only and cursor-paginated for latest/oldest sorting.

• Trace an XGR transaction relation graph

  Loads an indexed transaction, uses its sender as the bounded graph root, returns sender/recipient trace roots plus the graph and an explicit edge to highlight. Useful for following native XGR transaction relations, but it does not attribute later mixed balances to the seed value.

• Trace native XGR value provenance

  Read-only native-XGR value-flow analysis starting from one transaction. Use model="possible" for conservative attribution ranges or model="proportional" for haircut attribution. Native XGR has no per-coin identity, so results are provenance models rather than proof that a specific coin moved. maxTransfers and maxHops accept a number or "all"; "all" is still bounded by Explorer server safety caps and reports truncation explicitly.

• Validate XDaLa blueprint

  Validate XRC-729 OSTC plus per-step XRC-137 payload-flow consistency.

• Validate XDaLa bundle

  Alias for validate_xgr_multibundle.

• Validate XDaLa rule expressions

  Validate rule expressions against available placeholder fields.

• Validate XGR MultiBundle

  Validate canonical deployable xgr-multi-bundle@1.

• Validate legacy XGR Session Start

  Validate legacy low-level session-start payload only.

• Validate XGR Session Start Handoff

  Validate a canonical Workbench xgr-session-start@1 request.

• Validate XRC-137 authoring rules

  Validate a drafted XRC-137 authoring object.