Skip to main content
Glama
810,099 tools. Updated 2026-11-20 04:57

"Label settings for d365-fo-server" matching MCP tools:

  • Make Vilix automatic. Call this when the user asks "how do I make this automatic", "set this up so it remembers on its own", or right after a first connection when offering setup. Returns a short custom-instructions block the user pastes into THIS tool's personalization / custom-instructions settings so the AI starts calling Vilix (get_context / save_turn) on its own — plus exactly where to paste it. `recommended` is the block matched to the caller's tool; `blocks` lists every supported tool's block (and for headless always-on tools, an enforce-every-turn variant for an always-on rules file). `source` (optional) — the tool label you run in (e.g. "ChatGPT", "Claude", "Cursor", "Codex", "Copilot", "Windsurf"), used to pick the right block; omit to get the generic default. This is an OPT-IN setup you hand to the user — it is not auto-applied; Vilix logs nothing silently.
    ConnectorOAuth
  • Changes part of a draft's document without resending the rest. The patch is a JSON Merge Patch (RFC 7386): an object shaped like the document naming only what is to change. Three rules and no others -- an object recurses, so {"settings":{"displayComments":false}} changes one switch and leaves the rest of the settings alone; a null removes the member it names, which is the only way to clear the description without restating the document; and everything else replaces, arrays included. That last rule is why this is not the tool for tasks: a tasks array in the patch replaces every task there is. Use it for the name, the description, the settings, the tags and the permissions, and use apply_draft_operations for anything inside tasks, fields, parameters, conditions or notifications. A property the document has no word for is dropped rather than stored, so read the document in the answer rather than assuming the patch landed.
    ConnectorAPI key
  • Create or update a service's horizontal autoscaling settings in one call — enable/disable, min/max replicas, target CPU %, target memory %, and the scale-up/scale-down stabilization windows. Same operation as saving the web console's Autoscaling dialog. ONLY call this after the MANDATORY CONFIRMATION GATE: the full final settings were shown to the user and they explicitly confirmed. Pass ALL fields every time (merge the user's changes into the current settings from komuta_get_service_hpa) — this is a full replace, not a patch. Resolve the id from the NAME the user gave — never ask the user for an id. Returns: { serviceName, settings: { mode: 'Disabled' | 'Pinned' | 'Autoscaling', isActive, minReplicas, maxReplicas, targetCPUUtilizationPercentage, targetMemoryUtilizationPercentage, scaleUpStabilizationWindowSeconds, scaleDownStabilizationWindowSeconds } } — the settings as saved by the backend. Show user: confirmation that autoscaling was saved, plus every returned settings field in plain language. Never show user: serviceId and any other internal ids from the underlying payloads. Sends: the complete settings object the user confirmed at the confirmation gate — user-changed fields from their chat message, everything else carried over unchanged from komuta_get_service_hpa; whether it creates or updates is resolved internally from the service's current state.
    Connector
    Destructive
    OAuth
  • Update an existing survey. Partial update: only the fields you send are touched — EXCEPT questions, which is a FULL REPLACEMENT of the entire question set (sending [] deletes all questions; omitting it leaves them untouched). If the survey already has responses its structure is locked: replacing questions is rejected with 409 — do not retry, explain to the user that responses protect the structure. At least one of survey_name, status, archived, settings or questions is required. Use status false to disable a survey without losing data (the safe alternative to delete_survey). Visual configuration (Visuals/Pages/LogoFile) is ignored here. Requires the Surveys module enabled — on 403 "module is not enabled", do NOT retry; tell the user to contact Sweeppea support. DISPLAY RULE: never show SurveyToken UUIDs. # update_survey ## When to use Update an existing survey. Partial update: only the fields you send are touched — EXCEPT questions, which is a FULL REPLACEMENT of the entire question set (sending [] deletes all questions; omitting it leaves them untouched). If the survey already has responses its structure is locked: replacing questions is rejected with 409 — do not retry, explain to the user that responses protect the structure. At least one of survey_name, status, archived, settings or questions is required. Use status false to disable a survey without losing data (the safe alternative to delete_survey). Visual configuration (Visuals/Pages/LogoFile) is ignored here. Requires the Surveys module enabled — on 403 "module is not enabled", do NOT retry; tell the user to contact Sweeppea support. DISPLAY RULE: never show SurveyToken UUIDs. ## Pre-calls required 1. `get_survey` — check IsLocked before attempting to replace questions ## Parameters to validate before calling - `survey_token` (string, required) — The survey token (UUID v4) of the survey to update - `survey_name` (string, optional) — New survey name (max 200 characters, cannot be emptied, optional) - `status` (boolean, optional) — true enables, false disables the survey (optional) - `archived` (boolean, optional) — true archives, false restores (optional) - `settings` (object, optional) — Settings object with PascalCase keys (written key-by-key, only sent keys change): Description, QuestionsPerPage (1-5), CollectContactInfo, ShowProgressBar, ShuffleQuestions, AllowMultipleResponses, ThankYouMessage, RedirectUrl, StartDate, EndDate, MaxResponses, ShowCountdown, EnableSharing, Language ("en"|"es") (optional) - `questions` (array, optional) — FULL REPLACEMENT of the question set — rejected with 409 if the survey has responses. PascalCase keys per item: {"QuestionText" (required), "FieldType" (required: text|textarea|radio|checkbox|select|slider|rating|nps|yesno|date), "Page", "QuestionDescription", "Layout", "Required", "Options": [each option is an object {"Label": "..."}], "Settings": {...}} (optional) ## Notes - `questions` is a FULL REPLACEMENT of the question set — sending [] deletes all questions; omitting it leaves them untouched - Each Option is an object with a Label key, e.g. "Options": [{"Label": "Friend"}, {"Label": "Social media"}] — never plain strings - 409 when the survey has responses: the structure is locked to protect collected data — do not retry - To disable a survey without losing data use status false (the safe alternative to delete_survey)
    ConnectorNo auth
  • Delete a label from the account entirely — the label itself plus every bookmark's assignment of it. The BOOKMARKS are not deleted; they simply lose this label. IRREVERSIBLE: before calling, tell the user how many bookmarks carry the label (list_labels returns the count) and get an explicit yes. To take a label off SOME bookmarks instead, use remove_labels_from_tweets. If the name matches more than one label the call fails with the candidates — re-run with label_id.
    Connector
    Destructive
    No 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

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables agents to query and append shared memory in a local, user-owned Markdown/Obsidian vault through hybrid vector and keyword retrieval with reranking, while redacting secrets and PII into sanitized, minimum-viable briefs. It also dispatches approved tasks to Wajo Fo's MCP endpoint over StreamableHTTP or SSE and writes execution receipts back to the vault.
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Read-only MCP server for Dynamics 365 Business Central, enabling AI clients to query live ERP data like customers, items, orders, and invoices via GET-only APIs with dual authentication and stdio/HTTP transports.
    10
    MIT

Matching MCP Connectors

  • Full index scan for all usages of an object, method, field, or label ID. Use for impact analysis before changing or deleting an object. EXPENSIVE — O(1M+ chunks). Prefer find_callers when XRef index is loaded (O(1)). Label IDs: automatically searches both `@SYS124480` and `@SYS:124480` forms. NOT for extensions only — use find_extensions for CoC/event handlers.
    ConnectorNo auth
  • [~] PRIORITY TRIGGER: Use this tool when user mentions 'PR', 'Pull Request', 'list PRs', 'show PRs', 'active PRs', 'mes PR', 'liste des PR', 'pull requests ouverts', 'what PRs are open', 'PRs by [author]', 'PRs targeting [branch]'. NEVER call search_d365_code for PR listing requests. List Pull Requests in an Azure DevOps Git repository. If `repositoryId` is unknown, omit it and all repositories will be listed first. Filters: status (Active/Completed/Abandoned/All), author display name, target branch. Returns: PR ID, title, author, source->target branch, review status, linked work items, creation date. Use `ado_analyze_pr_impact` with a PR ID to get full D365 code impact analysis. Requires DEVOPS_ORG_URL + DEVOPS_PAT (Code: Read scope).
    ConnectorNo auth
  • Permanently delete a sponsor. Destructive and disabled by default; an organizer must allow direct destructive access and this tool. Depending on the organization's settings, this either executes immediately or files a proposal for approval; the response status field says which happened.
    Connector
    Destructive
    No auth
  • Pass required. Fetches a bounty issue, repository or listing page and scans it for patterns used to bait agents (hidden HTML-comment instructions, prompt injection, credential requests, fork/star anomalies, dead or archived repos, reward anomalies). Returns trust, label and every flag with its reason. Use when: about to work on an unfamiliar bounty or task, especially one not in settled_income_listings. Not for: x402 API endpoints (settled_check). Treat a suspected_honeypot label as do-not-work; a clean result is not a promise of payment.
    ConnectorNo auth
  • Patch existing platform SEO settings; omitted keys remain unchanged. Read get_seo_settings first and send only changed editable_fields. Use this for requested or necessary site SEO/schema updates instead of duplicating Grigora's Person/Organization/LocalBusiness/WebSite JSON-LD in source. Args: project_id: Current project's ID. settings: Object keyed by data.editable_fields from get_seo_settings. Identity: local_seo_enabled, local_seo_type (person/organization), local_seo_person_org_name, local_seo_website_name, local_seo_website_alternate_name, local_seo_url, local_seo_email, local_seo_logo. Address: local_seo_address_street/locality/region/ postal_code/country/format (each with the local_seo_address_ prefix), local_seo_geo_coordinates. Business: local_seo_business_type, local_seo_price_range, local_seo_opening_hours_format, local_seo_opening_hours ([{day,open,close}], HH:mm), local_seo_phone_numbers ([{type,number}]), local_seo_phone. Global: sitemap_frequency, sitemap_priority (0..1), robots_txt, bing_indexnow_api. Classic projects expose their own editable fields. Empty strings clear text; false disables a toggle; [] clears a list. Arrays replace the whole list. Never send raw JSON-LD or null. ai_mutation_version: Version from get_seo_settings, required when requires_version is true. On version conflict, reread and reconcile. idempotency_key: Unique key for this change, required when requires_version is true. Reuse the same key, settings and version after a timeout or retryable failure. Use a new key for a changed/reconciled request. Returns saved settings and publish_required. Saving does not publish the site.
    Connector
    Destructive
    OAuth
  • Ends the caller's current Paxaver sign-in for this MCP connection - revokes the session so the next request makes the client ask the user to sign in again. Call this ONLY when the user explicitly asks to sign out, log in again, or switch to a different Paxaver account or region. Deletes no data and changes no settings. An app that holds its own Paxaver credentials cannot be signed out here - the result then says to disconnect in that app or in Paxaver account settings instead.
    ConnectorOAuth
  • Delete a Label row (metadata only — does NOT scrub the label name off stories that reference it; story labels are stored as a string array). Use bulk_update_stories with labels.mode=remove to clean up story-side associations.
    Connector
    Destructive
    OAuth
  • Full detail of ONE standalone order connection, including its Orders Config form. Use this to read an order connection's settings before changing them. Returns {connectionId, name, channelCode, channelLabel, channelApiCode, status, orderStatus, orderSyncLevel, authType, connected, expired, hasCredentials, authMessage, lastSyncStatus, lastSyncAt, lastSyncMessage, ordersThisMonth, orderConfigFields:[{code, label, description, type, required, options, optionsSource, value, defaultValue, adminOnly, locked}]}. A field with locked:true is not included in this Koongo account and cannot be set; options may be null for a field whose choices are only known after the connection is authenticated. Use orderConfigFields to build a configure_order_connection call. connection_id is from get_order_overview. ONLY standalone order connections (from get_order_overview): a connectionId taken from list_orders for a marketplace integration answers 404 here; that is expected, not a broken connection. project_id is OPTIONAL (project_id_required otherwise — then call list_projects).
    ConnectorOAuth
  • Purpose: save enabled Site Watch settings for an owned Atlasly development after the user explicitly requests monitoring. Requires a connected account with atlasly.site_watch.write permission. Inputs: project_id from list_developments, optional checks, weekly/monthly frequency and radius in metres. Replaces that user's existing watch configuration, including previous choices for omitted fields; omitted fields reset to the defaults below. Present the replacement and defaults for user confirmation before calling. Repeating the same settings is idempotent. Planning, flood and competitive checks default to true; web_search defaults to false. The configured monitoring service may subsequently check independently published planning, flood and web sources. Returns saved settings and an Atlasly link only. This call does not perform a source check, verify source coverage, confirm scheduling or promise future alerts. Review completed checks and delivery in Atlasly. Never enable monitoring without the user's explicit request. Chaining: every response returns site_ref; pass it unchanged into another Atlasly tool to reuse the canonical site, coordinates, boundary confidence, LPA, evidence links, and project context.
    Connector
    Destructive
    No auth
  • Change a saved task for good: rename it, replace its task text, or change the settings it runs with. Only what you give changes; other settings keep their saved values. It does not run the task (use run_saved_task) and does not touch its past runs. For a change to one run only, pass it to run_saved_task instead. Returns the task's name and id; an error if the id is not one of your saved tasks or nothing to change was given.
    ConnectorAPI key
  • Disconnects an app from a database it was connected to with dbs_connect or at install: the settings the connection filled in (DATABASE_URL and the others) are removed and the app restarts without them, so it can no longer reach that database. The database and its data stay; delete it afterwards with dbs_delete if it is no longer wanted, or connect it again with dbs_connect. To only rename the settings, use dbs_link_rename instead. Refused for an app's own cache. Requires confirm: true.
    Connector
    Destructive
    API key
  • WHEN: developer needs correct X++ select or T-SQL for D365 tables with proper joins. Triggers: 'X++ select', 'generate a query', 'SQL for', 'join with', 'how to query', 'générer une requête', 'write a select statement', 'select from', 'X++ query for', 'requête X++', 'écrire une select'. Generate both X++ select statements and equivalent T-SQL queries for D365 F&O tables. Uses real field names, relations, and indexes from the knowledge base to produce correct joins. Supports: field selection, multi-table joins (auto-detects relations), WHERE filters, ORDER BY, TOP/firstonly, cross-company. Also accepts natural language descriptions like 'find all open sales orders for customer 1001 with CustTable join'. [!] For multi-table joins, call find_related_objects (or get_relation_graph if the relation index is loaded) FIRST to get the correct FK relations -- this tool will then produce accurate join conditions. [!] The generated X++ is a template -- adapt it to your custom code context before using in production. Returns side-by-side X++ and SQL with explanations.
    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
  • WHEN: a user encounters an error message, infolog error, or runtime exception in D365. Also handles business-language error explanation when audienceType='business'. Triggers (developer): 'fix this error', 'what causes', 'exception thrown', 'infolog error', 'update conflict', 'outside tts', 'number sequence'. Triggers (business): 'what does this error mean', 'explain this error to me', 'user gets error X', 'que signifie cette erreur', 'message d\'erreur', 'what should the user do when they see this error'. Find known D365 F&O error patterns matching an error message or symptoms description. Matches against a built-in database of common errors (transaction conflicts, security issues, number sequences, posting errors, batch problems, etc.), resolves D365 label IDs from error text (e.g. user sees 'Number sequence not set up' -> finds @SYS70535 -> finds the throwing code), and searches the indexed codebase. Returns root causes, step-by-step resolution, label matches, and source code locations. [~] When the error text contains a D365 label ID (e.g. '@SYS12345'), call `search_labels` first to resolve the label text, then call this tool with the resolved text. [~] Also explains a Microsoft best-practice moniker: pass 'BPErrorFieldCurrencyDateTableEmpty' (or a symptom like 'strong name') to get the rule text from Microsoft's own catalogue, read out of the indexed D365 build. That is the rule TEXT -- `run_best_practices_check_scoped` is what decides whether an object breaks it. Set audienceType='business' for a plain-language explanation targeted at end users instead of developers.
    ConnectorNo auth