Call a view/pure function on a TRON smart contract. No auth or private key required.
ConnectorNo auth
620,587 tools. Updated 2026-09-29 01:58
"How to call a smart contract function" matching MCP tools:
- Composite: send a DVM-BASIC contract source to the daemon's gas estimator, then return the raw estimate alongside a plain-text breakdown (what each gas number means), the parsed contract surface, and curated DVM deploy docs as citations. When to call: BEFORE asking a wallet to broadcast a deploy transaction, OR when explaining the cost of a contract to a user. PREFER this over chaining dero_get_gas_estimate yourself: this composite already explains gascompute vs gasstorage in plain language, parses the SC source to show what functions the user is about to deploy (reusing extractScSurface from explain_smart_contract), and protects against fabricating a breakdown when the daemon reports 0/0 with a non-OK status. Input Requirements: - `sc` is REQUIRED. The full DVM-BASIC contract source — must contain at least one `Function ... End Function` block. A function body alone will fail with INVALID_INPUT. - `signer` is OPTIONAL. A dero1.../deto1... address that will sign the eventual deploy tx. The daemon uses it for fee context; omitting it still returns a meaningful estimate. - `include_breakdown` is OPTIONAL (default true). Set false when you only need the raw numbers (e.g. piping into a fee table). Output: `{ estimate: { gascompute, gasstorage, status }, breakdown: { compute_note, storage_note, total_units } | null, signer_used, include_breakdown, sc_surface: { functions, stringkeys, uint64keys, raw_code_length, function_count }, related_docs }`. `breakdown` is null when `include_breakdown=false` OR when the daemon returned 0/0 with a non-OK status (never fabricated). On DVM compile failure the composite returns a structured `_meta.error` with code `INVALID_INPUT` and the daemon's exact compile message in `_meta.error.raw`.ConnectorNo auth
- Composite: fetch a DERO smart contract (code + variables + balances) and return its function surface, a classification of the contract pattern (tela_index | tela_doc | token | registry | minimal | generic), a plain-language narrative, and curated DVM docs citations re-ordered so the most relevant page is first. TELA contracts (apps/files) are detected first and cite the TELA spec; for a deep TELA parse use tela_inspect. When to call: when the user wants to UNDERSTAND a smart contract — its functions, state shape, or which DVM concept to read about. PREFER this over chaining dero_get_sc with a docs lookup yourself: this composite already parses the DVM-BASIC source for function declarations, sorts stringkeys/uint64keys deterministically, and picks the right docs page from a heuristic so the agent does not have to learn DVM-BASIC syntax to summarize a contract. Input Requirements: - `scid` is REQUIRED. Must be 64 hex chars (the smart contract id). Use `0000…0001` for the on-chain name registry as a known-good example. - `topoheight` is OPTIONAL. Provide to inspect the contract at a specific topo height; omit for latest tip. Output: `{ scid, topoheight, kind, surface: { functions[], stringkeys[], uint64keys[], balances }, narrative, raw_code_length, has_code, related_docs }`. `kind` is one of `tela_index | tela_doc | token | registry | minimal | generic`. `surface.functions` items are `{ name, args, returns }`. `has_code` is false when the SCID is unknown or has no on-chain code; `functions` is then `[]` and the narrative explains the gap. `raw_code_length` is always present so the agent knows when to fall back to `dero_get_sc` for the full source.ConnectorNo auth
- Engine version, API contract number, and health. Free (not quota-counted). Call once at the start of a session to confirm the engine is reachable and which contract it serves.ConnectorNo auth
- Agent Brain — Reason over a question or task with your agent's own persistent memory in the loop: recalls up to 12 relevant memories from your agent's private scope, reasons with Claude, and writes up to 3 new memories back, so the agent improves with every call. Recall by meaning, not just keyword, when the estate's memory server is reachable (falls back to its own always-on store otherwise — never fails the call). Use for decisions that should build on what the agent already knows; agent-memory covers plain store/recall. Runs claude-haiku-4.5 — the response names the model that served the call; agent-brain-smart runs the identical contract on claude-sonnet-5. Input: {think: string}. Returns {answer, reasoning, confidence, memories_considered, used_memories, learned, model, engine}. (8 MESH/call, a tool · cognition)ConnectorNo auth
- Runs a deployed Function once, without waiting for a Schedule. It fires a method that is not a GET, sends a request body, and reaches a Function that is not on its public address. It answers with the invocation_id the run will run under, before there is anything to read by it: once the run has been through the worker, 'get_invocation' answers how it went and 'read_invocation_logs' what it printed. Nothing the Function served comes back here; 'fetch_function' answers what a path serves. One run at a time per Function; a second while one is in flight is refused.ConnectorDestructiveOAuth
Matching MCP Servers
- AlicenseAqualityAmaintenanceAn MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.215Apache 2.0
- FlicenseNot gradedqualityDmaintenanceAn MCP server that statically audits Solidity smart contracts for common vulnerabilities like reentrancy and access control, enabling developers to identify and fix security issues via natural language.-
Matching MCP Connectors
- Smart MoneyOAuth
Personal finance: log expenses in plain language, track accounts, budgets and spending
Korean public procurement law: rule-engine rulings, statutes search, live court precedents
- The tracked wallets holding a token, sorted by balance, with market cap and price in USD on Solana. Use when the user asks who is still holding, rather than who ever traded it. blockchain: solana, bnb, base, eth or rh mint: token address wallet_type: restrict to kol, smart or whale. Omit to merge all types. limit: how many holders (default 25)ConnectorNo auth
- Get how a page served from a Valet site talks to the connectors attached to it. It is the pair to get_design_system: consult that tool for the artifact's identity, this one for how it talks to its connectors. Call it before writing any page code that fetches from a connector. Returns the same-origin request contract and a paste-whole session helper that handles both sessionless and stateful connectors, plus the rules a page has to follow: handling a 403, recovering a lapsed session, and never caching a response on the caller's behalf. This needs no Valet account. It answers with static guidance about how pages work — nothing here reads an organization or a site — so an agent can call it before running any OAuth flow.ConnectorNo auth
- 10 dollars per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. A ChainHelix API key does not cover this tool. The MEV order flow stream PUSHED to your https URL for all four chains at once (bnb, ethereum, polygon, avalanche): one signed message per chain per completed minute with detected MEV, each carrying the per-pool rows of that minute. 10 dollars buys 7 days of every chain, against 4 dollars per chain one at a time with stream_register. Call again to renew. Manage with webhook_status and webhook_unregister; the contract is in mev_flow_specConnectorNo auth
- 10 dollars per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. A ChainHelix API key does not cover this tool. The MEV order flow stream PUSHED to your https URL for all four chains at once (bnb, ethereum, polygon, avalanche): one signed message per chain per completed minute with detected MEV, each carrying the per-pool rows of that minute. 10 dollars buys 7 days of every chain, against 4 dollars per chain one at a time with stream_register. Call again to renew. Manage with webhook_status and webhook_unregister; the contract is in mev_flow_specConnectorNo auth
- Create a goal PLAN on Visions & Goals — the qualitative clarify-and-plan side (SMART criteria, action steps). Use this when the user has a vague aspiration to shape ("I want to get fit", "someday buy a cabin"); use ``create_goal`` for the money-tracking side, and link the two. Args: title: The goal statement (required, ≤300 chars). description: Longer context for the plan. timeframe: One of "short", "medium", "long" (default medium). target_date: YYYY-MM-DD (optional). smart_specific: Answer to the SMART "Specific" prompt (optional). smart_measurable: SMART "Measurable" answer (optional). smart_achievable: SMART "Achievable" answer (optional). smart_relevant: SMART "Relevant" answer (optional). smart_timebound: SMART "Time-bound" answer (optional). zoninga_goal_id: An existing zoninga goal id to link the new plan to (sets that goal's ``vng_goal_id``). Returns: {"goal": {id, title, ..., edit_url}} — relay ``edit_url`` to the user as a plain markdown link so they can refine the plan.ConnectorAPI key
- Retrieves native currency transfers and smart contract interactions (calls, internal txs) for an address. **EXCLUDES TOKEN TRANSFERS**: Filters out direct token balance changes (ERC-20, etc.). You'll see calls *to* token contracts, but not the `Transfer` events. For token history, use `get_token_transfers_by_address`. A single tx can have multiple records from internal calls. Requires an `age_from` date to scope results for performance and relevance. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.ConnectorOAuth
- Call any view/pure function on a smart contract and return the decoded result, using a supplied ABI fragment. Supports historical reads via block_identifier and caller_address context for msg.sender-dependent views. Read-only: state-changing functions are rejected. Use when: Use when a protocol question needs a contract read that no higher-level tool covers — e.g. a niche view function or a protocol outside the standard tool set. Prefer purpose-built tools (get_defi_positions, get_lending_rates) for supported protocols. Limitations: Requires a valid ABI fragment; payable/nonpayable functions are rejected. Ethereum mainnet and Base only, with bounded RPC timeout and retry. Alternatives: get_defi_positions, get_lending_rates, get_token_approvalsConnectorNo auth
- Search the Klever VM knowledge base for smart contract development context. Returns structured JSON with matching entries, scores, and pagination. Use this for precise filtering by type or tags; use search_documentation for human-readable "how do I..." answers.ConnectorNo auth
- Retrieves native currency transfers and smart contract interactions (calls, internal txs) for an address. **EXCLUDES TOKEN TRANSFERS**: Filters out direct token balance changes (ERC-20, etc.). You'll see calls *to* token contracts, but not the `Transfer` events. For token history, use `get_token_transfers_by_address`. A single tx can have multiple records from internal calls. Requires an `age_from` date to scope results for performance and relevance. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.ConnectorNo auth
- Get the x402 payment requirements to fund yourself in USDC so you can buy RWAs — the agent-native on-ramp. This returns the 402 challenge only; it moves no funds. To complete funding (two signatures total, the same a human gives), the agent then, ENTIRELY CLIENT-SIDE: 1. Reads `accepts[0]` from the returned body: `payTo` is YOUR Base smart account (derived from `owner_eoa`), `maxAmountRequired` the USDC atomic amount, `asset` the Base USDC contract, `extra` the EIP-712 domain. 2. Signs an EIP-3009 `transferWithAuthorization(from=owner_eoa, to=payTo, value=maxAmountRequired, ...)` over that domain, base64-encodes the x402 PaymentPayload, and re-POSTs to `/v1/route/x402-buy` with it in the `X-PAYMENT` header. On settlement the USDC bridges custody-free to your Injective smart account. 3. Buys any RWA from that Injective balance via `POST /v1/route/intent` (signing the route as usual). The asset rests in your smart account; `send` it elsewhere if you want — exactly like a human user. Always verify `payTo` derives from your own `owner_eoa` before signing. Args: owner_eoa: Your EVM EOA — the payment signer and smart-account owner. amount_usdc: USDC to fund yourself with (human units, e.g. 25.0). asset_id: Optional RWA you intend to buy, recorded for context.ConnectorNo auth
- Individual buys and sells by tracked wallets in one token, most recent first. Use for the sequence of events, for example whether KOLs bought before or after a price move. blockchain: solana, bnb, base, eth or rh mint: token address wallet_type: restrict to kol, smart or whale. Omit to merge all types. limit: how many transactions (default 25)ConnectorNo auth
- How many trades happened and how much value moved over a window of up to 24 hours, plus how many distinct wallets were involved. Use for how busy the market or a single token is, rather than for the individual trades. blockchain: solana, bnb, base, eth or rh wallet_type: kol, smart or whale (default kol) hours: window in hours, at most 24 (default 1) mint: restrict to one tokenConnectorNo auth
- Reconstruct a PARTIAL function/event interface for an EVM contract on a supported EVM chain from its BYTECODE — no source or verification needed. Extracts PUSH4 function selectors + recent event topic0 hashes and resolves the ones public signature DBs (openchain/4byte) know to human signatures. Works on UNVERIFIED contracts because bytecode is ground truth, but it is NOT a full ABI: novel/proprietary selectors DBs have never seen stay unresolved (decompile for those). Use it to understand what an unknown contract does before trusting behavior-based guesses.ConnectorNo auth
- Simulate a call and return success, gas, decoded return, and best-effort state diff / asset changes / logs. Provide a high-level call (address + function + args) or raw (to + data), never both.ConnectorNo auth
- Aggregate hiring data across the whole board, recomputed live: open-role and hiring-company counts, demand mix by function, posted pay-band midpoints by function (p25/median/p75, annual USD), remote share, top hiring locations, and the speedrun vs a16z portfolio split. Use this to answer "what do a16z portfolio startups pay" or "how many startup jobs are open" — the human-readable version lives at https://speedrun-talent-network.com/network.ConnectorNo auth