الأوامر الرئيسية المتقدمة لبروتوكول MCP ‏(MCP Master Prompts)

Using the RemotePass MCP, call list_companies first — if the account has access to more than one entity, ask which entity to report on (or use switch_entity) before continuing; if there's only one, proceed with it. Call list_contracts with the status filter set to active. This is a headcount number people will quote, so make it exact: if the response indicates more rows exist beyond this page, keep calling again for the next page (using whatever pagination mechanism the tool's response describes) and merge every page's rows into one running set, continuing until the tool reports no further pages. There's no small cutoff here — a large workforce just takes more calls. Only pause if you pass roughly 40 calls without exhausting the pages — report the total counted so far and ask whether to keep going or narrow the filter. From the complete set of active contracts, compute: total headcount, a breakdown by contract type, and a breakdown by country (use list_countries to turn any ISO country codes into readable names). Build a single self-contained HTML artifact: a header stat for total active headcount, a bar or donut chart of contract type mix, and a ranked bar chart of headcount by country (top 10 + "Other", with a "Show all" toggle). Leadership-briefing tone, one page, no scrolling.

Using the RemotePass MCP, call list_companies first and confirm (or select) the entity to scope this to. Call list_contracts with the status filter set to active, and paginate through every page the same way — merge into one complete set until the tool reports no further pages, since a partial list here means a missed renewal, not just an imprecise one. From each contract's returned end date, bucket the complete set into three groups: expiring within 30 days, within 60 days, and within 90 days (each bucket also contains the ones before it). Use today's date as the reference point. Build a single self-contained HTML artifact with three toggle buttons — "30 days," "60 days," "90 days" — each showing a table of the contracts in that bucket (contract reference, name, country, type, end date), sorted soonest-first, plus a headline count per bucket. HR/ops tone, scannable. If I've also pasted or attached a budget or headcount plan in this conversation, cross-reference the expiring contracts against it and add a short "renewal cost impact" section — this is the kind of analysis RemotePass data .alone, or the budget alone, can't produce

Using the RemotePass MCP, call list_companies first and confirm (or select) the entity to scope this to. Call list_payments to get upcoming and unpaid payments across all contracts. This feeds a cash-out forecast, so make the total exact: paginate through every page and merge into one complete set until the tool reports no further pages. From the complete set, compute: total value pending (grouped by currency, since payments span multiple currencies — do not sum across currencies without converting or labeling them separately), a count of payments, and the payments ranked by amount, highest first. Build a single self-contained HTML artifact: a header strip with total pending value per currency and payment count, a ranked table of the top 15 payments (contract, amount, currency, due/status) with a "Show all" toggle, and a short callout for anything that looks overdue rather than merely upcoming. Finance-briefing tone.

Using the RemotePass MCP, call list_companies first and confirm (or select) the entity to scope this to. Call list_review_items to get every pending item requiring review — time-off requests, expense claims, invoices, bills, works, and documents. Paginate through every page and merge into one complete set until the tool reports no further pages, so nothing waiting for approval is left off the list. Group the complete set by item type, and within each type sort oldest-submitted first. Build a single self-contained HTML artifact: a header stat for total items pending, a bar chart of items by type, and a table per type (submitter, date submitted, brief description/amount where relevant) with the oldest 10 shown by default and a "Show all" toggle. Manager-facing, action-oriented tone — this should read like a to-do list, not a report.

Using the RemotePass MCP, call list_companies first and confirm (or select) the entity to scope this to. Call list_approval_flows to get every approval flow with its approver steps and settings. Then, for each flow, call list_approval_flow_contracts to get the contracts attached to it. Also call list_contracts (status: active, paginated to completion) to get the full set of active contracts. Cross-reference: any active contract that does not appear in any flow's attached-contracts list is flagged as having no approval coverage. Also flag any flow with only a single approver step, as a concentration-of-control note. Build a single self-contained HTML artifact: a table of approval flows (name, number of approver steps, number of contracts attached), a headline "# of active contracts with no approval flow attached," and a table listing those uncovered contracts. Security/governance-review tone.

Using the RemotePass MCP, call list_companies first and confirm (or select) the entity to scope this to. For each of the last 6 calendar months, call list_transactions filtered to that month and year, paginating each month's results to completion so the count and value per month are exact, not sampled. Build a single self-contained HTML artifact: a bar or line chart of transaction value per month, month-over-month % change labeled on each bar, and a headline calling out the current month's pace vs. the trailing 3-month average. The current (partial) month should be labeled as partial and excluded from the %-change math. FP&A tone.

Using the RemotePass MCP, call list_companies to get every entity the authenticated user has access to. If there's only one, say so plainly and skip the rest of this prompt — this view only adds value for multi-entity accounts. For each entity, use switch_entity to scope to it, then call list_contracts (status: active, paginated to completion) and list_company_users (paginated to completion) for that entity. Build a single self-contained HTML artifact with one row per entity: active headcount, total company users, and a breakdown of users by role. Include a combined total across all entities at the top. Admin/access-review tone.

Using the RemotePass MCP, call list_companies first and confirm (or select) the entity to scope this to. Call list_payments (paginated to completion, so the totals are exact) and list_currencies (for readable currency names and symbols). Group the complete set of pending payments by currency and compute total value per currency. Build a single self-contained HTML artifact: a ranked bar chart of pending payment value by currency (labeled with currency name and symbol, not just the code), and a headline noting how many distinct currencies are in play. Treasury/FX-review tone.

Using the RemotePass MCP, call list_contracts with the search filter set to "CONTRACT_REFERENCE" to find the matching contract (confirm the right one if more than one result comes back — show me the candidates rather than guessing). Call get_contract_details for the confirmed contract to get its full field-level details (type, rate, frequency, status, start/end dates, country). Call list_contract_payments for that same contract, paginated to completion, to get its complete payment history. Build a single self-contained HTML artifact: a summary card of the contract's key terms, a chronological table or chart of its payment history (date, amount, currency, status), and a short note flagging anything that looks inconsistent with the contract terms (a gap in the expected cadence, an amount that doesn't match the stated rate) — or an explicit all-clear if nothing looks off. Contract-review tone.