Skip to main content
Glama
459,989 tools. Updated 2026-08-17 12:39

"Workflow builder and monitoring tools" matching MCP tools:

  • Use this read-only composite workflow tool for risk and stress monitoring across the current DeltaSignal issuer universe. It server-enforces the pressure-board call plan: readiness, top_stressed with limit 15, and risk_distribution. Parameters: optional output_mode=compact only; do not pass limit, offset, ticker, source_date, or issuer filters because this preset owns exact arguments internally. Behavior: read-only and idempotent; it performs three internal HTTPS reads, has no destructive side effects, never calls issuer-level tools, and preserves partial results if one internal call fails. Use it when the user asks for risk monitoring, pressure board, stress board, top stressed overview, or current risk mix.
    Connector
  • Use this read-only composite workflow tool for risk and stress monitoring across the current DeltaSignal issuer universe. It server-enforces the pressure-board call plan: readiness, top_stressed with limit 15, and risk_distribution. Parameters: optional output_mode=compact only; do not pass limit, offset, ticker, source_date, or issuer filters because this preset owns exact arguments internally. Behavior: read-only and idempotent; it performs three internal HTTPS reads, has no destructive side effects, never calls issuer-level tools, and preserves partial results if one internal call fails. Use it when the user asks for risk monitoring, pressure board, stress board, top stressed overview, or current risk mix.
    Connector
  • PREFERRED chart-creation path. Send a structured Builder spec (chart_type + x_col + y_col[s] + optional group_by, palette, axis overrides, annotations) and Autario builds the chart with the same templates the Builder UI uses. Brand attribution (publisher source + autario.com) is applied automatically and cannot be overridden. Insight must cite numbers verifiable against the data | hallucinated numbers return 422 with the available anchor list. For advanced use cases the Builder cannot express, fall back to publish_chart with a freeform plotly_spec. Call chart_instructions() first if unsure of the spec shape.
    Connector
  • Hosted-safe unsigned builder for create_escrow_v2. Use this from hosted SAP MCP, preview the result, then call local sap_payments_finalize_transaction with submit:true. The depositorWallet signs locally; keypair bytes never leave the user machine. Defaults to DisputeWindow settlementSecurity=2 and rejects SelfReport/0. SAP MCP context: Hosted-safe unsigned Escrow V2 builder. The output is not submitted and is not signed by hosted SAP MCP. Preview it, then call local sap_payments_finalize_transaction with submit:true and confirm:true. Never create temporary signing scripts or read keypair JSON. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: hosted-safe builder. If a transaction is returned, preview/sign/submit with sap_payments_finalize_transaction; never create temporary signing scripts. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.
    Connector
  • Hosted-safe unsigned builder for close_escrow_v2. The depositor signs locally; the builder refuses to close until balance and pendingAmount are both zero. SAP MCP context: Hosted-safe unsigned Escrow V2 builder. The output is not submitted and is not signed by hosted SAP MCP. Preview it, then call local sap_payments_finalize_transaction with submit:true and confirm:true. Never create temporary signing scripts or read keypair JSON. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: hosted-safe builder. If a transaction is returned, preview/sign/submit with sap_payments_finalize_transaction; never create temporary signing scripts. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.
    Connector
  • Build an unsigned native SOL transfer transaction using SystemProgram.transfer. Returns serialized base64 transaction for the agent to sign locally with sap_payments_finalize_transaction or sap_sign_transaction → sap_submit_signed_transaction. This is the hosted-safe equivalent of spl-token_transferSol (which is local-signer-only and cannot run on the hosted accountless server). Builder fee applies. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • ⚠️ IRREVERSIBLE in Core + Builder FS — kills the running MCP process, unregisters from skill registry, deletes the Mongo record, drops from solution.skills[] and solution.linked_skills, and removes the skill's files from Builder FS. REQUIRES `confirm:true`. RECOVERY: the skill still lives in GitHub — `ateam_github_pull` rebuilds the whole solution (no per-skill restore path).
    Connector
  • Check that the Builder filesystem state and GitHub state are in sync for a solution. Read-only probe — does NOT trigger a deploy. Returns: • ok: true + drifts: [] if everything matches • ok: false + drifts: [{path, kind}] listing files that differ (kinds: fs_missing, gh_missing, content_differs) Drift can creep in when GitHub writes happen but Builder FS doesn't get the mirror update (network blip, container restart mid-write). Boot sync heals most of it on next backend restart; this tool surfaces drift earlier. Run after a series of ateam_github_patch calls to confirm the Builder backend is consistent with GitHub before you ateam_build_and_run.
    Connector
  • Load earnings workflow for EPS surprises, beat/miss, estimates, revenue. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks about earnings results, EPS surprises, beat/miss history, "did X beat estimates", quarterly earnings, revenue growth trends, earnings season, or estimates vs actuals. Can be combined with other workflow tools.
    Connector
  • Use this read-only monitoring tool to retrieve the latest meaningful DeltaSignal daily change snapshot. It highlights tracked crypto filing deltas, newly discovered crypto issuers, source dates, computed timestamps, classification summary, and change statistics. Parameters: none; call it exactly as-is when the user asks what changed today or needs a monitoring summary. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write notifications, files, accounts, or wallet state. Use it for daily monitoring and freshness narratives; use readiness for service health and issuer-specific tools for detailed research on any ticker it mentions.
    Connector
  • Use after explicit user intent to unpublish a Dreamlit workflow. Side effect: disables live triggers or schedules for that workflow and stops future automated sends. Returns updated workflow status and app URLs. Do not use for deleting drafts, canceling one broadcast run, or editing workflow content.
    Connector
  • List all television stations available for TV search with their market, network, monitoring start date, and monitoring end date. Stations with an end date within the last 24 hours are flagged as active; stations with earlier end dates are discontinued. Use before querying to verify a station was active during the target time period, or to discover valid station IDs for the stations parameter in other TV tools. Most station monitoring ended October 2024 when the Internet Archive TV feed stopped updating.
    Connector
  • Execute a signed swap transaction obtained from getOrder and receive execution status. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.
    Connector
  • Export a session as a structured calendar artifact preserving session_id and per-story story_id traceability. Use after a niche_signal_scan when you want a metadata-rich content backlog instead of running individual pieces end-to-end. Outputs a standard editorial-calendar shape suitable for content-backlog and planning workflows. Two formats: • markdown: human-readable and agent-citable. Session metadata at top (session_id, niche, scan timestamp, and brand_profile_active state). Then a card per story with title, headline_candidate, summary, recency_score, publication_breakdown, source_breakdown, and empty slots for the user to fill (Frame, Hook, Article-shape, Ship Order). Followed by a 'recommended ship order' section and cross-cutting notes. • json: structured shape ready to pipe to other tools or load into a notebook. Same data, machine-shaped. Preserves story_id and session_id traceability so you can come back in N weeks and re-run niche_angle_propose / niche_draft_create against the same stories with the same brand profile bound. The artifact is the entry point to a calendar-builder workflow.
    Connector
  • Use this read-only monitoring tool to retrieve the latest meaningful DeltaSignal daily change snapshot. It highlights tracked crypto filing deltas, newly discovered crypto issuers, source dates, computed timestamps, classification summary, and change statistics. Parameters: none; call it exactly as-is when the user asks what changed today or needs a monitoring summary. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write notifications, files, accounts, or wallet state. Use it for daily monitoring and freshness narratives; use readiness for service health and issuer-specific tools for detailed research on any ticker it mentions.
    Connector
  • Start a new heart-shaped route for a given city. Returns existing AI-validated matches from inventory PLUS a deep-link to the live builder for an on-demand fresh generation with the user's exact dedication and cause. Use when the user explicitly wants a NEW heart, or when an existing match is "close enough but not personal yet". Optional dedication / cause_url pre-fill the builder fields, so the URL deep-link arrives configured.
    Connector
  • Hosted-safe unsigned builder for finalize_settlement. Use after the dispute window has elapsed and a pending settlement exists; any payerWallet can locally sign to crank finalization. SAP MCP context: Hosted-safe unsigned Escrow V2 builder. The output is not submitted and is not signed by hosted SAP MCP. Preview it, then call local sap_payments_finalize_transaction with submit:true and confirm:true. Never create temporary signing scripts or read keypair JSON. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: hosted-safe builder. If a transaction is returned, preview/sign/submit with sap_payments_finalize_transaction; never create temporary signing scripts. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.
    Connector
  • Local-signer-only direct withdrawal from a V2 escrow. Hosted users should call sap_escrow_build_withdraw_transaction and finalize locally. SAP MCP context: Payment and settlement flow. Estimate or fetch state before creating escrows or settling calls; write operations require an enabled signer mode and MCP policy approval. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.
    Connector
  • Get the best Ethereum block builder for MEV bundle submission RIGHT NOW based on live relay acceptance rate and submission volume. Returns the top recommended builder name and acceptance percentage. Full ranked builder list with telemetry available at /intelligence/builder-recommendation with x402 payment ($0.25).
    Connector
  • Returns guidance on diagram-creation workflow and tool selection: how to choose between Mermaid and manual element creation, and the recommended iteration workflow. Consult before building complex diagrams.
    Connector