MCP tools reference

Get the current user's information (email, name, etc.)

Get Ramp Categories Get all available Ramp transaction categories.

Get an answer to a question about the expense policy or funds (amount, restrictions, etc). Use this tool when the user asks about expense policy rules, spending limits, fund restrictions, or whether certain purchases are allowed under company policy.

Enroll the current business in agent cards for agentic commerce.

Estimate the reimbursement amount for a given mileage distance based on the user's company rates.

Estimate the per diem reimbursement amount for a trip given start/end dates and optional meal deductions.

Run read-only SQL against the resolved Core analyst artifact. Use this for aggregate spend and business analysis questions: totals, trends, group-bys, vendor/payee/merchant/category/user/department/card analysis, travel/trip/itinerary analysis, procurement/PO/spend request analysis, AP/bill analysis, accounting/tracking category/currency analysis, and approval/workflow analysis where represented in curated `analyst.*` tables. For analyst questions, inspect artifact status and catalog before querying. Use metric metadata for supported metric-style questions. Before writing SQL against an analyst table not already inspected in this conversation, call the analyst table domain docs tool and use its grain, column, join, filter, freshness, and caveat guidance. Treat Core analyst catalog, domain docs, and metric metadata as the semantic source of truth; do not rely on DuckDB metadata introspection or artifact column comments for schema semantics. Queries are validated and executed by the Core analyst query helper, which restricts access to approved artifact schemas and mounts the resolved Modal volume for the requested artifact instance. Use transaction tools instead for individual transaction lookup, approvals, missing receipt/item workflow, or other transaction action status. SQL style requirements: use only column names listed in the analyst catalog/domain docs for each table; always qualify every column reference with its table name or alias (for example `spend_facts.amount`, not `amount`), especially in queries with joins or subqueries; include every non-aggregated SELECT column in the GROUP BY clause; when filtering or joining by UUID string literals, use the `*_uuid` columns (for example `spend_facts.spend_event_uuid`) — never compare integer `*_id` columns to UUID strings; and use typed date literals like `DATE 'YYYY-MM-DD'` instead of bare strings when comparing date or timestamp columns.

Get daily balance history for a specific Ramp Checking Account. Use when the user asks about balance history for a specific account, savings account trend, checking account balance over time, or the balance trend for a specific Ramp Checking Account. This tool only supports Ramp Checking Accounts, not Investment Accounts or Managed Portfolios.

Get a one-time payment token for a fund. Handles card enrollment and purchase instructions automatically.

List funds that can be used for agent card payments. Returns eligible funds with available balance.

List Users List and search users across the entire business. Returns all users in the organization matching the given filters. Supports searching by name (partial match, case-insensitive), filtering by department or location, and pagination. Results include active and inactive users — check the is_inactive field to distinguish. Use department_ids or location_ids (lists of UUIDs from the departments or locations tools) to narrow results.

Return Core-owned status metadata for the current analyst DuckDB artifact. Use this before querying analyst data to disclose whether the current artifact is fresh, stale, missing, failed, or otherwise unavailable.

Return Core-owned catalog metadata for analyst artifact tables. Use this to discover which `analyst.*` tables are present in the resolved artifact, whether they are queryable, and starter guidance for supported tables. This is part of the preferred path for aggregate spend and business analysis; use transaction tools only for individual transaction lookup or workflow status.

Return metric definitions for the Core analyst artifact. Use this to pick supported spend, PO coverage, procurement request, and approval backlog metrics and starter SQL before querying. This is the preferred path for aggregate metric questions such as totals, trends, and group-bys.

Return Core-owned semantic docs for `analyst.spend_facts`. Use this before writing spend analysis SQL when the answer depends on table grain, money fields, date fields, identity caveats, dimensions, freshness, or boundaries between spend facts and dedicated procurement facts. This is for aggregate spend analysis, not individual transaction workflow lookup.

Return Core-owned semantic docs for a supported analyst table. Use this before writing analysis SQL when the answer depends on table grain, curated filters, money fields, lifecycle fields, identity caveats, dimensions, freshness, or known unsupported semantics. Treat these docs as the source of truth for table semantics instead of DuckDB metadata introspection or artifact column comments. Use analyst table docs for aggregate business analysis; use transaction tools for individual transaction workflow lookup.

Return the authenticated user's homepage attention feed. Use this tool to see what needs the user's attention right now: pending approvals, missing receipts, overdue reviews, signatures, and similar action items that appear on the Ramp homepage. By default, the tool returns the default homepage sections with compact LIST-hydrated task rows. To fetch more from a section, pass that section's section_type and next_cursor back in sections.

Returns aggregate dollar amounts for bills matching given filters, e.g. total unpaid amount, total pending amount. Use when users ask things like "How much do we owe in bills?" or "What's our total outstanding bill amount?".

Retrieve comments from a bill's comment thread.

Get comprehensive details about a specific bill including payment status, approval status, and all metadata. This tool retrieves submitted bills only. For draft (provisional) bills that have not yet been submitted, use GetDraftBillDetails instead.

Retrieve the full modification and approval history of a bill, including status changes, approval actions, and creation details.

Retrieve invoice file attachments for a bill.

Returns the count of bills matching specified filters. Use this to answer questions like "How many bills are pending approval?" or "How many overdue bills do we have?".

Get the current payment and approval status of a specific bill, including any required next actions.

Get bills that are pending approval from the current user. Use this tool when the user wants to see bills they need to approve or asks about pending approvals. This returns only bills where the user is the next approver in the approval chain.

Retrieves flight, hotel, and car rental bookings for the user. Use this tool when users ask about their: - Hotel bookings or reservations - Flight bookings - Car rental bookings - Travel bookings in general - Status of a recent booking request - The booking UUID to cancel or change an existing flight, hotel, or car rental By default this returns the acting user's own bookings. To look up ANOTHER user's bookings (e.g. an admin, travel manager, or a delegate asking about the person they assist), first resolve that person to a user UUID with GetAllReducedUsers (an org-wide search; do NOT use LookupUser, which is team-scoped and fails for delegates/regular employees) and pass it as `traveler_user_id`. Results are permission-scoped: you only receive bookings the acting user is authorized to see. An empty result can mean either that the person has no bookings or that you are not authorized to see them — say you couldn't find any bookings you can access for that person; do NOT assert a hard permission denial, and do NOT fall back to searching for new hotels or flights. By default this returns only CURRENT and UPCOMING bookings — flights that have not yet landed, hotel stays that have not yet ended, and car rentals not yet returned. Past/completed bookings are excluded so that cancellation and modification requests never act on a finished booking. When past bookings are hidden, the past_*_excluded counts are non-zero; mention to the user that they also have past bookings available if they want to see them (e.g. "you also have past flights I can show you") and only call this tool again with include_past=True if they explicitly ask. Pending and failed booking requests are always returned regardless of include_past. Returns both confirmed bookings and pending/failed booking requests in unified lists. Check the status field: PENDING_APPROVAL, PROCESSING, or FAILED indicate unconfirmed requests. If status is FAILED, the error_message field explains why. IMPORTANT: Cancelled and failed bookings do NOT block new bookings. If a user has a prior booking with status CANCELLED or a failed request with status FAILED, they can still make a new booking for the same route, hotel, or trip. Always allow the user to proceed with a new search and booking when they ask to rebook after a cancellation or failure. IMPORTANT: When presenting results, use Rich Object References (ROR) format: - For hotels: [Hotel Name](hotel-uuid) e.g., [Marriott Downtown](abc123-def456) - For flights: [Flight Info](flight-uuid) e.g., [UA 100 SFO → JFK](abc123-def456) The 'id' field in each booking is the UUID to use in the reference.

Fetch trips that could be relevant to the current transaction. Returns ongoing, upcoming, and recently completed trips for the acting user.

Get a detailed explanation of why a transaction was declined. IMPORTANT: Only call this tool on transactions that are already known to be declined. If you need to find declined transactions first, use GetUserTransactions with state='declined'. Do NOT call this on approved or pending transactions — it will return a not_declined error. This tool provides: - Human-readable explanation of the decline reason - Structured remediation actions the user or admin can take - The SMS/push notification message sent to the user - Transaction details (amount, merchant, card, timestamp) Use this when a user asks why their transaction was declined or what they can do about it.

Get rich details for a draft (provisional) bill. Returns compact draft-bill metadata by default. When requested, it also returns the canonical provisional-bill update payload inline.

Resolves locations (airports/cities) available for booking a flight from user intent. Returns locations where flights can be booked from or to, which may include: - Individual airports (e.g., JFK, SFO, LAX) - City groups with multiple airports (e.g., NYC includes JFK, LGA, EWR) - Major travel destinations with flight availability Pass a result's ``search_code`` straight into SearchFlights departure/arrival. Cities search every airport in the metro area; airports search just that airport.

View all details, memos, funds, and receipts for a specific transaction.

Get the balance of investment accounts for the business. Use this when the user asks about investment account balances, brokerage cash, or the current balance of Ramp investment accounts. Returns all investment accounts the business has, along with balances, status, yield, and earnings.

Get the balance of managed portfolio accounts for the business. Use this when the user asks about managed portfolio balances, managed portfolio cash, or the current balance of Ramp managed portfolio accounts. Returns all managed portfolio accounts the business has, along with balances, market value, status, yield, and earnings.

Get org chart for a user, including reporting chain and direct reports. This tool provides comprehensive org chart visibility including: - The user's position in the organization - Their direct reports (team members) - Their reporting chain (managers up the hierarchy) Use this tool whenever the user asks anything about their manager, team, or direct reports.

Get approved and failed reimbursements that would be affected by a bank account currency change.

Get comprehensive details about a specific purchase order. Use this after SearchPurchaseOrders or when the user is already looking at a purchase order and wants more detail, such as status, amount, vendor, or the associated unified request ID.

Get Ramp Business Account Balance Get the balance of Ramp Checking Accounts for the business. Returns the available balance, statement balance, and other details for all Ramp Checking Accounts associated with the user's business. This includes yield/earnings information and account status. This tool is intentionally limited to the stable user-facing fields for Ramp Checking Accounts. Do not infer deprecated pending balances or current month accrued yield values from other treasury payloads when responding to the user.

Retrieve details of a recurring bill template including vendor, amount, recurrence schedule, and next payment date.

Retrieve receipts attached to a reimbursement.

Search and retrieve reimbursements with filters for users, text search, amount ranges, tags, date ranges, approval status, and policy assessments.

Get reimbursements that require approval from the current user. Returns employee reimbursements pending approval. Use specifically when users ask about reimbursements, out-of-pocket expenses, or reimbursement approvals. Do NOT use for card transactions or purchase requests. Only shows reimbursements where the current user has approval authority. Includes policy assessment data and recommended actions to help with approval decisions.

Get requests that require the current user's review and approval. This is the approval-queue wrapper over SearchUnifiedRequests. Use it when the user is specifically asking what they need to review or approve right now. For broader lookup by vendor, owner, status, or request name, prefer SearchUnifiedRequests instead. Only handles lookups, does not take any action.

Get the current user's details. Returns multiple results for users that are part of multiple businesses. When authenticated via an agent key, also returns the active agent key identity.

Retrieve all active tracking categories for the current business. Tracking categories are used to organize and categorize transactions in the accounting system. Common examples include: - Departments (e.g., Engineering, Sales, Marketing) - Classes or Business Units - Locations (e.g., US East, US West) - Projects - Customers - Cost Centers This tool returns only the tracking category metadata, not the available options. To get the options for a specific tracking category, use GetTrackingCategoryOptions. This tool should mainly be used as a helper tool to identify tracking categories when users want to set accounting categories on transactions. If passing transaction_uuid, use an actual TransactionCanonical UUID from the current transaction context or a prior transaction lookup tool result. Do not pass placeholders like "target" or natural-language references; omit transaction_uuid when no transaction UUID is available.

List specific departments, projects, or other options for a tracking category. Pass `query_string` to narrow by name. If you're coding a specific transaction or reimbursement, pass its UUID so results respect conditional filtering (subsidiary, department, location, etc.); skip it for generic lookups, including bill/invoice contexts. Categories can have millions of options — paginate via `next_page_cursor` when needed.

Check what receipts, memos, or accounting items are missing from a specific transaction.

Get AI-suggested memo/note options for a specific transaction.

Retrieve the user's traveler profile information including name, email, phone, date of birth, gender, known traveler number (KTN/TSA), redress number, and loyalty programs.

Get daily balance history across all Treasury accounts for a date range.

Get detailed information about a specific unified request the acting user can view. Use this when the user asks for more detail about a specific spend request, purchase order, fund request, or other unified request - for example its current status, approval chain, comments, or agent-generated reports. This works both after SearchUnifiedRequests or GetRequestsToReview and for any other unified request the user can already access via page context, tagged objects, or a known request UUID.

Get Funds Retrieve funds (also known as cards or budgets) that belong to the current user or other users. Use this tool when users ask about: - Their funds, cards, or budgets (e.g., "show me my funds", "what cards do I have?") - What they can buy from a specific fund - Why their card is locked or not working (e.g., "why is my card locked?", "why can't I use my card?") - Fund balances, restrictions, or lock status When querying for a specific person's funds, first call GetOrgChart to get their UUID, then use the user_uuids parameter. For queries about "my funds", use funds_to_retrieve=MY_FUNDS. To search by fund name, use search_by_fund_display_name. To look up a specific fund by its UUID, use fund_uuid. For card lock questions, set include_lock_info=True to get lock details.

Get reimbursement history for the current user. `limit` takes precedence over `up_to_days` so if you want to get all reimbursements in a given time frame, do not specify `limit`. `include_rejected` controls whether to include rejected reimbursements in the results. By default, rejected reimbursements are excluded. `use_submitted_date_ordering` controls the ordering of results. By default (False), results are ordered by transaction_date. Set to True to order by submitted_date instead. If the user did not ask for a specific number of reimbursements or a time frame, assume they want to see the latest 10 reimbursements.

Get Transactions Search and retrieve individual card transactions and workflow details for the user's business. Use analyst tools instead for aggregate spend analysis, totals, trends, or group-bys when analyst tools are available. Declined transactions are excluded by default; pass state='declined' to include them.

Fetch trips for the acting user with optional filters.

Retrieve details for a specific vendor agreement/contract by UUID. Returns contract metadata, terms, line items, contract owners, documents, linked spend requests, and renewal history.

Get bulk vendor document upload progress and current document review state. Use this after `BulkUploadVendorDocuments` to inspect the batch job status, understand whether any documents still need manual review, and inspect the current document/vendor matching and extracted tax details.

List and filter bills with optional search, pagination, and status filters. Returns bills for the current user's business. When called with no parameters, returns the most recent bills. Supports optional text search across vendor name, invoice number, and payment ID.

List all Ramp Checking Accounts (wallet accounts) for the user's business. Returns account details including balances, currency, yield rate, and status. Use this tool when the user asks about their checking accounts, wallet accounts, or wants to see an overview of their Ramp Checking Accounts.

List non-terminated cards for the current user or a visible target cardholder, including activation status, lock state, and shipping metadata. IMPORTANT: When a user asks to unlock their card, call this tool FIRST to check which cards are locked (is_locked=true). Then use LockOrUnlockCard to unlock. Do NOT use GetUserFunds for card unlock requests — funds and cards are different.

List all Treasury accounts (Ramp Checking Accounts, Investment Accounts, Managed Portfolios).

List and filter vendor agreements/contracts across the business. Returns agreement details including dates, values, renewal status, line items, and days remaining. All filters are optional — omit all to list all agreements, or combine filters to narrow results.

List wallet transfers for the user's business Ramp Checking Accounts. Returns a list of transfers including deposits, withdrawals, and other transactions with details like amount, status, and dates.

Search User Match a user name to a Ramp user in the context of a transaction, for adding as an attendee. Returns users from the business ranked by relevance to the given transaction (recent attendees and teammates appear first). If no transaction ID is provided, the user's most recent transaction is used as context. The search is case-insensitive and matches partial names.

Search for bills using natural language queries like vendor names, amounts, or invoice numbers. Submitted and active draft bills may both be returned unless include_drafts=False. To look up only a draft bill, use GetDraftBillDetails instead.

Search for flights and return policy-tagged offers ready to quote. Server runs the search to completion (waiting on the search workflow rather than client-side polling), tags results with in/out-of-policy (per fare when fare_options is present, else per offer), and includes a top-level policy banner. Dense routes can exceed the server-side wait; the response then has ``search_complete=false`` with the best offers so far — re-call with ``resume_job_id`` to get the final set. Returns up to ``limit`` offers. Output is additionally token-capped, so a large ``limit`` may return fewer offers; paginate with ``next_cursor`` to fetch the rest. Pass ``return_date`` for round-trip: the response returns OUTBOUND offers with ``is_round_trip=true``. Then call again with ``outbound_offer_id`` set to the chosen outbound's id to get its matching RETURN offers; book by passing the chosen return offer's id. Pass ``sort_key`` to order results (same keys as the flight search UI/REST API). The sort is fixed for a job's lifetime, so re-sort by starting a new search rather than resuming. Each offer's ``price`` is the cheapest fare. Set ``include_fare_options`` when the user asks about upgrades or comparing cabins to also get each offer's ``fare_options`` (Economy Plus, Business, etc.); book a specific fare by passing that fare option's ``id``, not the offer's top-level ``id``. Pass ``include_fare_options`` again on resume calls to keep it on across pages. Policy is evaluated per fare. When ``fare_options`` is present, read each fare's ``in_policy`` for the booking decision; the offer's top-level ``in_policy`` is null because different fares on the same flight can have different verdicts. The offer-level ``in_policy`` is only set when ``fare_options`` is absent (the offer is a single bookable fare). Paginate by passing the previous response's ``job_id`` as ``resume_job_id`` and ``next_cursor`` as ``cursor``. Resume calls read from Redis (no provider re-fetch). A resume can also re-filter the same itinerary by passing a new ``cabin_class``, ``airlines``, or ``max_stops`` (re-applied to the cached results, no provider re-fetch). To page a re-filtered view, re-send the same filters with the returned ``next_cursor``. Changing airports, dates, or passengers still requires a new search. Do NOT use this tool to change, modify, cancel, or rebook an existing booking.

Tool for searching Ramp's help center documentation using RAG (Retrieval Augmented Generation). This tool performs semantic search across help center articles using embeddings, returning only the most relevant snippets rather than full articles. This is more efficient and provides focused information. The tool: 1. Fetches relevant articles from the help center 2. Chunks articles into smaller semantic units 3. Uses embedding similarity to find the most relevant snippets 4. Returns top K snippets with their source articles IMPORTANT: If you have other tools that can actually perform the action a user is asking about, you should use those tools instead of or in addition to providing help center information. For example, if a user says "how can I upload a receipt", you should tell them they can upload a receipt in the chat directly, even if you also find a help center article that explains how to upload receipts in the web app. Use this tool when you need to: - Find specific information within help articles - Get concise, focused answers from documentation - Minimize token usage while maintaining relevance - Answer questions about Ramp products and features

Search for purchase orders using structured purchase order filters.

Search reimbursements across a business, optionally filtering to a specific user's reimbursements.

Search for unified requests using free-text and structured request filters. Use this to find existing purchase orders, fund requests, procurement requests, or approval-only requests by vendor, request name, owner, requester, status, type, or whether they require action. Use GetRequestsToReview when the user is specifically asking what they need to approve right now. Use GetUnifiedRequestDetails once one request has been identified.

Search reimbursements with text-based filters and structured filters. Supports filtering by: - User name (e.g., 'John Smith') — resolved automatically, defaults to current user if not specified - Accounting coding selections (tracking categories) like Department, Cost Center, Class, GL Account - Merchant name, spend allocation name (resolved from text automatically) - Reimbursement status (DRAFT, PENDING, APPROVED, etc.) - Date range and text search The tool resolves text queries to internal IDs automatically via the search tag service. Results are scoped to the current user's business.

Search for vendors (payees) within the business by name. This tool searches for vendor records using both fuzzy SQL matching (trigram similarity + substring) and semantic (vector) search. Use this to find vendor IDs when you need to: - Look up a vendor by partial name - Find the correct vendor UUID for further analysis - Discover vendors similar to a given name The search is scoped to the current business context.

Book a selected flight offer. Two-step flow: call without ``confirm`` for a summary (itinerary, price, in-policy status, required approvals) without booking, then call with ``confirm=true`` and the previewed ``expected_total_amount`` to book once the traveler approves that summary. ``flight_offer_uuid`` is the literal ``id`` from search: the outbound flight for one-way, the return flight for round trips (it carries both legs), or a fare option's id to book that fare. For a delegated booking, pass the ``traveler_user_id`` from search. For changes or cancellations, use the web app. If the chosen flight is out of policy, you MUST collect an ``oop_reason`` from the traveler and pass it here.

Submit feedback to Ramp about the MCP server interface or problems you run into. Must be at least 10 characters long and less than 1500 characters.