Skip to main content
Glama
811,798 tools. Updated 2026-11-20 16:27

"Factur-X MCP (Model Context Protocol) Integration" matching MCP tools:

  • Get Total Value Locked for one or many DeFi protocols from DeFiLlama: current USD TVL, 7/30-day change, fees and revenue when reported, per-chain breakdown, and optional daily historical series. Batch multiple protocols via protocols=[...] — batch responses return one compact economic summary per protocol; single-protocol calls add chain and historical detail. Supports 3,000+ protocols; use DeFiLlama slugs ('aave-v3', 'uniswap-v3'); common aliases are auto-corrected. Use when: Use for protocol-level economic questions — size, growth, fees, or revenue of a specific protocol. For 2+ protocols always batch in one call rather than calling per-protocol. Pass include_historical=true with days when a trend is needed; without it the response is a current TVL scalar. For ecosystem-level chain comparisons use get_chain_metrics instead. Limitations: Third-party DeFiLlama analytics, not on-chain truth. Upstream revenue failures surface as revenue_error_type and null economic fields are data gaps — never fabricate values for them. Alternatives: get_chain_metrics, get_yield_rates, get_dex_volume
    ConnectorNo auth
  • Rank DeFi protocols by total value locked from DefiLlama, filtered by chain, category or name substring, with each protocol's slug, category, chain list, TVL in USD, 1d/7d TVL change and market cap. Use it to size a protocol, find the biggest venues on a chain, or resolve the slug the protocol-detail tool needs. A protocol DefiLlama publishes no TVL for keeps a null figure, never a zero. Read live at request time and held for 5 minutes. Costs $0.008 USDC per call via x402 on Base; an unpaid call returns the payment challenge instead of data, and a call that returns no data is never settled so it costs nothing. Equivalent HTTP route: GET /defi/protocols.
    ConnectorNo auth
  • Get a wallet's DeFi positions across all DeBank-supported chains and protocols. Returns protocol-level positions, asset/debt/net USD values, optional token lists, aggregate exposure, and optional all-chain net worth. Set include_token_balances=true to also return DeBank's complete cross-chain wallet token list. Set include_token_lists=false for a compact balance and debt summary without nested position tokens. This covers substantially more protocols and chains than the block-accurate get_defi_positions tool. Use raw-RPC tools for liquidation, swap quotes, or other transaction-critical questions. Use when: Use for broad wallet discovery, portfolio allocation, protocol exposure, or cross-chain position questions. Set include_token_balances=true when complete wallet token discovery is required; otherwise the response only includes tokens attached to protocol positions. Set include_token_lists=false when only protocol balances, debt, or aggregate exposure are needed. Use get_defi_positions when the user needs a block-accurate Aave, Compound, Uniswap, or Lido snapshot. Limitations: DeBank portfolio data is third-party analytics and may be stale, including occasional long refresh delays. It is read-only, EVM wallet oriented, and does not prove current liquidation or execution state. include_token_balances adds a separate billable DeBank request; include_token_lists only changes response detail. Alternatives: get_defi_positions, get_wallet_portfolio, get_token_approvals
    ConnectorNo auth
  • Get Total Value Locked for one or many DeFi protocols from DeFiLlama: current USD TVL, 7/30-day change, fees and revenue when reported, per-chain breakdown, and optional daily historical series. Batch multiple protocols via protocols=[...] — batch responses return one compact economic summary per protocol; single-protocol calls add chain and historical detail. Supports 3,000+ protocols; use DeFiLlama slugs ('aave-v3', 'uniswap-v3'); common aliases are auto-corrected. Use when: Use for protocol-level economic questions — size, growth, fees, or revenue of a specific protocol. For 2+ protocols always batch in one call rather than calling per-protocol. Pass include_historical=true with days when a trend is needed; without it the response is a current TVL scalar. For ecosystem-level chain comparisons use get_chain_metrics instead. Limitations: Third-party DeFiLlama analytics, not on-chain truth. Upstream revenue failures surface as revenue_error_type and null economic fields are data gaps — never fabricate values for them. Alternatives: get_chain_metrics, get_yield_rates, get_dex_volume
    ConnectorNo auth
  • Get a wallet's DeFi positions across all DeBank-supported chains and protocols. Returns protocol-level positions, asset/debt/net USD values, optional token lists, aggregate exposure, and optional all-chain net worth. Set include_token_balances=true to also return DeBank's complete cross-chain wallet token list. Set include_token_lists=false for a compact balance and debt summary without nested position tokens. This covers substantially more protocols and chains than the block-accurate get_defi_positions tool. Use raw-RPC tools for liquidation, swap quotes, or other transaction-critical questions. Use when: Use for broad wallet discovery, portfolio allocation, protocol exposure, or cross-chain position questions. Set include_token_balances=true when complete wallet token discovery is required; otherwise the response only includes tokens attached to protocol positions. Set include_token_lists=false when only protocol balances, debt, or aggregate exposure are needed. Use get_defi_positions when the user needs a block-accurate Aave, Compound, Uniswap, or Lido snapshot. Limitations: DeBank portfolio data is third-party analytics and may be stale, including occasional long refresh delays. It is read-only, EVM wallet oriented, and does not prove current liquidation or execution state. include_token_balances adds a separate billable DeBank request; include_token_lists only changes response detail. Alternatives: get_defi_positions, get_wallet_portfolio, get_token_approvals
    ConnectorNo auth
  • Daily TVL, volume, and fees time series for one named protocol. One-shot profile→get_platform_info. Ranked multi-protocol list→search_platforms. CEX perps history: pass exchange_slug (e.g. gate) or platform_name. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • One-shot protocol profile by name and scope. scope=full adds competition_metrics{} for CEX venues (spot/derivs/depth/OI core+extended/PoR). Set include_oi_symbol_detail=true with oi_symbol_limit (1-100, default 20) for top-N OI breakdown. Ranked multi-protocol list→search_platforms. Daily time series→get_platform_history. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.
    ConnectorNo auth
  • Generate compliant e-invoice XML from a JSON invoice, in either EN 16931 syntax. Profiles: en16931, xrechnung-ubl, peppol-bis-3, xrechnung-cii, facturx-en16931 — the profile chooses the syntax, and xrechnung-cii and facturx-en16931 come back as CII. The invoice is validated first and generation is refused if it fails, because emitting XML for an invalid invoice produces a file that passes nothing. CREDIT NOTES GENERATE TOO, from the same object: invoiceTypeCode "381" emits a UBL CreditNote document under the UBL profiles and ram:TypeCode 381 under the CII ones, since CII has one document for both. XML ONLY, NEVER A PDF: Factur-X and ZUGFeRD files are CII XML inside a PDF/A-3 container, and this tool builds no container, so a facturx-en16931 result is the payload and not a Factur-X document — do not tell the user otherwise. If they need the PDF itself, no tool here returns one; the HTTP API does, on every plan: POST https://api.attestwire.com/v1/generate?format=pdf with the same invoice and profile facturx-en16931 returns a Factur-X / ZUGFeRD PDF (EN 16931 profile), with the CII XML inside as factur-x.xml, watermarked "not for sending" on the free plan and clean on a paid one. On xrechnung-cii the generator's own FIXTURE documents were run through the official KoSIT validator on release and accepted; on facturx-en16931 they were not, because that profile's BT-24 matches no XRechnung scenario for the validator to judge. Neither is a verdict on the document you just generated — nothing is sent to KoSIT at call time, so never call it "KoSIT-validated". REQUIRES AN API KEY and costs 1 document.
    ConnectorNo auth
  • Estimate the USDC cost of a chat completion request before paying — free, no payment, no authentication required. Read-only: no state changes and no external calls; the estimate is computed locally from server pricing config, so repeated calls with identical inputs return identical results (idempotent). Use this tool to check the exact price for a given model/mode, messages, and max_tokens before calling the paid chat_completions tool. Provide either mode (auto/eco/premium routing) or model (explicit id, mutually exclusive with mode); one of the two is required — if both are sent, model wins. mode values: auto = cheapest model fitting the context, eco = cheapest available, premium = best model.
    ConnectorNo auth
  • WHEN: object name is unknown, partial, or you need to find by concept/keyword. Search the D365 F&O knowledge base for X++ code, tables, classes, forms, views, enums, EDTs, security objects using natural language or partial names. Returns ALL chunks (metadata, Declaration, methods) for the top-scoring objects so the LLM has complete context on the first call. Lower-scoring results return a short preview. No follow-up get_object_details call is needed for top results. NOT for listing all objects in a model -- use list_objects for that. NOT when the exact name is known -- use get_object_details for that. NEVER call search_d365_code twice in the same conversation turn. If one search did not find the object, answer from what you have -- do not repeat the search. When you need context on MORE THAN ONE concept simultaneously, use batch_search instead -- it runs all queries in parallel and is faster. NEVER call for ADO items (FDD, RDD, IDD, Bug, Task, PR, WorkItem, sprint, #1234) -- use ado_* tools instead.
    ConnectorNo auth
  • List the full model catalog. Returns id, provider, display name, context window, max output tokens, pricing, and a per-model `available` verdict for your account (with `unavailable_reason` when false). Nothing is filtered out — `available` is what varies by caller. It also shows your plan, how many models a panel seats, each model's family, and which model a family name resolves to for you. Call before `create_deliberation` if the user wants specific models. Model IDs from this endpoint are what `create_deliberation`'s `models` parameter expects.
    ConnectorNo auth
  • Use this when the user asks about a specific Model Context Protocol server — whether it is listed in the official MCP registry, what endpoint it publishes, how current its listing is, or whether that endpoint responds. Returns the registry record (name, version, publish and update dates, declared remote endpoints, registry status) plus the result of one anonymous request to a registry-published endpoint. Reports observations only. It does NOT assess whether a server is safe, trustworthy, well-built or suitable — we cannot see what a server does with data, and reachability is not safety. Many listed servers require authentication and cannot be queried anonymously; that is normal and is not a fault. Absence from the registry is not evidence a server does not exist. Not for: security assessment, recommending which MCP server to install, or checking AI tools in the RightAIChoice catalog (use check_tool_status).
    ConnectorNo auth
  • Use this when the user asks about a specific Model Context Protocol server — whether it is listed in the official MCP registry, what endpoint it publishes, how current its listing is, or whether that endpoint responds. Returns the registry record (name, version, publish and update dates, declared remote endpoints, registry status) plus the result of one anonymous request to a registry-published endpoint. Reports observations only. It does NOT assess whether a server is safe, trustworthy, well-built or suitable — we cannot see what a server does with data, and reachability is not safety. Many listed servers require authentication and cannot be queried anonymously; that is normal and is not a fault. Absence from the registry is not evidence a server does not exist. Not for: security assessment, recommending which MCP server to install, or checking AI tools in the RightAIChoice catalog (use check_tool_status).
    ConnectorNo auth
  • Delete a teammate by UUID (a soft delete; their emails are removed from signature deployment). Only available when the workspace manages its own team list — if a directory integration (Google, Microsoft or Zoho Mail) drives teammates, this returns a 409 conflict.
    Connector
    Destructive
    OAuth
  • Define a new custom smart field, a merge field signature templates and campaign conditions can use. Check list_smart_fields first: labels are unique, and to rename, retype or rebind an existing field use update_smart_field instead. A manual field starts empty; set each teammate's value with update_teammate. Bound to an integration (integration_id + integration_attribute), its values come from that integration and update_teammate can no longer set them; integrations do not fill url fields, so keep a url field manual. Creating the field changes no signature until a template references it. Writes one field and returns it. Needs the smart_fields:write scope; a taken label, an invalid kind or an unknown or unsuitable integration returns 422.
    ConnectorOAuth
  • Authoritative REST API reference for writing integration code into the user's app. Base URL: https://api.volanea.com — auth is `Authorization: Bearer <secret key>`; sends accept an `Idempotency-Key` header. Use this instead of guessing endpoint shapes or SDK names. THREE MODES, and the default is the expensive one: `{ resource, indexOnly: true }` lists every operation's id, method, path, and one-line summary with NO schemas (a few KB); `{ resource, operations: [ids] }` returns full request/response schemas for just those operations, plus only the schemas they reference; `{ resource }` alone returns the entire resource, which for Campaigns or Contacts is 40-50 KB of one reply. Start with indexOnly, then expand the two or three operations you are actually going to call — every byte of a reference dump re-enters your context on every later turn.
    ConnectorNo auth
  • Authoritative REST API reference for writing integration code into the user's app. Base URL: https://api.volanea.com — auth is `Authorization: Bearer <secret key>`; sends accept an `Idempotency-Key` header. Use this instead of guessing endpoint shapes or SDK names. THREE MODES, and the default is the expensive one: `{ resource, indexOnly: true }` lists every operation's id, method, path, and one-line summary with NO schemas (a few KB); `{ resource, operations: [ids] }` returns full request/response schemas for just those operations, plus only the schemas they reference; `{ resource }` alone returns the entire resource, which for Campaigns or Contacts is 40-50 KB of one reply. Start with indexOnly, then expand the two or three operations you are actually going to call — every byte of a reference dump re-enters your context on every later turn.
    ConnectorNo auth
  • Get the connection status of every third-party integration stored for the organization, as an object mapping each integration name to a boolean: true when it is connected and usable, false when it needs reconnecting. Integrations never set up are absent. Use get_integration for one integration's expiry and last update. Any member may read; tokens are never returned.
    ConnectorOAuth
  • Creates an API key on the connected account for the user's server to call the REST API with, and returns it once. Create one only when the user asks for it or the integration needs it; keys are listed and revoked in the dashboard. While building or testing an integration, create a test key: it answers from fictional people and companies, never reaches a registry, and is never billed.
    ConnectorNo auth
  • Creates an API key on the connected account for the user's server to call the REST API with, and returns it once. Create one only when the user asks for it or the integration needs it; keys are listed and revoked in the dashboard. While building or testing an integration, create a test key: it answers from fictional people and companies, never reaches a registry, and is never billed.
    ConnectorNo auth
  • Disconnect a sign-in based integration (for example Google Ads, Meta Ads or HubSpot) from a deployed agent. Call it without confirm first: it shows what is connected and what will be removed, and changes nothing. After the user agrees, call again with confirm: true. The saved sign-in, the selected accounts and the connection's settings are cleared (your own app keys are kept), the provider is asked to revoke the access where it supports that, scheduled tasks that need the integration stop running, and a running agent restarts. It cannot be undone; reconnect with connect_agent_oauth. For plain credentials such as Telegram, clear fields with set_agent_credentials instead.
    Connector
    Destructive
    API key