Skip to main content
Glama
742,988 tools. Updated 2026-11-04 18:29

"C# Azure .NET development assistance" matching MCP tools:

  • Submits an approval request of any supported type: UAT_PROMOTION, UAT_SIGN_OFF, PRODUCTION_PROMOTION, VISIBILITY_CHANGE, OWNERSHIP_TRANSFER, RETIREMENT, DOMAIN_CHANGE, or ROLLBACK. **An agent may submit but never decide**: SpringRoll requires a human approver, and an agent token cannot approve its own request. Confirm with the user before calling this. It creates review work for named people. Type-specific behaviour: • `PRODUCTION_PROMOTION`: this does NOT deploy. It asks. `releaseId` defaults to the application's latest release, and `targetEnvironmentType` to 'production'. Once approved, call springroll.deploy.promote. • `UAT_PROMOTION`: `targetEnvironmentType` is required, 'uat' (or 'development' where Development needs approval). An approval only unlocks the environment it names. • `UAT_SIGN_OFF`: `targetEnvironmentType` defaults to 'uat'. • `ROLLBACK`: `justification` and `targetEnvironmentType` (the environment to roll back) are required. Put the deployment to restore in `payload.targetDeploymentId`; it defaults to the last successful one. • `RETIREMENT`: `justification` is required. • Every other type takes no `targetEnvironmentType`.
    ConnectorNo auth
  • WHEN: at the START of any release-note / upgrade-impact conversation -- call this BEFORE list_release_note_inputs to check whether a Client Profile already exists for the CURRENT caller's Azure DevOps org/project (auto-detected from DEVOPS_ORG_URL/DEVOPS_PROJECT MCP headers -- you don't pass anything). If found, it gives you the client's currentVersionTag, targetVersionTag, customModelIds (their own extensions AND any attached ISV/vendor models) and the latest diff snapshot in one call -- use those directly as v1/v2/customModelIds for prepare_release_note_context, no further discovery needed. If not found, fall back to list_release_note_inputs and/or save_client_profile.
    ConnectorNo auth
  • Run the classic operations-research teaching demo: pooled queueing (one shared queue, c servers) vs separate queues (c independent queues, one server each, λ/c traffic to each). Both runs have identical total capacity (c × μ) and identical total arrivals (λ), so the offered load ρ is the same; the only structural difference is whether arrivals share a queue or split into c isolated streams. The pooled configuration ALWAYS produces shorter waits — that's the whole teaching point. Use this when the user asks 'should we pool our resources?' / 'should we cross-train?' / 'why do banks have one line instead of c?' / 'what's the cost of siloing my call center into specialist queues?'. Returns both runs side by side with the pooled-vs-separate wait delta. ANTI-FABRICATION: numbers come from two real DES runs. Quote them VERBATIM.
    ConnectorNo auth
  • Run the same M/M/c configuration through BOTH the closed-form Erlang-C formula AND the discrete-event simulator, returning a side-by-side comparison with deltas. Use this when the user is validating QueueSim's engine against textbook values, learning queueing theory by watching simulation converge on the formula, or auditing a result that 'feels off' — agreement within ~5%% is the canonical sanity check for an M/M/c run. Pure-Exponential M/M/c only; the closed-form Erlang-C is undefined for other service distributions. Large deltas usually mean the simulation run was too short for steady-state — raise simulationDays. ANTI-FABRICATION: both sides come from real computation — closed-form is deterministic, simulation is stochastic but engine-backed. Quote both verbatim. Do not synthesize an 'average of the two' or recompute the formula from training-data recall.
    ConnectorNo auth
  • 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.
    ConnectorNo auth
  • Compute the gross price to charge so you net a target after fees. FREE. 'Charge X to receive Y' after percentage + fixed processor fees. Typical input {"net_target": 100, "pct_fee": 2.9, "fixed_fee": 0.30} returns {"charge": 103.4, "fee": 3.4, "net": 100.0}. The inverse of processor_fees - solves for gross from a target net. Use when the payout is the fixed requirement. Not when the price is already set. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "net_target > 0 and pct_fee < 100 required"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    A
    quality
    B
    maintenance
    Enables web search and anonymous public-page retrieval through MCP, with provider-neutral selection, bounded plain-text results, and built-in auditing.
    2
    -

Matching MCP Connectors

  • The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.

  • Connect your AI to your own devices, 3D printers, factory tools and a shared agent task pool.

  • Compute the gross price to charge so you net a target after fees. FREE. 'Charge X to receive Y' after percentage + fixed processor fees. Typical input {"net_target": 100, "pct_fee": 2.9, "fixed_fee": 0.30} returns {"charge": 103.4, "fee": 3.4, "net": 100.0}. The inverse of processor_fees - solves for gross from a target net. Use when the payout is the fixed requirement. Not when the price is already set. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "net_target > 0 and pct_fee < 100 required"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • List open times on Upforge's calendar for a free consultation (usually 30 minutes), in the person's own timezone. Call this before book_consultation and let the person pick a time; never pick one for them. Meeting types come live from the scheduler: general-inquiry is the default, and service types such as web-design, application-development or ai-automation route to the right person. Bookings need about a day's notice, so the search starts tomorrow.
    ConnectorNo auth
  • Get counts of NSW complying development certificates (CDCs) by status, application type and council. Call it before nsw_cdc_search_applications or nsw_cdc_search_nearby_applications: it returns the total loaded and by_status, by_application_type and by_council lists of { key, count }, whose keys are the exact filter values those tools accept. Filters are optional and combine with AND; without them the counts cover all of NSW. Counts refresh every 6 hours while the history backfill extends coverage back to 2021. Free, no payment needed. Source: NSW Department of Planning, Housing and Infrastructure (NSW Planning Portal), CC BY 4.0.
    ConnectorNo auth
  • Specialist tasks that one agent has commissioned from another and that no provider has taken yet: data integrity, research replication, measurement analysis, method documentation, interoperability testing. Each lists the deliverable, the price in NET, who will judge the result, and the deadline, so a provider can decide before agreeing. Reading a task commits nobody; a provider agrees to the exact NET amount separately, and nobody is paid in NET by default. Free, keyless, read-only, moves no money. Cost and signer: free and keyless, nothing to sign.
    ConnectorNo auth
  • Prices a given number of inboxes at WarmInboxes' published prices: the domains (or Azure tenants) they sit on, daily sending capacity at the provider's pace, monthly cost and delivery time. Use it when the person already knows the count ("preview 100 inboxes"); for a send volume use plan_infrastructure. Azure is sold by the tenant, so a count that does not fill one is quoted for the tenants it needs, with a note. A quote only: it orders nothing, and the exact preview with real domain and mailbox names is in the app or on WarmInboxes Infrastructure MCP.
    ConnectorNo auth
  • Listet die Rennen des Athleten mit Prioritaet (A/B/C), Format, Distanzen, Hoehenmetern, Zielzeit und Status. **Standard: die kommenden Rennen**, naechstes zuerst. include_past: true zeigt auch vergangene — dort heisst status PLANNED "kein Ergebnis erfasst", nicht "verpasst". A-Rennen sind die Saisonziele, auf die ein Plan zielt; B-Rennen ernsthafte Formtests, C-Rennen Trainingswettkaempfe. Dieselbe Tabelle wie der Rennplaner der App. training_profile nennt das naechste A-Rennen, training_plan_list markiert Renntage. Args: - id (string, optional): genau ein Rennen; schlaegt alle Filter - from / to (string, optional): Fenster YYYY-MM-DD, Kalendertage des Athleten - include_past (boolean, default false): auch vergangene Rennen - priority (string, optional): A | B | C - limit (number): 1-100, default 20 Returns: { count, has_more, items: [{ id, name, date, start_time, days_until, location, sport, format, draft_legal, swim_km, bike_km, run_km, total_km, bike_elevation_m, run_elevation_m, course_elevation_m, priority, goal_time, goal_time_sec, personal_goal, notes, status, activity_id, result_time, goal_splits: { swim, t1, bike, t2, run }, swim_water_temp_c, checkpoints: [{ name, date_from, date_to, targets: { css, ftp, run_threshold_pace } }] }] } checkpoints tragen css und run_threshold_pace in Sekunden (je 100 m bzw. km), ftp in Watt. Soll-Ist und Rennprognose liefert training_race_prognosis.
    ConnectorOAuth
  • Projects net worth trajectory spanning past history and future forecast. Returns historical trend, forecast projection, growth metrics, and milestone projections (auto-detected or user-specified). Uses the user-level balances endpoint which aggregates ALL accounts (not just those marked is_net_worth). Growth metrics use simple average monthly change (not CAGR) to handle net worth crossing zero correctly. Milestones apply to TOTAL net worth only — for a single account reaching a target balance (e.g. an emergency fund hitting $10k) use cash_flow_forecast with account_ids instead. Subscription plan limits may restrict the available date range. navigate_to_net_worth is the matching page link to offer alongside an answer.
    ConnectorOAuth
  • Projects net worth trajectory spanning past history and future forecast. Returns historical trend, forecast projection, growth metrics, and milestone projections (auto-detected or user-specified). Uses the user-level balances endpoint which aggregates ALL accounts (not just those marked is_net_worth). Growth metrics use simple average monthly change (not CAGR) to handle net worth crossing zero correctly. Milestones apply to TOTAL net worth only — for a single account reaching a target balance (e.g. an emergency fund hitting $10k) use cash_flow_forecast with account_ids instead. Subscription plan limits may restrict the available date range. navigate_to_net_worth is the matching page link to offer alongside an answer.
    ConnectorOAuth
  • Given an M/M/c configuration (arrivalRate, serviceRate, servers) and optionally an observed average wait, returns a queueing-theory framed interpretation: where you sit on the utilization curve, what ρ means in plain language, what one more or fewer server would qualitatively do, and which complexity factors (priority, abandonment, skills routing) might be hiding in real data the M/M/c model can't see. Use this to TEACH while answering — when the user wants context around a number, not just the number itself. Pure text computation, no simulation, no RNG — deterministic output.
    ConnectorNo auth
  • Update an existing identity: description and tags (removeTagKeys drops tags), its cloud-identity blocks (aws, gcp, azure, ngs; each replaces the stored block, and removeCloudIdentities detaches the ones it names), networkResources and nativeNetworkResources (each replaces the whole array), and the SpiceDB and memcache access lists. Provider blocks can modify real resources in the connected cloud account, including AWS IAM roles, GCP service accounts, and Azure managed identities. A new identity: create_identity. Giving one workload AWS, GCP, or Azure access: grant_cloud_access.
    Connector
    Destructive
    OAuth
  • Break down payment-processor fees: fee, net, and effective rate. FREE. Uses editable presets for stripe/paypal/square/shopify (verify current rates) or your own custom_pct + custom_fixed. Typical input {"amount": 1000, "processor": "stripe", "transactions": 10} returns {"gross": 1000, "fee": 32.0, "net": 968.0, "effective_rate_pct": 3.2, "note": "..."}. Use when the charge amount is known and the net payout is the question. Not for the reverse: the gross needed to net a target is charge_to_net. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "amount must be > 0, transactions >= 1"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • Break down payment-processor fees: fee, net, and effective rate. FREE. Uses editable presets for stripe/paypal/square/shopify (verify current rates) or your own custom_pct + custom_fixed. Typical input {"amount": 1000, "processor": "stripe", "transactions": 10} returns {"gross": 1000, "fee": 32.0, "net": 968.0, "effective_rate_pct": 3.2, "note": "..."}. Use when the charge amount is known and the net payout is the question. Not for the reverse: the gross needed to net a target is charge_to_net. Errors: on invalid, missing, or malformed input this tool never raises a protocol error; it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "amount must be > 0, transactions >= 1"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • AZURE DEVOPS ONLY -- Query Work Items (Bugs, Tasks, FDDs, User Stories, CRs) in Azure DevOps. [~] PRIORITY TRIGGER: use this tool when the user mentions 'FDD', 'RDD', 'IDD', 'CR', 'Task', 'Workitem', 'Work Item', 'Bug', 'User Story', 'Feature', 'Issue', 'ticket', 'sprint', 'backlog', 'DevOps', 'liste des tâches', 'show tasks', 'find bugs', '#1234', 'WI#'. NEVER use this tool for: D365 labels (@SYS/@TRX), X++ code, AOT objects, tables, classes, forms, enums, error messages, 'c\'est quoi le label', 'search_labels', 'libellé', 'label D365'. For labels -> use search_labels. For D365 code -> use search_d365_code or get_object_details. Shortcuts: 'bugs' (all active bugs), 'my bugs' (assigned to me), 'recent' (updated last 7 days), 'sprint' (current iteration). Or pass any WIQL SELECT statement or a free-text title search. Use '*' with filters only. Returns max 50 work items with ID, title, type, state, priority, area, assigned-to. Requires DEVOPS_ORG_URL + DEVOPS_PAT env vars.
    ConnectorNo auth
  • Securely register the D365 F&O environment's Application Insights / Log Analytics connection for the CURRENT session. The client secret is encrypted in memory (AES-256-GCM), never written to disk and never echoed back. Once set, appinsights_query and appinsights_diagnose_slowness use it automatically until it expires or you call appinsights_clear_connection. HOW TO GET THE VALUES: workspaceId -- the Log Analytics WORKSPACE ID (GUID, not the App Insights app id) behind the Application Insights resource the environment is linked to (D365FO: System administration > Monitoring and Telemetry parameters > Application Insights Registry tab shows the connection string; the workspace id is on that Log Analytics workspace resource's Overview blade in the Azure Portal). tenantId/clientId/clientSecret -- an Entra ID app registration granted the 'Log Analytics Reader' (or 'Monitoring Reader') role on that workspace resource (Azure Portal > workspace > Access control (IAM) > Add role assignment). Read-only -- no write access is ever needed or used. In a locked server deployment (APPINSIGHTS_LOCK_SERVER_CONFIG=true) this tool is disabled and the server's own environment credentials are used instead.
    ConnectorNo auth
  • Submits an enquiry to Development Exit Finance — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three commercial mortgage and business finance brokers, chosen by Development Exit Finance, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
    ConnectorNo auth