Skip to main content
Glama
205,114 tools. Last updated 2026-06-16 04:11

"Microsoft Azure Cloud Services" matching MCP tools:

  • Cloud- and night-independent Sentinel-1 C-band confirmation of forest disturbance. Intact forest scatters VV strongly + stably (canopy volume scattering); clearing collapses that term so VV backscatter DROPS ~3-5 dB. Samples VV at a baseline-year July-1 anchor and the latest scene, reports `vv_drop_db = baseline − recent` and a `disturbed` flag when the drop ≥ 3 dB (Reiche et al. 2018, RSE 204:147). Both VV reads are signed Primary facts; the response cites both fact_cids. Honest `inconclusive` when either S1 vintage is unavailable. Source: Microsoft Planetary Computer sentinel-1-rtc (anonymous SAS — no requester-pays, no API key). When to use: Call to corroborate or scout forest clearing where cloud blocks the optical products — radar sees through cloud and at night, catching wet-season clearing the annual Hansen/JRC-TMF layers and a single cloudy Sentinel-2 pass miss (the gap RADD was meant to fill). This is an ADDITIVE scout signal, NOT a standalone legal verdict: a VV drop can also be transient (soil moisture, harvest, flood recession), so confirm with the optical consensus (`emem_eudr_dds` or `emem_deforestation_alert`) before crediting a decision.
    Connector
  • Use this read-only resolver tool to load a TF-SUB article/narrative research object from the TrendForge Azure Blob resolver lake. Parameters: tripcode is required and must be a proprietary DeltaSignal article resolver key such as TF-SUB-DA79A58372. Behavior: idempotent and read-only with no destructive side effects; it does not mutate Azure Blob, Substack, filings, wallets, or account state. Use this when a subscriber gives Codex or Claude Code a TripCode from an article subtitle and asks for the machine-readable research object behind the article.
    Connector
  • Checks whether a task can be handled by a local model instead of a cloud API. Call this BEFORE your agent routes any task to a cloud model — at the moment a task is ready to be sent and the model has not yet been selected. Use this when your agent is about to make a cloud inference call and wants to determine whether a local model could handle it at lower cost. Returns LOCAL/CLOUD/EITHER verdict with recommended model. If verdict is LOCAL, skip the cloud call entirely — saves cost on every routable inference call. Pass data_sensitivity=CONFIDENTIAL to force LOCAL verdict for tasks that must not leave the machine. Do not route to cloud without checking local viability first.
    Connector
  • Use this read-only tool to check whether the Azure-native ATLAS-7 full-universe regression audit is healthy. It reads the latest audit summary artifact from Azure Blob and reports last successful run time, issuer count, operation count, failure counts, historical route status, composite route status, and artifact prefix. Parameters: none. Behavior: read-only and idempotent; it has no destructive side effects, does not run the audit, mutate data, or access raw issuer evidence. Use this before trusting historical ATLAS-7 surfaces in an agent workflow or when an operator asks whether the nightly 215-issuer audit is current.
    Connector
  • Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.
    Connector
  • List Parallax’s services with real pricing. Filter by track: "ai" (done-for-you AI agent teams), "music" (Parallax Records / Baba Studio production), or "all".
    Connector

Matching MCP Servers

Matching MCP Connectors

  • List all available diagram providers (aws, gcp, azure, k8s, onprem, etc.). Use list_providers -> list_services -> list_nodes to browse available node types for a specific provider.
    Connector
  • Use this read-only resolver tool to load a TF-SUB article/narrative research object from the TrendForge Azure Blob resolver lake. Parameters: tripcode is required and must be a proprietary DeltaSignal article resolver key such as TF-SUB-DA79A58372. Behavior: idempotent and read-only with no destructive side effects; it does not mutate Azure Blob, Substack, filings, wallets, or account state. Use this when a subscriber gives Codex or Claude Code a TripCode from an article subtitle and asks for the machine-readable research object behind the article.
    Connector
  • Submits a demo request. A human at A Cloud Frontier will follow up by email. Use only with the prospect's explicit consent.
    Connector
  • Search Redpanda API reference documentation by keyword. Returns up to 20 matching endpoints, schemas, or topics with URL, title, and text excerpts. SCOPING (important for accurate results): - api="all" or omit: Search across ALL APIs at once - useful when unsure which API contains the endpoint - api="admin": Search only cluster management (brokers, partitions, configs, users, maintenance) - api="cloud-controlplane": Search only Cloud resource management (clusters, networks, namespaces) - api="cloud-dataplane": Search only Cloud data operations (topics, ACLs, connectors) - api="http-proxy": Search only HTTP Proxy (produce, consume, offsets over HTTP) - api="schema-registry": Search only Schema Registry (register, retrieve, compatibility) WHEN TO USE WHICH: - User asks "broker endpoints" → api="admin" (brokers are cluster management) - User asks "create topic API" → api="all" (topics exist in admin AND cloud-dataplane) - User asks "Cloud cluster API" → api="cloud-controlplane" - User asks about Redpanda APIs generally → api="all" or omit For general Redpanda questions (not API-specific), use ask_redpanda_question instead.
    Connector
  • Load educational slides or cloud file attachments. Use laminasAnexos for educational slides/laminas (~238 items with PDFs about nutrition topics), cloudAnexos for uploaded cloud files. For guidelines/orientations specifically, use webdiet_orientacoes action=list_banco. Bulk support: accepts patient_ids for batched execution.
    Connector
  • "What's the weather in [city]" / "weather forecast for [location]" / "will it rain tomorrow" / "temperature in [place] this week" / "wind / precipitation / humidity forecast" — global weather forecast up to 16 days ahead, hourly or daily, at any lat/lng. Returns temperature, precipitation, wind, humidity, cloud cover, weather codes by default; pass hourly/daily arg for custom variables. Free, keyless, no signup (Open-Meteo / ECMWF + national weather services). Pair with geocode to convert "Paris" → lat/lng first.
    Connector
  • List pages in Redpanda API reference documentation. Returns endpoints, schemas, and topic pages with URL, title, type, and description. SCOPING (important for accurate results): - api="all" or omit: Lists all available APIs - api="admin": Cluster management operations (brokers, partitions, configs, users) - api="cloud-controlplane": Redpanda Cloud resource management (clusters, networks, namespaces) - api="cloud-dataplane": Cloud cluster data operations (topics, ACLs, connectors) - api="http-proxy": Kafka operations over HTTP (produce, consume, offsets) - api="schema-registry": Schema management (register, retrieve, compatibility) Use this to browse API structure. For general Redpanda docs, use ask_redpanda_question instead.
    Connector
  • Upload local contexts to the GitWhy cloud as private (not shared with team). Use after saving contexts locally to back them up to the cloud. Synced contexts remain private until explicitly published with gitwhy_publish. CLI alternative: `git why push <context-id>` (syncs specified contexts as private).
    Connector
  • [IN DEVELOPMENT] [READ] Aggregated list of paid services swarm.tips agents can spend on. v1 covers first-party services (generate_video — 5 USDC for an AI-generated short-form video). External spend sources (Chutes inference at llm.chutes.ai/v1, x402-paywalled APIs, etc.) are deferred to follow-up integrations. Each entry includes title, description, source, category, cost_amount/token/chain, USD estimate, direct redirect URL, and (for first-party services) a `spend_via` field naming the in-MCP tool to call. Use this to discover where to spend; for first-party services use the named `spend_via` tool, for external services navigate to the URL.
    Connector
  • Fetch currently open government contract solicitations matching a keyword. Read-only. No side effects. Idempotent. keyword: Description of goods or services sought e.g. cloud computing services. Required. Encode special characters — + becomes %2B. agency: Awarding agency name. Optional, defaults to all agencies. jurisdiction: One of US, EU, or UK. Optional. Default US. Returns solicitation title, agency, response deadline, estimated value, and NAICS code. Use this when looking for active bid opportunities. Use govcon_search_contract_awards instead when you need historical awards not open solicitations. Verified source: SAM.gov + USASpending.gov. 4-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="govcon_fetch_open_solicitations", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}".
    Connector
  • Live up/down/degraded status for major AI & dev services (OpenAI, Anthropic, GitHub, Cloudflare, etc.). Use this to answer "is X up right now?". Services with issues are listed first. Args: category: filter by ai | dev | infra | platform. only_issues: only return services currently degraded or down. limit: max results. Envelope: measured_at = when the freshest status row was last probed (each row's `updated_at`); max_age 300s matches the ~5-min probe cadence, so freshness is honest live/stale.
    Connector
  • Use this read-only tool to check whether the Azure-native ATLAS-7 full-universe regression audit is healthy. It reads the latest audit summary artifact from Azure Blob and reports last successful run time, issuer count, operation count, failure counts, historical route status, composite route status, and artifact prefix. Parameters: none. Behavior: read-only and idempotent; it has no destructive side effects, does not run the audit, mutate data, or access raw issuer evidence. Use this before trusting historical ATLAS-7 surfaces in an agent workflow or when an operator asks whether the nightly 215-issuer audit is current.
    Connector
  • Search official Microsoft/Azure documentation to find the most relevant and trustworthy content for a user's query. This tool returns up to 10 high-quality content chunks (each max 500 tokens), extracted from Microsoft Learn and other official sources. Each result includes the article title, URL, and a self-contained content excerpt optimized for fast retrieval and reasoning. Always use this tool to quickly ground your answers in accurate, first-party Microsoft/Azure knowledge. ## Follow-up Pattern To ensure completeness, use microsoft_docs_fetch when high-value pages are identified by search. The fetch tool complements search by providing the full detail. This is a required step for comprehensive results.
    Connector