The MCP tool directory.

Delete an existing Recruit role and transfer users to another role

Retrieve details of a specific Recruit role by its identifier

Retrieve a list of all Recruit roles in the organization

Update multiple Recruit roles in the organization

Update an existing Recruit role with new information

Search for code snippets and examples in official Microsoft Learn documentation. This tool retrieves relevant code samples from Microsoft documentation pages providing developers with practical implementation examples and best practices for Microsoft/Azure products and services related coding tasks. This tool will help you use the **LATEST OFFICIAL** code snippets to empower coding capabilities. ## When to Use This Tool - When you are going to provide sample Microsoft/Azure related code snippets in your answers. - When you are **generating any Microsoft/Azure related code**. ## Usage Pattern Input a descriptive query, or SDK/class/method name to retrieve related code samples. The optional parameter `language` can help to filter results. Eligible values for `language` parameter include: csharp javascript typescript python powershell azurecli al sql java kusto cpp go rust ruby php

Fetch and convert a Microsoft Learn documentation page to markdown format. This tool retrieves the latest complete content of Microsoft documentation pages 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 link from the microsoft.com domain. ## Output Format markdown with headings, code blocks, tables, and links preserved.

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. The `question` parameter is no longer used, use `query` instead. ## 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.

Mint a free trial API key for this session, when you don't already have one. This tool only appears while the session has no API key configured -- once a key is set, it drops off the tool list, so seeing it here IS the signal that you need it. Takes no parameters. Minting is anonymous: it issues an API key, not a user account -- no signup, no email, no card, no identity attached. The key works immediately on the free tier, which stays the same small per-IP daily budget whether or not you mint. Minting does NOT authenticate the current session: the session stays un-keyed until the client reconnects with the returned key in its Authorization header, so the result explains how to persist the key, not how to keep going in this transcript. If you cannot edit the client config yourself, return the key and setup snippet to the user so they can paste it and reconnect. After minting, do not call this tool again -- configure the key at the transport layer and use the data tools once reconnected. Returns the key itself (shown once) plus setup instructions; it never returns platform data.

Read or update conversion notes with explicit required key names. How to use: - Call without `conversion_notes` to inspect current notes. - For updates, provide all three canonical keys for consistency. Expected keys (string values): - `Product Name` - `Payment Terms/Plans` - `General Notes`

Read or replace funnels with explicit shape validation. How to use: - Call without `funnels` to inspect current funnel list. - Update is replace-style: provide the full intended funnels list. Expected item shape: - `url` (string) - `description` (string) - `primary_use_case` (string) - `qualification` (optional string)

Read or update keyword targeting with optional search parameters. How to use: - Call without `keywords` to inspect current keywords config. - Update writes explicit keyword list and optional search params. Expected payload shape: - `keywords`: list[str] - `search_params` (optional): - `sort`: one of `relevance|hot|top|new|comments` - `time_filter`: one of `hour|day|week|month|year|all` - `per_keyword_limit`: int

Read or update market positioning with explicit format guidance. How to use: - Call without `market_position_patch` to inspect current data before editing. - Send only keys you want to change (patch semantics). Expected patch keys (string values): - `one_line_pitch` - `icp` - `competitive_alternatives` - `uniqueness` - `value_proof` - `market_category` - `trends` - `additional_info`

Read or update subreddit targeting groups. How to use: - Call without `subreddit_groups` to inspect current targeting. - Update expects `groups` format used by onboard API targeting endpoint. Expected `subreddit_groups` item shape: - `subreddits`: list of subreddit names (without `r/` prefix preferred).

Request a custom analysis module to be built for your use case.

Create a new namespace with a server-generated human-readable name, owned by the authenticated user

Delete a namespace owned by the authenticated user. The namespace must not contain any servers. Skills and connections in the namespace will be deleted automatically.

When called without query params, returns the authenticated user's namespaces (backwards compatible). When query params are provided, searches public namespaces with pagination. Use ownerId to filter by owner, hasServers/hasSkills to filter by content, q for text search.

Create a new namespace owned by the authenticated user or an organization. This endpoint is idempotent - if the namespace already exists and is owned by the user/org, returns success. Pass organizationId in the request body to create an org-owned namespace.

Retrieve NFT tokens (ERC-721, ERC-404, ERC-1155) owned by an address, grouped by collection. Provides collection details (type, address, name, symbol, total supply, holder count) and individual token instance data (ID, name, description, external URL, metadata attributes). Essential for a detailed overview of an address's digital collectibles and their associated collection data. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.

Get the latest daily brief — the most recently generated plain-language summary of what happened overnight across your watched items. Read-only; never triggers fresh AI generation.

Get overall health across every watched item — total count, counts by dashboard bucket (needs_help, needs_a_look, fine, waiting), overall status, last check time, and a plain-language one-liner. Counts use the same display-status precedence as the dashboard, so `needs_help` excludes never-pinged or unreachable items that still carry stale raw-red status.

Get full details for one watched item: schedule, recent activity, error history, and next expected run. `last_error_message` is the most recent error string seen, regardless of current status; use `last_error_state` ("current" or "resolved") to tell whether it's the current problem or already cleared. Both are nil when the watch has never errored.

List event history across your watched items — filter by watch, by event type, or pass `event_id` to fetch a single event in full detail. Event types span the full range NoCrash watches for: routine check-ins, failures, recoveries, missed runs, silent step-level breakage, workflow on/off changes upstream, and browser-side errors from vibe-coded apps (script crashes, unhandled promise rejections, failed network calls, page loads).

List every watched item with its current status (green/yellow/red), optionally filtered by status. Also returns an overall health summary using the same display buckets (needs_help, needs_a_look, fine, waiting) the dashboard and nocrash_get_health show, so totals never contradict across tools. Each watch includes `last_error_message` (most recent error seen, regardless of current status) and `last_error_state` ("current" or "resolved"); both are nil when the watch has never errored.

Force a fresh check of a watched item now instead of waiting for the next scheduled poll. Shares the dashboard refresh cooldown — 60-second wait between refreshes and a 10-per-hour ceiling per connection. Push-based watches (JS snippet) update on their own when data arrives and can't be refreshed on demand. The refresh runs asynchronously, so the new status appears on the item a few seconds later.

Report that a workflow failed. Records the error and updates the watched item's status. Include as much detail as possible — error message, failing step, and any context an agent or human will need to debug.

Search every error event by keyword. Matches against error messages, failing node names, plain-language error context, and AI-suggested fixes across all your watched items.

Send a heartbeat for a watched item to confirm the workflow is running. This is a write — it resets the failure count and updates status to green.

Creates one or more note records.