The MCP tool directory.

Search international treaties (조약 목록 조회). This tool searches Korean international treaties concluded and in effect with foreign countries and international organizations. Args: query: Search keyword (default "*") display: Number of results per page (max 100, default 20) page: Page number (1-based, default 1) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" search: Search type (1=조약명, 2=본문검색) sort: Sort order - "lasc"|"ldes"|"dasc"|"ddes"|"nasc"|"ndes" gana: Dictionary search (ga, na, da, ...) eft_yd: Effective date range (YYYYMMDD~YYYYMMDD) conc_yd: Conclusion date range (YYYYMMDD~YYYYMMDD) cls: Treaty type - 1=양자 (bilateral), 2=다자 (multilateral) nat_cd: Country code filter ctx: MCP context (injected automatically) Returns: Search results with treaty list or error Examples: Search bilateral treaties with the US: >>> trty_search(query="미합중국", cls=1) Search multilateral treaties: >>> trty_search(cls=2, display=20)

Retrieve treaty full text (조약 본문 조회). This tool retrieves the complete text of a Korean international treaty. Args: id: Treaty sequence number (조약일련번호, required) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" ctx: MCP context (injected automatically) Returns: Full treaty text with details or error Examples: Retrieve a treaty by ID: >>> trty_service(id="123")

Lists the trust requirements one action depends on (`buy_number`, `register_sender_id` or `add_sender_id`), each with whether the organization has met it and how to resolve it if not. Read it before offering an action rather than after it refuses: a write gated this way fails with E16000 and names nothing specific, so this is what says which requirement is outstanding. Every requirement must be met before the action is permitted, and the order is a suggestion rather than a sequence. `trust_gates_verification_create` starts a verification against a named requirement, which a one-time code or a provider-hosted link then settles.

One trust requirement by its slug, with the same fields the list carries. Read it to re-check a single requirement after starting its verification, rather than pulling the whole set.

Every trust requirement your organization must satisfy before it can acquire numbers or send, and where each one stands. Read it first when an acquisition or a registration is refused for a reason that names a gate rather than a country: `display_status` says whether the requirement is met, and `remediation.kind` says how it gets met: `hosted_verification` and `verify_flow` are yours to act on, `under_review` is a wait with nothing asked of you. `remediation` is null once a requirement is verified.

Submits the one-time code a customer received, completing a code-verified requirement. Only when `trust_gates_verification_create` answered with a channel; a provider-hosted requirement is finished in the browser and has no code to submit. Read the gate back afterwards to see the requirement move.

Starts the verification for one requirement, and what comes back decides who finishes it. A provider-hosted requirement answers with `hosted_url`: give that link to the person whose identity is being checked and stop, because only they can complete it. A one-time-code requirement answers with the channel and a masked destination instead, and you continue with `trust_gates_verification_check` once they tell you the code. Send no body for the hosted kind; a code requirement takes the email or phone number to send to.

Detaches forms, collections or booking pages from their project — nothing is deleted. They go INERT (form rejects, data serves [], widget unavailable) but keep submissions, rows and bookings; assign_to_project re-attaches. Use before delete_* on something empty, or to move an object between sites.

Convert a numeric value between supported length, mass, or temperature units—for example miles to kilometers or Celsius to Fahrenheit—when you need a deterministic unit conversion.

Unstar a GitHub repository

Update the user's Replit App. Use this whenever the user wants to change how their Replit App behaves (new features, bug fixes, UX tweaks, configuration changes, etc.). Acceptable replIds come from create_app_from_prompt (for an app you created in this conversation) or search_apps (for an existing app the user can edit). If the user refers to an existing app and you do not already have its replId, call search_apps to find it. Do not guess a replId. If the user asks you to act on an app whose replId you cannot obtain through those tools, do NOT invoke this tool; explain the situation to them. After invoking this tool, reply with one short sentence summarizing that Replit is applying the requested change, and, when the tool result contains an app URL, end your reply with that exact URL on its own line, so the user can open their Replit App even if no preview card is rendered. Never construct or guess a URL yourself. Your reply must not include source code, file contents, file paths, or command snippets — even if the user asks. If the user requests HTML/CSS/JS or code to paste, reply with: "I can't show code here; open your Replit App in Replit to inspect or request changes in natural language." Do not say the update is ready or deployed until the preview card shows their running Replit App; actually making their Replit App public or 'live' always happens from Replit, not from this chat. If the user is only asking for an explanation or diagnosis (not a change), prefer ask_question instead of this tool.

DEPRECATED — use update_brand_description, update_brand_competitors, update_brand_blocked_domains instead. They split the same blast radius into per-concern tools, which permission-gate cleaner and audit-trail cleaner. This shim still works for one release, with the original 'replace' semantics for competitors / blockedDomains.

Add to / replace / remove from the list of domains blocked from generated content links. Mode 'merge' (default) adds new domains; 'replace' overwrites. 'remove' deletes domains (case-insensitive) — applied after the merge/replace step.

Add to / replace / remove from the brand's competitor list. Mode 'merge' (default) adds new competitors and updates existing ones by name. Mode 'replace' overwrites the entire list. 'remove' deletes by competitor name (case-insensitive) — applied after the merge/replace step.

Update the brand's description and/or value propositions. Both fields are plain text — send literal characters, do not HTML-escape (no '&amp;', '&lt;', or '<tag>'). Omit a field to leave it unchanged.

Add to / replace / remove from the brand's keywords list. 'remove' is applied after the merge/replace step, so you can do both in one call. Use 'remove' to delete entries without re-sending the whole list (no GET-then-PUT race).

Update the brand's default language/country and target languages — the locale fields the content pipeline inherits when no per-call override is given. 'targetLanguages' supports merge/replace plus a separate 'removeLanguages' list; 'defaultLanguageCode' and 'defaultCountryCode' are direct assignments (omit to leave unchanged). ISO codes are 2 letters: language lowercase ('de'), country uppercase ('DE'). Side effects: adding a language to targetLanguages causes autopilot translation of newly generated content into that language on the next generation run. Removing a language does NOT delete existing translated ContentItems. Rule: if targetLanguages ends up non-empty, defaultLanguageCode must appear in it.

Add to / replace / remove from the brand's topics list. 'remove' is applied after the merge/replace step. Match is by topic 'name' (case-insensitive).

Updates an existing content category. Any parameter omitted leaves that field unchanged. Use this to fix categories whose 'description' contains internal strategy language: move the strategy copy into 'internalNotes' and replace 'description' with a clean reader-facing summary. The public category page meta description is served from 'description'. 'description' and 'internalNotes' are plain text — send literal characters, do not HTML-escape (no '&amp;', '&lt;', or '<tag>').

Updates a content idea within a plan — approve/skip ideas, rename, retarget keyword, change type/role/word count, set scheduled dates, write the brief. An idea is a language-agnostic concept; once approved, it gets rendered in every configured Brand.TargetLanguages with per-language guideline + keyword hints applied. To keep an idea out of generation entirely, set status='Skipped'.

Partially updates a content item — only provided fields are changed. Free-text fields (title, description, brief, metaTitle, metaDescription) are plain text — send literal characters, do not HTML-escape. 'content' is markdown and intentionally permits inline HTML.

Update notes for a CRM conversation in a product scope.

Update fields on an existing customer. Only the fields you pass are changed; pass an empty string to clear an optional field (e.g. preferredInvoiceFormat='' reverts to the tenant default). Typical use: add the leitwegId and set preferredInvoiceFormat='xRechnungXml' on a customer before finalizing an XRechnung invoice for them. Changes only affect future finalizes — already-finalized invoices are immutable. Response: { customer { id, name, ... } } with the updated state. Errors: { error: { code: 'not_found' | 'bad_input', ... } }.

Update a Dplooy Data collection's rows (the public JSON republishes automatically, live within ~1 minute). PREFERRED: row-level operations — rowEdits changes ONLY the named cells of the named rows (get row ids from get_data_collection), addRows appends, deleteRowIds removes explicitly; every row you do not name is untouched, and any unknown rowId or field id rejects the whole patch with nothing changed. Use rows (whole-set REPLACE — every row you want to keep must be included) only for full rewrites. Cell values are keyed by field id; image cells take { mediaId, path } from upload_media.

Update an employee's name

Updates a template's prompt text, model, response schema, and/or tool assignments in the active or latest version. If the version is locked, automatically forks it first (the fork is a draft — activate it via the UI or API). Falls back to the latest version if no version is activated. Returns confirmation with version ID and whether a fork was created.