"How to add a note to an order or object" matching MCP tools:

• openstreetmap_reverse_geocode

  openstreetmap-mcp-server

  Convert latitude/longitude coordinates to the nearest address or place name via Nominatim/OpenStreetMap. Returns the closest matching OSM object at the given coordinates. Note: Nominatim finds the nearest indexed OSM object — in dense areas this may differ from the address at the exact coordinate. Use zoom=18 for building-level accuracy, lower zoom values for coarser resolution (e.g., zoom=10 for city-level). The match is made on proximity and layer, never on an OSM attribute tag: extratags decorates the matched object and cannot select one. To find the objects in an area that carry a given tag, use openstreetmap_query_nearby, openstreetmap_query_bbox, or openstreetmap_query_raw.

  Connector

• submit_feedback

  Kifly — Agentic Commerce & Payments

  Send structured feedback to the Kifly team. **Call after a confusing response, a dead-end, or a successful workaround you had to invent** — it's how we improve the agent surface. Fire-and-forget: returns 202 immediately, no blocking, safe to skip if it would add latency to a user-facing flow. `category` and `severity` are required enums (don't free-form them). Include `context` with what you were doing (tool called, query used, response shape, what you expected). Add `suggested_fix` only if you have a concrete idea. Rate-limited to 10/min per agent token; everything is reviewed before influencing anything.

  Connector

• validate_addresses_batch

  acuris-mcp

  Validate up to 50 addresses in one call (mixed countries allowed). `addresses` is a list where each entry is either a free-text string, or an object {"input": <string or fielded object>, "country": "iso3"}. Entries without their own country use the `country` parameter. UK (gbr) rows are routed individually to the Royal Mail PAF service; everything else goes through the batch endpoint. Results come back in the same order, each with the same shape as validate_address. Cost: 1 validation credit per successfully validated row; failed rows are refunded. For files bigger than 50 rows, call this tool repeatedly.

  Connector

• lunium_quote_crypto_sale

  lunium

  Requires an API key. Step 1 of 3 of selling crypto for reais. Prices a specific amount of a specific asset on a specific network against a specific PIX key, returning brl_amount (what the recipient receives), expires_at, an order id and a confirmation_token. No money moves and no deposit address is issued here — nothing is committed until lunium_confirm_crypto_sale. Always show the user brl_amount and the destination PIX key before confirming. This is the last step where a wrong destination is still free to fix. Rules that prevent expensive mistakes: send amount as a decimal STRING ("50", "12.5"), never a JSON number — floats lose precision in transit. pix_key_type is mandatory because a CPF and a phone number are both 11 digits and cannot be told apart without it. Always send your own external_id: it makes the call idempotent, so repeating it returns the same order instead of creating a second one, and it is how you recover after a timeout or a crash. Read expires_at from the response instead of assuming a window. Do not call it in a loop to "watch the price" — every call is an order. Do not quote an amount you are not ready to send. Do not quote an asset or network you have not confirmed with lunium_list_settlement_options. Errors: acao=corrigir with a limits object → the value is outside the per-operation range (R$ 5.00 to R$ 50,000.00) or above the daily ceiling, and limits.min_amount / limits.max_amount come back already converted into this asset at this order's rate — use one of those numbers, do not guess. A refusal on the network means it is not settling at this moment: offer another network instead of retrying. acao=esperar → quota. acao=repetir → retry with the SAME external_id. erro="external_id_divergente" (acao=corrigir) → this external_id already exists with different parameters; generate a new one, do not reuse.

  Connector

• route_order

  ensotrade

  Cheapest way to fill a crypto perp order across multiple venues, and what that saves versus using the single best venue. Merges every order-book level from Binance, Bybit, Bitget, Hyperliquid, OKX and Gate into one list ordered by FEE-ADJUSTED price and walks it until filled. Use for "how should I split this order", "what's the cheapest venue to buy $2M of SOL", "how much would routing save me". Returns the per-venue allocation, the blended price, the best single venue, and the saving in bp and USD. `coin` = ticker e.g. 'sol'. `notional_usd` = order size in USD. `side` = 'buy' or 'sell'. `venues` = optional comma-separated subset (e.g. "binance,bybit") for a desk that only has accounts on some — the saving is only real on venues you can actually trade. This is a MEASUREMENT of a live book, not a prediction: it is optimal for the static snapshot, prices move while an order works, and it assumes capital is already on each venue and ignores transfer costs. Requires an EnsoTrade Pro API key.

  Connector

• get_wedding_information

  The Hill Kinabalu

  Retrieve The Hill Kinabalu’s official public wedding venue and 2026/2027 package information, including capacity, event sizes, starting package prices, key inclusions, add-ons without prices, payment structures, and enquiry links. Use this when someone asks about weddings, wedding packages, the event venue, guest capacity, package pricing, or how to enquire. This tool does not check date availability or submit an enquiry.

  Connector

• add_pantry_item

  ForkMate

  Add a food to the user's pantry, or UPDATE it if it's already there (matched by name, any casing) — e.g. 'add rolled oats to my pantry'. Only `name` is required; include `macros` (for one serving), a `serving` label, a `source`, and a short `note` when you know them, so a later log can reuse them. Re-adding the same food REPLACES its details (an upsert — it never creates a duplicate). Only pass a `source` you actually got from search_foods/lookup_barcode; an unrecognized value is recorded as the user's own estimate ('client'). This does NOT log a meal — it only curates the user's staples.

  Connector

• apihub_call

  APIHub

  Sends payment. Calls a paid endpoint on an onboarded APIHub service. Debits the endpoint's price from your credit balance and forwards the request to the upstream provider. Returns an object with the upstream response body, HTTP status, and credits_charged_microdollars. Requires a valid API key and sufficient credit balance; if balance is insufficient the call returns a 402 with payment requirements (use apihub_topup to add credits, apihub_balance to check). Use this for services already onboarded to APIHub (find slugs via apihub_search or apihub_list_services); use apihub_call_external for arbitrary x402 URLs not onboarded here, or apihub_read_content for content gateways.

  Connector

• get_all_forex_quotes

  TipRanks

  Real-time forex quotes: the most-traded pairs, each with a display name. The feed carries 1,550 pairs in alphabetical order, which is far more than one response can hold — so this returns the most prominent `limit` of them (majors first, then by volume), and the response states how many were left out. Pass `symbols` for specific pairs, or call get_forex_quote for a single one. Read `note` before summarising: it says how many pairs the slice covers out of how many exist, so a "top pairs" answer is not mistaken for the whole market. `volume` on a forex row is a per-venue tick count, not market turnover — FX is over-the-counter and most pairs report 0. It does not rank the market. Args: symbols: Comma-separated pairs (optional; overrides the ranked slice) limit: How many ranked pairs to return (optional)

  Connector

• goal-add-evidence-text

  Planner — provable "done" for AI agents

  SUBORDINATE / supplementary path — does NOT close an acceptance criterion. Adds a text-only note (URL to a permanent external source like CI run / GitHub commit / issue, or a description of a manual scenario) as extra context alongside the real proof. The path that actually covers an AC and closes a Grove goal is goal-attach-evidence — use that one for every criterion. Plain evidence NEVER counts toward AC coverage no matter how many you add; it is only a complement to an attached file. NOT for bytes — screenshots, logs, API responses, exports all go through goal-attach-evidence. NOT for filesystem paths — those need goal-attach-evidence with the actual file.

  Connector

• firmaradar_get_regnskapsrapport

  Firmaradar

  Order a formatted, downloadable financial report (Excel or PDF) for a Norwegian company — the same multi-source-fused figures, layout and source note as the report a customer would download in the Firmaradar portal, ready to file or forward. Returns a short-lived download link + metadata (years covered, source, currency), NOT the file itself and NOT base64 data — fetch the download_url separately, no further auth required, within expires_in seconds. Use `get_company_financials` instead when you need the raw figures to reason about, not a document to hand off. Requires the Excel-export or PDF-export add-on (matching the requested format) on the caller's account. Charges 1 credit per financial year included in the report.

  Connector

• create_ticketcomments

  ProWoDo

  Add a comment to a ticket. DEFAULT is an INTERNAL note (is_internal=true): team-only, NOT shown to the customer. To reply visibly to the customer pass is_internal=false — the comment then appears on the customer's public ticket page. Draft internally first; make it public deliberately. Each comment carries app_url, an INTERNAL deep link to the ticket's task drawer — do not hand it to the customer; use the ticket's public_url (from retrieve_ticketsubmissions) for a customer-facing link.

  Connector

• sieve_dataroom_add

  Sieve

  Add a document to a deal's data room. Creates the deal if needed. This is the primary way to get documents into Sieve for screening. Upload a pitch deck, financials, or any document -- then call sieve_screen to analyze everything in the data room. Provide company_name to create a new deal (or find existing), or deal_id to add to an existing deal. Provide exactly one content source: file_path (local file), text (raw text/markdown), or url (fetch from URL). Args: title: Document title (e.g. "Pitch Deck Q1 2026"). company_name: Company name -- creates deal if new, finds existing if not. deal_id: Add to an existing deal (from sieve_deals or previous sieve_dataroom_add). website_url: Company website URL (used when creating a new deal). document_type: Type: 'pitch_deck', 'financials', 'legal', or 'other'. file_path: Path to a local file (PDF, DOCX, XLSX). The tool reads and uploads it. text: Raw text or markdown content (alternative to file). url: URL to fetch document from (alternative to file).

  Connector

• submit_feedback

  Kifly — Agentic Commerce & Payments

  Send structured feedback to the Kifly team. **Call after a confusing response, a dead-end, or a successful workaround you had to invent** — it's how we improve the agent surface. Fire-and-forget: returns 202 immediately, no blocking, safe to skip if it would add latency to a user-facing flow. `category` and `severity` are required enums (don't free-form them). Include `context` with what you were doing (tool called, query used, response shape, what you expected). Add `suggested_fix` only if you have a concrete idea. Rate-limited to 10/min per agent token; everything is reviewed before influencing anything.

  Connector

• integrate_overview

  mcp

  Orientation for wiring a redu.cloud capability (backups, DNS, extra storage, a managed DB, ...) INTO an app already deployed on redu, e.g. 'add a backup feature to the Supabase I deployed on redu'. Explains the pattern: mint a LEAST-PRIVILEGE scoped API key (with the user's approval via create_api_key), inject it into the app, and call the redu API from the app. Call this when a user asks to add/integrate a redu feature into a running deployment and you are unsure how.

  Connector

• watch_domains

  snooze

  Add one or more domains to your snooze watchlist. Each is monitored continuously and you get an email when its status changes or it nears a drop. Requires signing in to your snooze account. Up to 25 domains per call (100 total).

  Connector

• add_changelog_entry

  cortexpad

  Add a short, dated changelog entry to a note — structured evidence of a change (e.g. "Bumped reply target 3-5 → 8-10"), separate from and never touching the note body by default. Purely additive: does not overwrite or clobber content. Two ways to use it: (1) create a NEW numbered entry — if `anchor` is given (exact or substring text of an existing line), a small "((n))" marker pointing to the new entry is appended to that line, failing if `anchor` doesn't match any line (call get_note first if unsure of the exact text); without `anchor` the entry is note-wide with no inline marker. (2) append to an EXISTING entry via `appendTo: n` (e.g. 3 for an existing "((3))" marker) — adds another dated comment/update under that same marker without creating a new marker or number; fails if entry `n` doesn't exist yet. `appendTo` and `anchor` are mutually exclusive — `anchor` is ignored when `appendTo` is set. Use `section` (e.g. "update", "note") to label what kind of entry this is when a marker accumulates several over time — the UI groups/filters by section. Use this instead of update_note/append_to_note when recording a decision or change without altering the visible note text. Capped to the most recent 20 entries total across all markers.

  Connector

• get_statement_notes

  schedule-iii

  Read the line-by-line breakdown of a generated statement's notes — every line's current and prior-year amount, and the note total. Pass note_numbers (from get_statement_figures' note_index) to fetch specific notes, or omit for all. Use this to answer "what's in Other Expenses?" or "what makes up trade receivables?". Each line has a kind: 'component' (an additive line), 'subtotal' (a presentational group subtotal — do NOT add it into the total, or you double-count), or 'header'. Fixed-asset / intangible notes carry a `block` per class with gross_block, accumulated depreciation, and net (the additions/deletions movement schedule itself lives in the workbook). If the full set is too large it returns too_large:true with a note_index — fetch note_numbers in small batches. A single very large note (e.g. a PPE schedule or an ageing note) is returned in explicitly-flagged line pages: each page carries the authoritative note total, lines_page, lines_total, and has_more_lines — keep fetching lines_page until has_more_lines is false; never treat one page's lines as the whole note. Amounts are decimal strings in rupees. Figures are Datavrn's deterministic engine output; interpretation is your assistant's.

  Connector

• cancel_order

  massprint

  Cancel an order, stopping it before it is printed. With the order_token from create_order this works while the order is awaiting_payment. A platform that sends its own API key (Authorization: Bearer mp_live_...) can additionally cancel an order THAT KEY created while it is confirmed or printing — that is how you stop a press when your customer cancels on your side. shipped and delivered can never be canceled; that is a refund, contact support (see get_catalog). Canceling stops production but moves no money, and it releases the order's client_reference — replaying that reference afterwards creates a new order and prints it. If the order moved on before the cancel landed you get not_cancellable naming its new status, never a false "canceled".

  Connector

• add_note

  AIOProductOS MCP

  Add an INTERNAL note to a support conversation — visible only to your team, never sent to the end-user — and return the result. A write. Use it to record context or hand off; resolve conversation_id via list_conversations. conversation_id and body are required. For a public reply use reply_to_conversation instead.

  Connector