archal 0.9.8 → 0.9.9

package/twin-assets/ramp/tools.json

@@ -0,0 +1,2610 @@
+{
+  "twin": "ramp",
+  "tools": [
+    {
+      "name": "activate-card",
+      "description": "Activate a card by its last four digits",
+      "inputSchema": {
+        "type": "object",
+        "description": "Activate a card by its last four digits.\n\nActivates an unactivated card for the user. If the last four digits do not match\nany of the user's cards, returns available card last-four values so the correct\ndigits can be provided.",
+        "properties": {
+          "last_four": {
+            "title": "Last Four",
+            "type": "string"
+          }
+        },
+        "required": [
+          "last_four"
+        ],
+        "title": "ActivateCard"
+      },
+      "hidden": false
+    },
+    {
+      "name": "answer-policy-question",
+      "description": "Get an answer to a question about the expense policy or funds (amount, restrictions, etc)",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get an answer to a question about the expense policy or funds (amount, restrictions, etc).\n\nUse this tool when the user asks about expense policy rules, spending limits,\nfund restrictions, or whether certain purchases are allowed under company policy.",
+        "properties": {
+          "include_restrictions": {
+            "default": true,
+            "title": "Include Restrictions",
+            "type": "boolean"
+          },
+          "question": {
+            "title": "Question",
+            "type": "string"
+          }
+        },
+        "required": [
+          "question"
+        ],
+        "title": "AnswerPolicyQuestion"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "approve-or-reject-bill",
+      "description": "Approve or reject a bill that requires approval",
+      "inputSchema": {
+        "type": "object",
+        "description": "Approve or reject a bill that requires approval.\n\nUse this tool when the user wants to approve or reject a bill that is pending their approval.\nYou can find bills for approval by the current user by using the GetBillsForApproval tool.\nBefore using this tool, ask the user if they would like to include a reason or note\nfor their decision. Reason is optional, so you may call this tool with no reason\nif the user declines to provide one.",
+        "properties": {
+          "action_type": {
+            "enum": [
+              "APPROVE",
+              "REJECT"
+            ],
+            "title": "Action Type",
+            "type": "string"
+          },
+          "bill_id": {
+            "description": "The UUID of the bill to approve or reject.",
+            "title": "Bill Id",
+            "type": "string"
+          },
+          "reason": {
+            "default": null,
+            "nullable": true,
+            "title": "Reason",
+            "type": "string"
+          }
+        },
+        "required": [
+          "action_type",
+          "bill_id"
+        ],
+        "title": "ApproveOrRejectBill"
+      },
+      "hidden": false
+    },
+    {
+      "name": "approve-or-reject-reimbursement",
+      "description": "Approve or reject an employee reimbursement request for an out-of-pocket expense",
+      "inputSchema": {
+        "type": "object",
+        "description": "Approve or reject an employee reimbursement request for an out-of-pocket expense.\n\nUse this tool when the user wants to approve or reject a reimbursement.\nReimbursements are employee-submitted requests for reimbursement of out-of-pocket expenses.\nCommon usage patterns: \"approve this reimbursement\", \"reject the expense\", \"yes, reimburse them\", \"no, don't reimburse this\".\nThis tool is specifically for employee reimbursements and is NOT for approving/rejecting card transactions\nor unified requests (spend allocations, purchase orders).",
+        "properties": {
+          "action": {
+            "description": "The action to take on the reimbursement: approve or reject.",
+            "enum": [
+              "approve",
+              "reject"
+            ],
+            "title": "ReimbursementAction",
+            "type": "string"
+          },
+          "reimbursement_id": {
+            "description": "The ID of the reimbursement to approve or reject.",
+            "title": "Reimbursement Id",
+            "type": "string"
+          },
+          "thoughts": {
+            "default": null,
+            "description": "Your internal reasoning about why you chose to approve or reject this reimbursement. This helps explain your decision-making process and is used for audit purposes. Include relevant details like policy compliance, receipt quality, amount reasonableness, etc.",
+            "nullable": true,
+            "title": "Thoughts",
+            "type": "string"
+          },
+          "user_reason": {
+            "default": null,
+            "description": "Optional notes from the user explaining their approval or rejection decision. This will be recorded in the approval history and may be visible to other approvers and the reimbursement submitter. Use this when the user provides context like 'approve it because...' or 'reject because...'.",
+            "nullable": true,
+            "title": "User Reason",
+            "type": "string"
+          }
+        },
+        "required": [
+          "action",
+          "reimbursement_id"
+        ],
+        "title": "ApproveOrRejectReimbursement"
+      },
+      "hidden": false
+    },
+    {
+      "name": "approve-or-reject-request",
+      "description": "Approve or reject a pending unified request for spend allocation (fund), purchase order, or procurement approval",
+      "inputSchema": {
+        "type": "object",
+        "description": "Approve or reject a pending unified request for spend allocation (fund), purchase order, or procurement approval.\n\nUse this tool when a user wants to approve or reject a specific request they have identified or referenced.\nCommon usage patterns: \"approve this request\", \"reject this request\", \"accept the request\", \"deny this\",\n\"authorize this\", \"yes approve it\", \"decline this request\".\nThis tool is specifically for unified requests (spend allocations, purchase orders, procurement approvals)\nand is NOT for approving expenses like corporate card transactions or reimbursements.\nThe user must have proper approval authority for the request.",
+        "properties": {
+          "action": {
+            "enum": [
+              "APPROVE",
+              "REJECT"
+            ],
+            "title": "RequestAction",
+            "type": "string",
+            "description": "The action to perform: APPROVE or REJECT"
+          },
+          "request_uuid": {
+            "description": "The unified request to act upon",
+            "nullable": true,
+            "title": "Request Uuid",
+            "type": "string"
+          },
+          "thoughts": {
+            "description": "Your reasoning about whether to approve or reject this request. Consider: did the user clearly indicate whether they wanted to approve or reject?",
+            "title": "Thoughts",
+            "type": "string"
+          }
+        },
+        "required": [
+          "action",
+          "request_uuid",
+          "thoughts"
+        ],
+        "title": "ApproveOrRejectRequest"
+      },
+      "hidden": false
+    },
+    {
+      "name": "approve-or-reject-transaction",
+      "description": "Approve or reject a transaction awaiting your review",
+      "inputSchema": {
+        "type": "object",
+        "description": "Approve or reject a transaction awaiting your review.\n\nUse this tool when the user wants to approve a transaction, send it back for\nrevisions, or require the cardholder to repay the full amount. The acting user\nmust have the proper approval authority for the transaction. If the user provides\na written justification (e.g., “reject this because the receipt is missing”), pass\nthat verbatim via `user_reason`—do not invent your own rationale.",
+        "properties": {
+          "action": {
+            "enum": [
+              "APPROVE",
+              "REJECT_AND_REQUEST_CHANGES",
+              "REJECT_AND_REQUEST_FULL_REPAYMENT"
+            ],
+            "title": "TransactionAction",
+            "type": "string",
+            "description": "Action to perform: APPROVE, REJECT_AND_REQUEST_CHANGES (send back to cardholder with requested revisions), or REJECT_AND_REQUEST_FULL_REPAYMENT (require employee repayment)."
+          },
+          "thoughts": {
+            "description": "Your internal reasoning summarizing what the user asked for and why this tool should be invoked.",
+            "title": "Thoughts",
+            "type": "string"
+          },
+          "transaction_id": {
+            "description": "The transaction to act on",
+            "title": "Transaction Id",
+            "type": "string"
+          },
+          "user_reason": {
+            "default": null,
+            "description": "Explanation written by the USER for their decision. Required when requesting changes or full repayment, and should only contain text the user explicitly provided.",
+            "nullable": true,
+            "title": "User Reason",
+            "type": "string"
+          }
+        },
+        "required": [
+          "action",
+          "thoughts",
+          "transaction_id"
+        ],
+        "title": "ApproveOrRejectTransaction"
+      },
+      "hidden": false
+    },
+    {
+      "name": "ask-help-center",
+      "description": "Ask a question and get an answer from Ramp's help center",
+      "inputSchema": {
+        "type": "object",
+        "description": "Ask a question and get an answer from Ramp's help center.\n\nThis tool uses an LLM to read through relevant help center articles and extract\nthe most pertinent information to answer your question. It provides synthesized answers\ncombining multiple sources with extracted relevant snippets and source attribution.\n\nIMPORTANT: If you have other tools that can actually perform the action a user is asking about,\nyou should use those tools instead of or in addition to providing help center information.\nFor example, if a user says \"how can I upload a receipt\", you should tell them they can\nupload a receipt in the chat directly, even if you also find a help center article that\nexplains how to upload receipts in the web app.\n\nUse this tool when you need to:\n- Ask specific questions about Ramp products and features\n- Get answers that combine information from multiple articles\n- Understand complex workflows\n- Get direct answers rather than searching through full articles",
+        "properties": {
+          "question": {
+            "description": "The question to ask about Ramp's help center documentation",
+            "title": "Question",
+            "type": "string"
+          }
+        },
+        "required": [
+          "question"
+        ],
+        "title": "AskHelpCenter"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "attach-receipt-to-transaction",
+      "description": "Attach an existing receipt to a transaction",
+      "inputSchema": {
+        "type": "object",
+        "description": "Attach an existing receipt to a transaction.\n\nUse this tool when the user wants to link an already-created receipt to a specific transaction.\nThe receipt must have been previously created (e.g. via CreateReceipt).",
+        "properties": {
+          "receipt_uuid": {
+            "description": "UUID of the receipt to attach. This should come from a previously created receipt.",
+            "title": "Receipt Uuid",
+            "type": "string"
+          },
+          "transaction_uuid": {
+            "description": "UUID of the transaction to attach the receipt to.",
+            "title": "Transaction Uuid",
+            "type": "string"
+          }
+        },
+        "required": [
+          "receipt_uuid",
+          "transaction_uuid"
+        ],
+        "title": "AttachReceiptToTransaction"
+      },
+      "hidden": false
+    },
+    {
+      "name": "create-trip",
+      "description": "Create a new trip for the acting user",
+      "inputSchema": {
+        "type": "object",
+        "description": "Create a new trip for the acting user.",
+        "properties": {
+          "are_trip_dates_from_booking_receipt_or_user_input": {
+            "title": "Are Trip Dates From Booking Receipt Or User Input",
+            "type": "boolean"
+          },
+          "destinations": {
+            "description": "Required trip destination(s). Infer from available evidence (for example merchant/location context, travel context, or user input). Ask the user only when destination cannot be inferred.",
+            "items": {
+              "properties": {
+                "end_date": {
+                  "default": null,
+                  "description": "End date for this location",
+                  "format": "date-time",
+                  "nullable": true,
+                  "title": "End Date",
+                  "type": "string"
+                },
+                "location": {
+                  "properties": {
+                    "city": {
+                      "default": null,
+                      "description": "City name",
+                      "nullable": true,
+                      "title": "City",
+                      "type": "string"
+                    },
+                    "country": {
+                      "default": null,
+                      "description": "Country name",
+                      "nullable": true,
+                      "title": "Country",
+                      "type": "string"
+                    },
+                    "lat": {
+                      "default": 0,
+                      "description": "Latitude of the location",
+                      "title": "Lat",
+                      "type": "number"
+                    },
+                    "lng": {
+                      "default": 0,
+                      "description": "Longitude of the location",
+                      "title": "Lng",
+                      "type": "number"
+                    },
+                    "state": {
+                      "default": null,
+                      "description": "State name",
+                      "nullable": true,
+                      "title": "State",
+                      "type": "string"
+                    },
+                    "timezone": {
+                      "default": null,
+                      "description": "Timezone",
+                      "nullable": true,
+                      "title": "Timezone",
+                      "type": "string"
+                    }
+                  },
+                  "title": "TravelLocation",
+                  "type": "object",
+                  "description": "The location details"
+                },
+                "start_date": {
+                  "default": null,
+                  "description": "Start date for this location",
+                  "format": "date-time",
+                  "nullable": true,
+                  "title": "Start Date",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "location"
+              ],
+              "title": "TripLocation",
+              "type": "object"
+            },
+            "title": "Destinations",
+            "type": "array"
+          },
+          "end_date": {
+            "default": null,
+            "description": "End date of the trip",
+            "format": "date-time",
+            "nullable": true,
+            "title": "End Date",
+            "type": "string"
+          },
+          "name": {
+            "description": "Name for the trip (e.g., 'NYC Conference', 'Client Visit'). Follow patterns for user's other trip names that have similar purpose, use month/yyyy to disambiguate if multiple trips with same name",
+            "title": "Name",
+            "type": "string"
+          },
+          "rationale": {
+            "description": "How you found out or inferred the field values for the trip",
+            "title": "Rationale",
+            "type": "string"
+          },
+          "start_date": {
+            "default": null,
+            "description": "Start date of the trip",
+            "format": "date-time",
+            "nullable": true,
+            "title": "Start Date",
+            "type": "string"
+          },
+          "trip_purpose": {
+            "default": null,
+            "description": "The purpose of the trip for incorporating into the trip name",
+            "nullable": true,
+            "title": "Trip Purpose",
+            "type": "string"
+          }
+        },
+        "required": [
+          "are_trip_dates_from_booking_receipt_or_user_input",
+          "name",
+          "rationale"
+        ],
+        "title": "CreateTrip"
+      },
+      "hidden": false
+    },
+    {
+      "name": "edit-reimbursement",
+      "description": "Edit a reimbursement field",
+      "inputSchema": {
+        "type": "object",
+        "description": "Edit a reimbursement field. The only supported edit types are memo, funds, and accounting category.\nThis tool allows updating specific fields of a reimbursement that the user has\npermission to edit. Provide at least one field to update.\n\nAfter successfully editing the reimbursement:\n1. Check missing_items to see what is required\n2. For items that CAN be filled via the agent (memo, accounting categories, funds):\n   - Request the missing item from the user\n   - Include the relevant suggestions (suggested_memos, suggested_codings, or suggested_funds)\n3. For items that CANNOT be filled via the agent (trip, attendee, mileage_locations, or if all agent-fillable items are complete):\n   - ALWAYS provide the reimbursement_link URL as a clickable link in your response\n   - Format it as markdown: [link text](reimbursement_link)\n   - Example: \"You can complete your reimbursement here: [Complete reimbursement](https://app.ramp.com/s/reimbursements/xxx)\"\n\nItems are requested in this order: receipt, memo, accounting categories, funds.\n\nIf there are no missing items left, the agent should confirm with the user if they want to submit the reimbursement.",
+        "properties": {
+          "fund_uuid": {
+            "default": null,
+            "description": "UUID of the fund (spend allocation) to charge this reimbursement to",
+            "nullable": true,
+            "title": "Fund Uuid",
+            "type": "string"
+          },
+          "memo": {
+            "default": null,
+            "description": "The memo/description text to set for the reimbursement",
+            "nullable": true,
+            "title": "Memo",
+            "type": "string"
+          },
+          "reimbursement_uuid": {
+            "description": "UUID of the reimbursement to modify. Call GetReimbursements to determine the UUID if it cannot be obtained from context.",
+            "nullable": true,
+            "title": "Reimbursement Uuid",
+            "type": "string"
+          },
+          "tracking_category_selections": {
+            "default": null,
+            "description": "Tracking category assignments (e.g., category, department, project). Must provide both category and option_selection. For BOOLEAN and SINGLE_CHOICE tracking categories, option_selection should be the UUID of the tracking category option. For FREE_FORM_TEXT tracking categories, option_selection should be the freeform text value.",
+            "items": {
+              "description": "A tracking category assignment with both category and option.",
+              "properties": {
+                "category_uuid": {
+                  "description": "UUID of the tracking category (the type of classification, e.g., 'Category', 'Department', or 'Project')",
+                  "title": "Category Uuid",
+                  "type": "string"
+                },
+                "option_selection": {
+                  "description": "For BOOLEAN and SINGLE_CHOICE tracking categories: UUID of the specific tracking category option (e.g., UUID of 'Engineering' within 'Department'), or None to explicitly clear the field (only allowed when the business permits it). For FREE_FORM_TEXT tracking categories: the freeform text value to use (e.g., 'Project Alpha').",
+                  "nullable": true,
+                  "title": "Option Selection",
+                  "type": "string"
+                },
+                "prefilled_suggested_coding_uuid": {
+                  "default": null,
+                  "description": "UUID of the suggested coding that was shown to the user as a prefill. Only set when the user is accepting a prefilled suggestion.",
+                  "nullable": true,
+                  "title": "Prefilled Suggested Coding Uuid",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "category_uuid",
+                "option_selection"
+              ],
+              "title": "TrackingCategorySelection",
+              "type": "object"
+            },
+            "nullable": true,
+            "title": "Tracking Category Selections",
+            "type": "array"
+          }
+        },
+        "required": [
+          "reimbursement_uuid"
+        ],
+        "title": "EditReimbursement"
+      },
+      "hidden": false
+    },
+    {
+      "name": "edit-transaction",
+      "description": "Edit a transaction field",
+      "inputSchema": {
+        "type": "object",
+        "description": "Edit a transaction field. The supported edit types are memo, funds, accounting category, trip, and attendees.\nThis tool allows updating specific fields of a transaction that the user has\npermission to edit. Provide at least one field to update.\n\nAfter successfully editing the transaction:\n1. Check missing_items to see what is required\n2. For items that CAN be filled via the agent (memo, accounting categories, funds, trip, attendees):\n   - Request the missing item from the user\n   - Include the relevant suggestions (suggested_memos, suggested_codings, or suggested_funds)\n3. For items that CANNOT be filled via the agent (if all agent-fillable items are complete):\n   - ALWAYS provide the transaction_link URL as a clickable link in your response\n   - Format it as markdown: [link text](transaction_link)\n   - Example: \"You can complete your transaction here: [Complete transaction](https://app.ramp.com/transactions/xxx)\"\n\nItems are requested in this order: receipt, memo, accounting categories, funds, trip, attendees.\n\nIf there are no missing items left, the agent should confirm with the user if they want to submit the transaction.",
+        "properties": {
+          "attendee_selections": {
+            "description": "Attendee selections: attendee_uuids (Ramp users), non_ramp_attendees (external people), include_self_as_attendee (auto-add self). This is an upsert - provide the complete set.",
+            "properties": {
+              "attendee_uuids": {
+                "default": null,
+                "description": "UUIDs of Ramp user attendees. Obtainable via SearchUser or GetOrgChart or calendar data.",
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Attendee Uuids",
+                "type": "array"
+              },
+              "include_self_as_attendee": {
+                "default": true,
+                "description": "Whether to automatically include the acting user as an attendee.",
+                "title": "Include Self As Attendee",
+                "type": "boolean"
+              },
+              "non_ramp_attendees": {
+                "default": null,
+                "description": "Free-text names of non-Ramp attendees. Last resort when SearchUser cannot find a matching Ramp user.",
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Non Ramp Attendees",
+                "type": "array"
+              }
+            },
+            "title": "AttendeeSelections",
+            "type": "object",
+            "default": null,
+            "nullable": true
+          },
+          "fund_uuid": {
+            "default": null,
+            "description": "UUID of the fund (spend allocation) to charge this transaction to.",
+            "nullable": true,
+            "title": "Fund Uuid",
+            "type": "string"
+          },
+          "memo": {
+            "default": null,
+            "description": "The memo/description text to set for the transaction. Set to empty string ('') if clearing the memo.",
+            "nullable": true,
+            "title": "Memo",
+            "type": "string"
+          },
+          "tracking_category_selections": {
+            "default": null,
+            "description": "Tracking/accounting category assignments (e.g., category, department, project). Must provide both category and option_selection. For BOOLEAN and SINGLE_CHOICE tracking categories, option_selection should be the UUID of the tracking category option, or None to clear the field (only when user explicitly replies 'none' and the business allows it). For FREE_FORM_TEXT tracking categories, option_selection should be the freeform text value. Retrieve these from codings you suggest to the user. Only the codings that are to be updated need to be provided.",
+            "items": {
+              "description": "A tracking category assignment with both category and option.",
+              "properties": {
+                "category_uuid": {
+                  "description": "UUID of the tracking category (the type of classification, e.g., 'Category', 'Department', or 'Project')",
+                  "title": "Category Uuid",
+                  "type": "string"
+                },
+                "option_selection": {
+                  "description": "For BOOLEAN and SINGLE_CHOICE tracking categories: UUID of the specific tracking category option (e.g., UUID of 'Engineering' within 'Department'), or None to explicitly clear the field (only allowed when the business permits it). For FREE_FORM_TEXT tracking categories: the freeform text value to use (e.g., 'Project Alpha').",
+                  "nullable": true,
+                  "title": "Option Selection",
+                  "type": "string"
+                },
+                "prefilled_suggested_coding_uuid": {
+                  "default": null,
+                  "description": "UUID of the suggested coding that was shown to the user as a prefill. Only set when the user is accepting a prefilled suggestion.",
+                  "nullable": true,
+                  "title": "Prefilled Suggested Coding Uuid",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "category_uuid",
+                "option_selection"
+              ],
+              "title": "TrackingCategorySelection",
+              "type": "object"
+            },
+            "nullable": true,
+            "title": "Tracking Category Selections",
+            "type": "array"
+          },
+          "transaction_uuid": {
+            "description": "UUID of the transaction to modify. Call GetUserTransactions to determine the UUID if it cannot be obtained from context.",
+            "nullable": true,
+            "title": "Transaction Uuid",
+            "type": "string"
+          },
+          "trip_selection": {
+            "description": "Trip selection configuration. Provide a trip_uuid to assign/change the transaction to a trip (or None to remove), or set mark_not_part_of_trip to True to mark as not part of any trip.",
+            "properties": {
+              "mark_not_part_of_trip": {
+                "default": false,
+                "description": "Whether to mark the transaction as not part of any trip (satisfies trip policy requirements without assigning to a specific trip).",
+                "title": "Mark Not Part Of Trip",
+                "type": "boolean"
+              },
+              "trip_uuid": {
+                "default": null,
+                "description": "UUID of the trip to assign this transaction to. Obtain a valid UUID from one of the Get/Create trip tools. Set to None to remove the trip from the transaction.",
+                "nullable": true,
+                "title": "Trip Uuid",
+                "type": "string"
+              }
+            },
+            "title": "TripSelection",
+            "type": "object",
+            "default": null,
+            "nullable": true
+          },
+          "user_submitted_fields": {
+            "description": "Fields where the user DIRECTLY provided the specific value in their message. Only include a field if the user explicitly stated that exact value. Do NOT include fields where you (the agent) decided/inferred the value based on context. Examples - INCLUDE in user_submitted_fields: User says 'Team lunch' -> include memo. User says 'Use the Travel fund' -> include fund_uuid. Examples - DO NOT INCLUDE: You decide to change fund based on memo content -> do not include fund_uuid. You infer tracking category from transaction details -> do not include tracking_category_selections.",
+            "items": {
+              "description": "Editable fields for EditTransaction tool.",
+              "enum": [
+                "attendee_selections",
+                "attendee_uuids",
+                "fund_uuid",
+                "memo",
+                "tracking_category_selections",
+                "trip_selection"
+              ],
+              "title": "EditableTransactionField",
+              "type": "string"
+            },
+            "title": "User Submitted Fields",
+            "type": "array"
+          }
+        },
+        "required": [
+          "transaction_uuid"
+        ],
+        "title": "EditTransaction"
+      },
+      "hidden": false
+    },
+    {
+      "name": "get-agent-card-creds",
+      "description": "Get a one-time payment token for a fund",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get a one-time payment token for a fund. Handles card enrollment and purchase instructions automatically.",
+        "properties": {
+          "amount": {
+            "description": "Transaction amount as decimal string (e.g., '45.00')",
+            "title": "Amount",
+            "type": "string"
+          },
+          "currency_code": {
+            "description": "ISO 4217 currency code (e.g., 'USD')",
+            "title": "Currency Code",
+            "type": "string"
+          },
+          "fund_id": {
+            "description": "UUID of the fund to pay from",
+            "title": "Fund Id",
+            "type": "string"
+          },
+          "merchant_country_code": {
+            "description": "2-letter country code (e.g., 'US')",
+            "title": "Merchant Country Code",
+            "type": "string"
+          },
+          "merchant_name": {
+            "description": "Merchant name (e.g., 'Figma Inc')",
+            "title": "Merchant Name",
+            "type": "string"
+          },
+          "merchant_url": {
+            "description": "Merchant website URL (e.g., 'https://figma.com')",
+            "title": "Merchant Url",
+            "type": "string"
+          }
+        },
+        "required": [
+          "amount",
+          "currency_code",
+          "fund_id",
+          "merchant_country_code",
+          "merchant_name",
+          "merchant_url"
+        ],
+        "title": "GetAgentCardCreds"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-agent-card-funds",
+      "description": "List funds that can be used for agent card payments",
+      "inputSchema": {
+        "type": "object",
+        "description": "List funds that can be used for agent card payments. Returns eligible funds with available balance.",
+        "properties": {},
+        "title": "GetAgentCardFunds"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-bill-details",
+      "description": "Get comprehensive details about a specific bill including payment status, approval status, and all metadata",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get comprehensive details about a specific bill including payment status, approval status, and all metadata.\n\nThis tool retrieves submitted bills only. For draft (provisional) bills that have\nnot yet been submitted, use GetDraftBillDetails instead.",
+        "properties": {
+          "bill_id": {
+            "description": "The UUID of the bill to retrieve details for",
+            "title": "Bill Id",
+            "type": "string"
+          }
+        },
+        "required": [
+          "bill_id"
+        ],
+        "title": "GetBillDetails"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-bill-invoices",
+      "description": "Retrieve invoice file attachments for a bill",
+      "inputSchema": {
+        "type": "object",
+        "description": "Retrieve invoice file attachments for a bill.",
+        "properties": {
+          "bill_id": {
+            "description": "The UUID of the bill to retrieve invoices for",
+            "title": "Bill Id",
+            "type": "string"
+          }
+        },
+        "required": [
+          "bill_id"
+        ],
+        "title": "GetBillInvoices"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-bills-for-approval",
+      "description": "Get bills that are pending approval from the current user",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get bills that are pending approval from the current user.\n\nUse this tool when the user wants to see bills they need to approve or asks about\npending approvals. This returns only bills where the user is the next approver in\nthe approval chain.",
+        "properties": {
+          "limit": {
+            "default": 10,
+            "description": "Maximum number of bills to return",
+            "maximum": 50,
+            "minimum": 1,
+            "title": "Limit",
+            "type": "integer"
+          },
+          "page_cursor": {
+            "default": null,
+            "description": "Pagination cursor from a previous response's next_page_cursor. The only valid string values are encrypted cursor tokens from a previous response (long strings starting with 'gAAAAA'). For the first page, for no more results, or for anything that is not one of those encrypted tokens, pass None (never the string 'None').",
+            "nullable": true,
+            "title": "Page Cursor",
+            "type": "string"
+          }
+        },
+        "title": "GetBillsForApproval"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-bookings",
+      "description": "Retrieves flight and hotel bookings for the user",
+      "inputSchema": {
+        "type": "object",
+        "description": "Retrieves flight and hotel bookings for the user.\n\nUse this tool when users ask about their:\n- Hotel bookings or reservations\n- Flight bookings\n- Travel bookings in general\n- Status of a recent booking request\n\nReturns both confirmed bookings and pending/failed booking requests in unified lists.\nCheck the status field: PENDING_APPROVAL, PROCESSING, or FAILED indicate unconfirmed requests.\nIf status is FAILED, the error_message field explains why.\n\nIMPORTANT: Cancelled and failed bookings do NOT block new bookings. If a user has a prior\nbooking with status CANCELLED or a failed request with status FAILED, they can still make\na new booking for the same route, hotel, or trip. Always allow the user to proceed with a\nnew search and booking when they ask to rebook after a cancellation or failure.\n\nIMPORTANT: When presenting results, use Rich Object References (ROR) format:\n- For hotels: [Hotel Name](hotel-uuid) e.g., [Marriott Downtown](abc123-def456)\n- For flights: [Flight Info](flight-uuid) e.g., [UA 100 SFO → JFK](abc123-def456)\nThe 'id' field in each booking is the UUID to use in the reference.",
+        "properties": {
+          "include_flights": {
+            "default": true,
+            "description": "Whether to include flight bookings",
+            "title": "Include Flights",
+            "type": "boolean"
+          },
+          "include_hotels": {
+            "default": true,
+            "description": "Whether to include hotel bookings",
+            "title": "Include Hotels",
+            "type": "boolean"
+          },
+          "limit": {
+            "default": 20,
+            "description": "Maximum number of bookings to return per type",
+            "maximum": 50,
+            "minimum": 1,
+            "title": "Limit",
+            "type": "integer"
+          }
+        },
+        "title": "GetBookings"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-candidate-trips-for-transaction",
+      "description": "Fetch trips that could be relevant to the current transaction",
+      "inputSchema": {
+        "type": "object",
+        "description": "Fetch trips that could be relevant to the current transaction.\nReturns ongoing, upcoming, and recently completed trips for the acting user.",
+        "properties": {},
+        "title": "GetCandidateTripsForTransaction"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-decline-explanation",
+      "description": "Get a detailed explanation of why a transaction was declined",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get a detailed explanation of why a transaction was declined.\n\nIMPORTANT: Only call this tool on transactions that are already known to be\ndeclined. If you need to find declined transactions first, use GetUserTransactions\nwith state='declined'. Do NOT call this on approved or pending transactions —\nit will return a not_declined error.\n\nThis tool provides:\n- Human-readable explanation of the decline reason\n- Structured remediation actions the user or admin can take\n- The SMS/push notification message sent to the user\n- Transaction details (amount, merchant, card, timestamp)\n\nUse this when a user asks why their transaction was declined or what they can do about it.",
+        "properties": {
+          "transaction_uuid": {
+            "description": "The UUID of the declined transaction",
+            "title": "Transaction Uuid",
+            "type": "string"
+          }
+        },
+        "required": [
+          "transaction_uuid"
+        ],
+        "title": "GetDeclineExplanation"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-draft-bill-details",
+      "description": "Get details about a draft (provisional) bill that has not yet been submitted for approval",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get details about a draft (provisional) bill that has not yet been submitted for approval.\n\nUse this tool when the user is viewing a draft bill page (e.g. /bill-pay/bills/list/edit-draft/{uuid})\nor asks about a bill that hasn't been submitted yet. Draft bills are also known as provisional bills.\nReturns vendor info, amount, line items, memo, and other metadata for the draft.",
+        "properties": {
+          "bill_id": {
+            "description": "The UUID of the draft bill to retrieve details for",
+            "title": "Bill Id",
+            "type": "string"
+          }
+        },
+        "required": [
+          "bill_id"
+        ],
+        "title": "GetDraftBillDetails"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-flight-booking-locations",
+      "description": "Resolves locations (airports/cities) available for booking a flight from user intent",
+      "inputSchema": {
+        "type": "object",
+        "description": "Resolves locations (airports/cities) available for booking a flight from user intent.\n\nReturns locations where flights can be booked from or to, which may include:\n- Individual airports (e.g., JFK, SFO, LAX)\n- City groups with multiple airports (e.g., NYC includes JFK, LGA, EWR)\n- Major travel destinations with flight availability",
+        "properties": {
+          "limit": {
+            "default": 5,
+            "description": "Maximum number of location results to return",
+            "title": "Limit",
+            "type": "integer"
+          },
+          "location_type": {
+            "default": "none",
+            "description": "Specific location type to search for: 'airport' for airports only, 'city' for cities only, or 'none' for both",
+            "enum": [
+              "airport",
+              "city",
+              "none"
+            ],
+            "title": "Location Type",
+            "type": "string"
+          },
+          "query": {
+            "description": "The location query from user intent (e.g., 'SF', 'San Francisco', 'NYC', 'JFK', 'Boston Logan')",
+            "title": "Query",
+            "type": "string"
+          }
+        },
+        "required": [
+          "query"
+        ],
+        "title": "GetFlightBookingLocations"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-full-transaction-metadata",
+      "description": "View all details, memos, funds, and receipts for a specific transaction",
+      "inputSchema": {
+        "type": "object",
+        "description": "View all details, memos, funds, and receipts for a specific transaction.",
+        "properties": {
+          "id": {
+            "description": "Transaction id (from tool calls or metadata)",
+            "nullable": true,
+            "title": "Id",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "title": "GetFullTransactionMetadata"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-funds",
+      "description": "Retrieve funds (also known as cards or budgets) that belong to the current user or other users",
+      "inputSchema": {
+        "type": "object",
+        "description": "Retrieve funds (also known as cards or budgets) that belong to the current user or other users.\n\nUse this tool when users ask about:\n- Their funds, cards, or budgets (e.g., \"show me my funds\", \"what cards do I have?\")\n- What they can buy from a specific fund\n- Why their card is locked or not working (e.g., \"why is my card locked?\", \"why can't I use my card?\")\n- Fund balances, restrictions, or lock status\n\nWhen querying for a specific person's funds, first call GetOrgChart to get their UUID,\nthen use the user_uuids parameter. For queries about \"my funds\", use funds_to_retrieve=MY_FUNDS.\nTo search by fund name, use search_by_fund_display_name.\nFor card lock questions, set include_lock_info=True to get lock details.",
+        "properties": {
+          "for_transaction_id": {
+            "default": null,
+            "description": "When provided, retrieves only the funds that this specific transaction can be reassigned to. When this parameter is set, all other parameters are ignored.",
+            "nullable": true,
+            "title": "For Transaction Id",
+            "type": "string"
+          },
+          "funds_to_retrieve": {
+            "enum": [
+              "ALL_FUNDS",
+              "MY_FUNDS"
+            ],
+            "title": "FundsToRetrieve",
+            "type": "string",
+            "default": null,
+            "description": "Scope of funds to retrieve. Use MY_FUNDS ONLY when the user explicitly asks about 'my funds'. Use ALL_FUNDS for general searches (e.g., searching by fund name) or when no specific owner is mentioned. NEVER use this parameter when the user mentions a specific person - use user_uuids instead.",
+            "nullable": true
+          },
+          "include_balance": {
+            "default": false,
+            "description": "Did the user request something related to the balance of the fund? Is the user trying to check if they used their funds this week/month?",
+            "title": "Include Balance",
+            "type": "boolean"
+          },
+          "include_lock_info": {
+            "default": false,
+            "description": "Set to True when the user asks about locks (e.g., 'why is my card locked?', 'how do I unlock my card?'). Adds lock details for the fund and its members, including information about missing policy items.",
+            "title": "Include Lock Info",
+            "type": "boolean"
+          },
+          "include_members": {
+            "default": false,
+            "description": "Set to True when the user asks about who has access to a fund or who are the members of a fund. Returns the names of users who have access to each fund.",
+            "title": "Include Members",
+            "type": "boolean"
+          },
+          "include_restrictions": {
+            "default": false,
+            "description": "Set to True when the user asks about fund restrictions such as: merchant/vendor whitelists or blacklists, category whitelists or blacklists, transaction amount limits, auto-lock dates, expiration dates, or interval/reset dates. This adds a lot of context, so only include it if needed.",
+            "title": "Include Restrictions",
+            "type": "boolean"
+          },
+          "search_by_fund_display_name": {
+            "default": null,
+            "description": "Text search to filter by the display name of the fund itself (e.g., 'office supplies', 'conference budget', 'equipment fund'). This searches what the fund is called, NOT who owns it. NEVER use this parameter when the user mentions a person's name - person names are not fund display names. If searching by owner/person, use user_uuids instead.",
+            "nullable": true,
+            "title": "Search By Fund Display Name",
+            "type": "string"
+          },
+          "state": {
+            "enum": [
+              "ACTIVE",
+              "ARCHIVED",
+              "TERMINATED"
+            ],
+            "title": "SpendAllocationState",
+            "type": "string",
+            "default": null,
+            "description": "Filter funds by state. Use ACTIVE to show only active funds, TERMINATED for terminated funds, or ARCHIVED for archived funds. If not provided, returns funds in all states.",
+            "nullable": true
+          },
+          "user_uuids": {
+            "default": null,
+            "description": "REQUIRED when the user asks about a specific person's funds. Workflow: (1) First call GetOrgChart to find the person and get their UUID, (2) Then pass that UUID here. Use this for any query mentioning a person by name. Do NOT use funds_to_retrieve when asking about a specific person.",
+            "items": {
+              "type": "string"
+            },
+            "nullable": true,
+            "title": "User Uuids",
+            "type": "array"
+          }
+        },
+        "title": "GetUserFunds"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-org-chart",
+      "description": "Get org chart for a user, including reporting chain and direct reports",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get org chart for a user, including reporting chain and direct reports.\n\nThis tool provides comprehensive org chart visibility including:\n- The user's position in the organization\n- Their direct reports (team members)\n- Their reporting chain (managers up the hierarchy)\n\nUse this tool whenever the user asks anything about their manager, team, or direct reports.",
+        "properties": {
+          "user_id": {
+            "default": null,
+            "nullable": true,
+            "title": "User Id",
+            "type": "string"
+          }
+        },
+        "title": "GetOrgChart"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-purchase-order-details",
+      "description": "Get comprehensive details about a specific purchase order",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get comprehensive details about a specific purchase order.\n\nUse this after SearchPurchaseOrders or when the user is already looking at a\npurchase order and wants more detail, such as status, amount, vendor, or the\nassociated unified request ID.",
+        "properties": {
+          "purchase_order_id": {
+            "description": "The UUID of the purchase order to retrieve details for",
+            "title": "Purchase Order Id",
+            "type": "string"
+          }
+        },
+        "required": [
+          "purchase_order_id"
+        ],
+        "title": "GetPurchaseOrderDetails"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-reimbursements",
+      "description": "Search and retrieve reimbursements with filters for users, text search,",
+      "inputSchema": {
+        "type": "object",
+        "description": "Search and retrieve reimbursements with filters for users, text search,\namount ranges, tags, date ranges, approval status, and policy assessments.",
+        "properties": {
+          "from_date": {
+            "default": null,
+            "description": "Start date for filtering reimbursements (YYYY-MM-DD format). Only reimbursements on or after this date will be included. Example: '2024-01-01'",
+            "nullable": true,
+            "title": "From Date",
+            "type": "string"
+          },
+          "include_policy_assessment": {
+            "default": false,
+            "description": "Whether to include AI policy assessment data for each reimbursement. When true, each reimbursement will include a recommended approval action (approve/reject/review) and rationale based on policy analysis. Most useful when reviewing reimbursements for approval.",
+            "title": "Include Policy Assessment",
+            "type": "boolean"
+          },
+          "include_suggestions": {
+            "default": false,
+            "description": "Whether to include suggested memos, codings, and funds for each reimbursement. Only set to true when the user specifically needs autofill suggestions for missing items. Increases response time significantly.",
+            "title": "Include Suggestions",
+            "type": "boolean"
+          },
+          "next_page_cursor": {
+            "default": null,
+            "description": "Use this to get additional results after the first page. Copy the next_page_cursor value from a previous response to continue pagination",
+            "nullable": true,
+            "title": "Next Page Cursor",
+            "type": "string"
+          },
+          "page_size": {
+            "default": 50,
+            "description": "Maximum number of reimbursements to return in one request. Use smaller numbers (10-25) for quick overviews, larger numbers (50-200) for comprehensive analysis",
+            "maximum": 200,
+            "minimum": 1,
+            "title": "Page Size",
+            "type": "integer"
+          },
+          "reimbursement_uuids": {
+            "default": null,
+            "description": "Filter by reimbursement UUIDs",
+            "items": {
+              "type": "string"
+            },
+            "nullable": true,
+            "title": "Reimbursement Uuids",
+            "type": "array"
+          },
+          "reimbursements_to_retrieve": {
+            "description": "Which set of reimbursements to search: your own reimbursements, reimbursements awaiting your approval, or all reimbursements across the business",
+            "enum": [
+              "all_reimbursements",
+              "my_reimbursements",
+              "reimbursements_awaiting_my_approval"
+            ],
+            "title": "ReimbursementSearchScope",
+            "type": "string",
+            "default": "all_reimbursements"
+          },
+          "search_string": {
+            "default": null,
+            "description": "Search for reimbursements with matching merchant name, memo, or cardholder name",
+            "nullable": true,
+            "title": "Search String",
+            "type": "string"
+          },
+          "tags": {
+            "default": null,
+            "description": "Additional tag-based filters. Currently supported tags are User, ReimbursementStatus, ReimbursementType, SpendAllocation, and Merchant. You must provide actual UUIDs or enum values - use other tools to retrieve UUIDs if needed. If a user is asking about their own reimbursements, you must include the User tag with their UUID.",
+            "items": {
+              "description": "Tag filter for reimbursements search.\n\nFor user, spend allocation, and merchant tags, the tag_id should be the UUID of the entity.\nFor reimbursement status and type tags, the tag_id should be the enum value of the status or type.\n\nIMPORTANT: You must provide actual UUIDs or enum values as tag_id. Do NOT use empty strings, placeholder values,\nor generic identifiers - these will cause errors. If you don't know a UUID, use other available tools to retrieve it first.\n\nAvailable reimbursement statuses: DRAFT, PENDING, APPROVED, AWAITING_PAYMENT, PROCESSING, PAID, REJECTED, PAYMENT_ERROR\nAvailable reimbursement types: OUT_OF_POCKET, MILEAGE, PER_DIEM",
+              "properties": {
+                "tag_id": {
+                  "description": "The UUID or enum value for the tag",
+                  "title": "Tag Id",
+                  "type": "string"
+                },
+                "tag_type": {
+                  "description": "The type of search tag category",
+                  "enum": [
+                    "merchant",
+                    "reimbursement_status",
+                    "reimbursement_type",
+                    "spend_allocation",
+                    "user"
+                  ],
+                  "title": "Tag Type",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "tag_id",
+                "tag_type"
+              ],
+              "title": "ReimbursementTag",
+              "type": "object"
+            },
+            "nullable": true,
+            "title": "Tags",
+            "type": "array"
+          },
+          "to_date": {
+            "default": null,
+            "description": "End date for filtering reimbursements (YYYY-MM-DD format). Only reimbursements on or before this date will be included. Example: '2024-12-31'",
+            "nullable": true,
+            "title": "To Date",
+            "type": "string"
+          }
+        },
+        "title": "GetReimbursements"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-reimbursements-for-approval",
+      "description": "Get reimbursements that require approval from the current user",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get reimbursements that require approval from the current user.\n\nReturns 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.",
+        "properties": {
+          "limit": {
+            "default": 10,
+            "title": "Limit",
+            "type": "integer"
+          }
+        },
+        "title": "GetReimbursementsForApproval"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-requests-to-review",
+      "description": "Get requests that require the current user's review and approval",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get requests that require the current user's review and approval.\n\nReturns purchase orders, fund requests, and procurement requests pending approval. Essential tool for checking request approvals - always use when users ask about approvals, pending items, approval queue, or need to review anything. Does not include expenses like transactions and reimbursements (use separate tools for those). Results include requester details, amounts, dates, and approval status.\nOnly handles lookups, does not take any action.",
+        "properties": {
+          "page_size": {
+            "default": 50,
+            "description": "Number of requests to return per page (1-100)",
+            "maximum": 100,
+            "minimum": 1,
+            "title": "Page Size",
+            "type": "integer"
+          },
+          "request_types": {
+            "description": "Types of spend requests to include (defaults to all types: PURCHASE_ORDER, SPEND_ALLOCATION, APPROVAL_ONLY, PROCUREMENT_SPEND_ALLOCATION)",
+            "items": {
+              "enum": [
+                "APPROVAL_ONLY",
+                "PROCUREMENT_SPEND_ALLOCATION",
+                "PURCHASE_ORDER",
+                "SPEND_ALLOCATION",
+                "TRAVEL"
+              ],
+              "title": "UnifiedSpendRequestType",
+              "type": "string"
+            },
+            "title": "Request Types",
+            "type": "array"
+          },
+          "start": {
+            "default": null,
+            "description": "Pagination cursor for next page",
+            "nullable": true,
+            "title": "Start",
+            "type": "string"
+          },
+          "thoughts": {
+            "description": "Is the user trying approve funds or purchase orders? Should we also check if there are transactions/reimbursements to approve via other tools? Is the user looking for _what_ to approve (use this tool) or actually trying to approve an object we already looked up (which should be another tool)?",
+            "title": "Thoughts",
+            "type": "string"
+          }
+        },
+        "required": [
+          "thoughts"
+        ],
+        "title": "GetRequestsToReview"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-simplified-user-detail",
+      "description": "Get the current user's details",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get the current user's details.\n\nReturns multiple results for users that are part of multiple businesses.",
+        "properties": {},
+        "title": "GetSimplifiedUserDetail"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-tracking-categories",
+      "description": "Retrieve all active tracking categories for the current business",
+      "inputSchema": {
+        "type": "object",
+        "description": "Retrieve all active tracking categories for the current business.\n\nTracking categories are used to organize and categorize transactions in the accounting system.\nCommon examples include:\n- Departments (e.g., Engineering, Sales, Marketing)\n- Classes or Business Units\n- Locations (e.g., US East, US West)\n- Projects\n- Customers\n- Cost Centers\n\nThis tool returns only the tracking category metadata, not the available options.\nTo get the options for a specific tracking category, use GetTrackingCategoryOptions.\n\nThis tool should mainly be used as a helper tool to identify tracking categories when users want to set\naccounting categories on transactions.",
+        "properties": {
+          "include_hidden": {
+            "default": false,
+            "description": "Set to True to include hidden categories. By default, only visible categories are returned.",
+            "title": "Include Hidden",
+            "type": "boolean"
+          },
+          "transaction_uuid": {
+            "default": null,
+            "description": "UUID of the transaction being coded. When provided, ensures the correct business context is used to look up tracking categories.",
+            "nullable": true,
+            "title": "Transaction Uuid",
+            "type": "string"
+          }
+        },
+        "title": "GetTrackingCategories"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-tracking-category-options",
+      "description": "Retrieve options for a specific tracking category with optional search",
+      "inputSchema": {
+        "type": "object",
+        "description": "Retrieve options for a specific tracking category with optional search.\n\nUse this tool to get the available options (e.g., specific departments, locations, projects)\nfor a tracking category. This tool supports pagination for tracking categories that have\nlarge numbers of options (some businesses can have millions of options). It is highly encouraged\nto use the query_string parameter to filter options by name when possible.\n\nWhen being used to set a coding for a transaction, you MUST pass the transaction_uuid parameter and set include_hidden to False\nto filter out hidden options based on subsidiary/conditional filtering. The transaction_uuid should only not be set when\ndoing generic searches over tracking category options.\n\nSearch behavior:\n- When query_string is provided and semantic search is enabled (via feature flag), the tool uses\n  turbopuffer semantic search combined with ILIKE for better results. Pagination is not supported\n  in this mode and falls back to the paginated endpoint on failure.\n- Otherwise, the tool uses simple ILIKE filtering with pagination support.\n\nWorkflow:\n1. First call GetTrackingCategories to get the list of tracking categories\n2. Then call this tool with the tracking_category_uuid to get the options, using query_string when possible and the transaction_uuid to be coded\n3. If next_page_cursor is returned, call again with that cursor to get more results if necessary\n\nThis tool should mainly be used to identify tracking category options when users want to set\naccounting categories on transactions. There is no need to use this tool if the user wants to use a\nsuggested coding that we already know the option UUID for.",
+        "properties": {
+          "include_hidden": {
+            "default": false,
+            "description": "Set to True to include hidden options. By default, only visible options are returned.",
+            "title": "Include Hidden",
+            "type": "boolean"
+          },
+          "next_page_cursor": {
+            "default": null,
+            "description": "Use this to get additional results after the first page. Copy the next_page_cursor value from a previous response to continue pagination",
+            "nullable": true,
+            "title": "Next Page Cursor",
+            "type": "integer"
+          },
+          "page_size": {
+            "default": 50,
+            "description": "Maximum number of options to return in one request. Use smaller numbers (10-25) for quick overviews, larger numbers (50-100) for comprehensive views",
+            "minimum": 1,
+            "title": "Page Size",
+            "type": "integer"
+          },
+          "query_string": {
+            "default": null,
+            "description": "Optional search string to filter options by name. Useful for finding specific options.",
+            "nullable": true,
+            "title": "Query String",
+            "type": "string"
+          },
+          "tracking_category_uuid": {
+            "description": "UUID of the tracking category to get options for. Obtain this from GetTrackingCategories.",
+            "title": "Tracking Category Uuid",
+            "type": "string"
+          },
+          "transaction_uuid": {
+            "default": null,
+            "description": "UUID of the transaction to filter options for when coding it. When provided, applies conditional filtering based on the transaction's user, department, location, etc. to exclude options that are hidden for that specific transaction context.",
+            "nullable": true,
+            "title": "Transaction Uuid",
+            "type": "string"
+          }
+        },
+        "required": [
+          "tracking_category_uuid"
+        ],
+        "title": "GetTrackingCategoryOptions"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-transaction-missing-items",
+      "description": "Check what receipts, memos, or accounting items are missing from a specific transaction",
+      "inputSchema": {
+        "type": "object",
+        "description": "Check what receipts, memos, or accounting items are missing from a specific transaction.",
+        "properties": {
+          "id": {
+            "description": "Transaction id (based on metadata or tool calls).",
+            "nullable": true,
+            "title": "Id",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "title": "GetTransactionMissingItems"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-transaction-suggested-memos",
+      "description": "Get AI-suggested memo/note options for a specific transaction",
+      "inputSchema": {
+        "type": "object",
+        "description": "Get AI-suggested memo/note options for a specific transaction.",
+        "properties": {
+          "id": {
+            "description": "The ID of the transaction to retrieve suggested memos for.",
+            "nullable": true,
+            "title": "Id",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "title": "GetTransactionSuggestedMemos"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-transactions",
+      "description": "Search and retrieve expense transactions from Ramp",
+      "inputSchema": {
+        "type": "object",
+        "description": "Search and retrieve expense transactions from Ramp\n\nThis tool helps you find card transactions. Use this tool when users want to:\n- View their recent transactions or expenses\n- Search for specific purchases by merchant, amount, or description\n- Find transactions that need approval\n- Analyze spending patterns\n- Review transactions by specific team members\n- Look up transactions with missing documentation and retrieve suggestions\n- View declined transactions (set state='declined')\n\nThe tool returns structured transaction data including amounts, merchants, dates,\nemployee names, policy compliance status, and missing documentation requirements + suggestions\n\nIMPORTANT: By default, declined transactions are NOT included in results. If a user asks\nabout declined, rejected, or failed transactions, you MUST set state='declined' to include them.\n\nIf the transaction the user is looking for or discussing is not returned, try again\nwith a different business_uuid — the user may have accounts across multiple businesses.\nYou can call this tool multiple times with different business_uuid values to get\ntransactions from all businesses for a given user.",
+        "properties": {
+          "business_uuid": {
+            "default": null,
+            "description": "The business UUID to scope the transaction search to. When the user has multiple businesses, use this to specify which business to query. If not available from context, retrieve it from GetSimplifiedUserDetail. If not provided, defaults to the first user's business.",
+            "nullable": true,
+            "title": "Business Uuid",
+            "type": "string"
+          },
+          "details_to_include_in_response": {
+            "default": null,
+            "description": "Additional detailed information to include for each transaction. Options: policy assessment data (for reviewers approving transactions), missing documentation details (what receipts or approvals are needed), suggestions for transaction items (memos, codings, and funds), and submitted items (receipts, trips, attendees, and accounting categories currently on the transaction)",
+            "items": {
+              "enum": [
+                "policy_assessment_for_reviewers",
+                "submitted_items",
+                "suggestions_for_transaction_items",
+                "transaction_documentation_and_missing_items"
+              ],
+              "title": "DetailedField",
+              "type": "string"
+            },
+            "nullable": true,
+            "title": "Details To Include In Response",
+            "type": "array"
+          },
+          "filters": {
+            "description": "Advanced filters to narrow down transactions by specific criteria like merchant categories, spending allocations, or business trips. Multiple filters use conjunction logic (AND) - e.g., merchant='Starbucks' AND fund='Marketing Budget'",
+            "properties": {
+              "filters": {
+                "description": "List of filter criteria to apply. All filters are combined with AND logic",
+                "items": {
+                  "description": "A single filter to apply to transaction search.",
+                  "properties": {
+                    "filter": {
+                      "description": "The specific value to filter by. Must match exactly for categories (e.g., 'Taxi and Rideshare', 'Airlines'). Can be partial match for merchant, spend_allocation, trip, and tracking_category.",
+                      "title": "Filter",
+                      "type": "string"
+                    },
+                    "filter_type": {
+                      "description": "Type of filter to apply:\n- 'category': Expense category. Valid categories: Airlines, Car Rental, Lodging, Taxi and Rideshare, Fuel and Gas, Restaurants, Alcohol and Bars, Office supplies and cleaning, Office, Electronics, Clothing, Books and Newspapers, General Merchandise, Streaming Services, Entertainment, Supermarkets and Grocery Stores, Medical, Pet, Shipping, Utilities, Professional Services, Advertising, Fees and Financial institutions, Taxes and tax preparation, Other\n- 'merchant': Specific merchant/vendor name like 'Starbucks', 'Amazon', 'Uber', 'Delta Airlines'\n- 'spend_allocation': Spending allocation/budget/fund name like 'Marketing Budget', 'Engineering Fund', 'Wellness Stipend'\n- 'trip': Business trip/event/conference name. IMPORTANT: Trip names are the EVENT names (e.g., 'ERP Conference', 'Q4 Sales Offsite', 'Client Summit 2024'), NOT city/location names. When a user asks about 'travel to/from [city] for [event]', the trip filter should be the EVENT name (e.g., 'ERP Conference'), not the destination city (e.g., 'New York City'). Cities mentioned are travel origins/destinations, not trip names.\n- 'tracking_category': Accounting coding / tracking category option name or code. Use this to filter transactions by their accounting coding values (e.g., 'Engineering', 'Marketing', 'US East', 'ENG-001'). Searches across all active tracking categories (Department, Cost Center, GL Account, etc.). Only available for businesses with a connected accounting integration.",
+                      "enum": [
+                        "category",
+                        "merchant",
+                        "spend_allocation",
+                        "tracking_category",
+                        "trip"
+                      ],
+                      "title": "Filter Type",
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "filter",
+                    "filter_type"
+                  ],
+                  "title": "FilterCriteria",
+                  "type": "object"
+                },
+                "title": "Filters",
+                "type": "array"
+              }
+            },
+            "required": [
+              "filters"
+            ],
+            "title": "Filter",
+            "type": "object",
+            "default": null,
+            "nullable": true
+          },
+          "from_date": {
+            "default": null,
+            "description": "Start date for filtering transactions (YYYY-MM-DD format). Only transactions on or after this date will be included. Example: '2024-01-01'",
+            "nullable": true,
+            "title": "From Date",
+            "type": "string"
+          },
+          "include_count": {
+            "default": true,
+            "description": "Whether to include the total count of matching transactions in the response. Set to false only if you just need the transaction data and want faster responses",
+            "title": "Include Count",
+            "type": "boolean"
+          },
+          "next_page_cursor": {
+            "default": null,
+            "description": "Use this to get additional results after the first page. Copy the next_page_cursor value from a previous response to continue pagination",
+            "nullable": true,
+            "title": "Next Page Cursor",
+            "type": "string"
+          },
+          "page_size": {
+            "default": 50,
+            "description": "Maximum number of transactions to return in one request. Use smaller numbers (10-25) for quick overviews, larger numbers (50-200) for comprehensive analysis",
+            "maximum": 200,
+            "minimum": 1,
+            "title": "Page Size",
+            "type": "integer"
+          },
+          "reason_memo_merchant_or_user_name_text_search": {
+            "default": null,
+            "description": "Text search across merchant names, transaction descriptions/memos, and employee names. Must be at least 3 characters long. Examples: 'Starbucks', 'office supplies', 'John Smith'. Trip names, attendees and fund budget names are not searchable from this field",
+            "nullable": true,
+            "title": "Reason Memo Merchant Or User Name Text Search",
+            "type": "string"
+          },
+          "sort": {
+            "description": "How to sort the results. You can sort by user (employee name), merchant name, or transaction date in ascending or descending order. By default we sort by transaction date descending",
+            "properties": {
+              "direction": {
+                "enum": [
+                  "asc",
+                  "desc"
+                ],
+                "title": "SortDirection",
+                "type": "string",
+                "description": "Sort order: ascending or descending"
+              },
+              "sort_by": {
+                "description": "Which field to sort by",
+                "enum": [
+                  "merchant",
+                  "transaction_date",
+                  "user"
+                ],
+                "title": "SortBy",
+                "type": "string"
+              }
+            },
+            "required": [
+              "direction",
+              "sort_by"
+            ],
+            "title": "Sort",
+            "type": "object",
+            "nullable": true
+          },
+          "state": {
+            "description": "Filter transactions by their state. Use 'declined' when the user asks about declined or failed transactions. Use 'pending' for pending/processing transactions, 'cleared' for completed transactions, or 'all' to include all states. When not specified, only non-declined transactions are returned by default.",
+            "enum": [
+              "all",
+              "cleared",
+              "declined",
+              "pending"
+            ],
+            "title": "TransactionStateFilter",
+            "type": "string",
+            "default": null,
+            "nullable": true
+          },
+          "to_date": {
+            "default": null,
+            "description": "End date for filtering transactions (YYYY-MM-DD format). Only transactions on or before this date will be included. Example: '2024-12-31'",
+            "nullable": true,
+            "title": "To Date",
+            "type": "string"
+          },
+          "transactions_to_retrieve": {
+            "description": "Which set of transactions to search: your own transactions, transactions awaiting your approval, all company transactions (if you have access), or transactions made by your team members",
+            "enum": [
+              "all_transactions_across_entire_business",
+              "my_transactions",
+              "transactions_awaiting_my_approval",
+              "transactions_made_by_my_team"
+            ],
+            "title": "TransactionSearchScope",
+            "type": "string"
+          }
+        },
+        "required": [
+          "transactions_to_retrieve"
+        ],
+        "title": "GetUserTransactions"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "get-user-trips",
+      "description": "Fetch trips for the acting user with optional filters",
+      "inputSchema": {
+        "type": "object",
+        "description": "Fetch trips for the acting user with optional filters.",
+        "properties": {
+          "cursor": {
+            "default": null,
+            "description": "Opaque bookmark returned by the API for pagination.",
+            "nullable": true,
+            "title": "Cursor",
+            "type": "string"
+          },
+          "page_size": {
+            "default": null,
+            "description": "Optional number of trips to return per page.",
+            "maximum": 100,
+            "minimum": 1,
+            "nullable": true,
+            "title": "Page Size",
+            "type": "integer"
+          },
+          "status": {
+            "default": null,
+            "description": "Optional trip status filter.",
+            "enum": [
+              "completed",
+              "ongoing",
+              "upcoming"
+            ],
+            "nullable": true,
+            "title": "Status",
+            "type": "string"
+          }
+        },
+        "title": "GetUserTrips"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "list-cards",
+      "description": "List active cards for the current user",
+      "inputSchema": {
+        "type": "object",
+        "description": "List active cards for the current user.",
+        "properties": {},
+        "title": "ListCards"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "lock-or-unlock-card",
+      "description": "Lock or unlock a card",
+      "inputSchema": {
+        "type": "object",
+        "description": "Lock or unlock a card.\n\nUse this tool when:\n- A user wants to temporarily lock their card (lock)\n- A user wants to unlock a previously locked card (unlock)\n\nIMPORTANT: Locking a card is a destructive action. Before calling this tool with action='lock', you MUST:\n1. Confirm the card details with the user (show them which card will be affected)\n2. Explain that locking the card will prevent all transactions until unlocked\n3. Ask the user to explicitly confirm they want to lock the card (e.g., \"Yes, lock my card\")\n4. Only proceed if the user has explicitly confirmed the action\n\nDo NOT lock a card based on assumptions about suspicious activity or compromised cards.\nThe user must explicitly request and confirm the lock action.\n\nFor unlocking, confirmation is not required since this is a non-destructive action.",
+        "properties": {
+          "action": {
+            "enum": [
+              "lock",
+              "unlock"
+            ],
+            "title": "Action",
+            "type": "string"
+          },
+          "id": {
+            "description": "The UUID of the card to lock or unlock.",
+            "title": "Id",
+            "type": "string"
+          }
+        },
+        "required": [
+          "action",
+          "id"
+        ],
+        "title": "LockOrUnlockCard"
+      },
+      "hidden": false
+    },
+    {
+      "name": "mark-transaction-missing-receipt",
+      "description": "Flag a transaction as having no receipt",
+      "inputSchema": {
+        "type": "object",
+        "description": "Flag a transaction as having no receipt.\n\nShould be called whenever the user says \"OOPS\" or if the user says something along the lines of \"I did not receive a receipt ...\". If the user already flagged the transaction as having no receipt, then you may need to call the ProvideNoReceiptReason tool.",
+        "properties": {
+          "transaction_uuid": {
+            "description": "What transaction are they talking about? If they said OOPS, they are referring to the latest transaction.",
+            "nullable": true,
+            "title": "Transaction Uuid",
+            "type": "string"
+          }
+        },
+        "required": [
+          "transaction_uuid"
+        ],
+        "title": "MarkTransactionMissingReceipt"
+      },
+      "hidden": false
+    },
+    {
+      "name": "post-comment",
+      "description": "Post a comment on a Ramp object (transaction, bill, reimbursement, etc)",
+      "inputSchema": {
+        "type": "object",
+        "description": "Post a comment on a Ramp object (transaction, bill, reimbursement, etc).\n\nIf there is any ambiguity as to whether the user's message is meant to be\nposted to the thread, ask them for confirmation first: 'Do you want me to post that\nas a comment reply on your [XYZ] transaction/reimbursement/bill/etc?'.\n\nHow can you determine if the user's message is meant to be a reply to a comment?\n  - If the only other messages in the conversation history are notifications about comments or mentions in Ramp, that is a very strong signal that the user's most recent message is meant to be a reply to the comment thread. In this case, you may use this tool immediately to post the comment without confirmation.\n  - If a recent assistant message is a notification about a comment or mention, that is a strong signal that the user's most recent message is meant to be a reply to that comment. Even if their reply seems irrelevant or unrelated to Ramp, you may ask \"Would you like me to post that as a comment on your...?\" - prefer asking the user instead of refusing to serve the request at all.",
+        "properties": {
+          "mention_user_uuids": {
+            "description": "List of user UUIDs to @-mention in the comment. If the user is replying to a recent comment or mention notification from the assistant, you must use this to set the UUID of the user they are replying to. The mentioned users will be notified and their names will be prepended to the comment message as @-mentions. Extract user UUIDs from the context when the user wants to mention someone (e.g., 'tell Bob that...' -> find Bob's UUID and include it here). If the user's message includes Slack-formatted @-mentions, use the ResolveSlackMention tool to turn those into user UUIDs",
+            "items": {
+              "type": "string"
+            },
+            "title": "Mention User Uuids",
+            "type": "array"
+          },
+          "message": {
+            "description": "The comment message text. If the user sends 'its done' -> post 'its done' to the comment thread. If the user sends 'its done' -> DO NOT post 'The receipt has been uploaded.' or any other variation. Do not correct spelling or punctuation or grammar. Do not include user @-mentions in this field - use mention_user_uuids instead and they will be added automatically. You may also replace Slack-formatted @-mentions with a user's full name by resolving it with the ResolveSlackMention tool.",
+            "title": "Message",
+            "type": "string"
+          },
+          "ramp_object_type": {
+            "description": "Type of the Ramp object. Valid options are: 'reimbursement', 'transaction', 'bill', 'card', 'spend_request', 'spend_intent', 'ticket', 'payee', 'booking_request', 'provisional_bill', or 'vendor_payment'.",
+            "enum": [
+              "bill",
+              "booking_request",
+              "card",
+              "payee",
+              "provisional_bill",
+              "reimbursement",
+              "spend_intent",
+              "spend_request",
+              "ticket",
+              "transaction",
+              "vendor_payment"
+            ],
+            "title": "RampObjectType",
+            "type": "string"
+          },
+          "ramp_object_uuid": {
+            "description": "UUID of the Ramp object to post a comment on. This can be extracted from notification messages.",
+            "title": "Ramp Object Uuid",
+            "type": "string"
+          }
+        },
+        "required": [
+          "message",
+          "ramp_object_type",
+          "ramp_object_uuid"
+        ],
+        "title": "PostComment"
+      },
+      "hidden": false
+    },
+    {
+      "name": "provide-no-receipt-reason",
+      "description": "Only call this tool if we directly ask for a no receipt reason",
+      "inputSchema": {
+        "type": "object",
+        "description": "Only call this tool if we directly ask for a no receipt reason. If a user is trying to mark their transaction as no receipt, use the MarkTransactionMissingReceipt tool. If the user is responding to a message that is asking for a reason for the user's receipt, then call this tool.",
+        "properties": {
+          "reason": {
+            "description": "The reason the user is providing for not having a receipt.",
+            "title": "Reason",
+            "type": "string"
+          },
+          "transaction_uuid": {
+            "description": "What transaction are they talking about? If they said OOPS, they are referring to the latest transaction.",
+            "nullable": true,
+            "title": "Transaction Uuid",
+            "type": "string"
+          }
+        },
+        "required": [
+          "reason",
+          "transaction_uuid"
+        ],
+        "title": "ProvideNoReceiptReason"
+      },
+      "hidden": false
+    },
+    {
+      "name": "search-bills",
+      "description": "Search for bills using natural language queries like vendor names, amounts, or invoice numbers",
+      "inputSchema": {
+        "type": "object",
+        "description": "Search for bills using natural language queries like vendor names, amounts, or invoice numbers.",
+        "properties": {
+          "include_paid": {
+            "default": true,
+            "description": "Whether to include paid bills in results",
+            "title": "Include Paid",
+            "type": "boolean"
+          },
+          "limit": {
+            "default": 10,
+            "description": "Maximum number of bills to return (max 50)",
+            "minimum": 1,
+            "title": "Limit",
+            "type": "integer"
+          },
+          "page_cursor": {
+            "default": null,
+            "description": "Pagination cursor from a previous response's next_page_cursor. The only valid string values are encrypted cursor tokens from a previous response (long strings starting with 'gAAAAA'). For the first page, for no more results, or for anything that is not one of those encrypted tokens, pass None (never the string 'None').",
+            "nullable": true,
+            "title": "Page Cursor",
+            "type": "string"
+          },
+          "query": {
+            "description": "Search for this string in payee name, invoice number, or payment ID of the bill. Examples: 'UPS' or 'Corodata' or 'INV-1722'.  Will find partial matches (e.g. 'UPS' will find 'UPS Store' and '1722' will find 'INV-1722').",
+            "title": "Query",
+            "type": "string"
+          }
+        },
+        "required": [
+          "query"
+        ],
+        "title": "SearchBills"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "search-purchase-orders",
+      "description": "Search for purchase orders using structured purchase order filters",
+      "inputSchema": {
+        "type": "object",
+        "description": "Search for purchase orders using structured purchase order filters.",
+        "properties": {
+          "filters": {
+            "description": "Structured purchase order filters. For free-text vendor / PO / owner lookup, set filters.search. You can also provide status, payee, owner, or other PurchaseOrderQueryV2Filters fields.",
+            "properties": {
+              "accounting_sync_task_statuses": {
+                "default": null,
+                "items": {
+                  "description": "The status of a purchase order accounting provider sync task to display on FE",
+                  "enum": [
+                    "COMPLETED",
+                    "FAILED",
+                    "IN_PROGRESS",
+                    "NOT_SYNCED"
+                  ],
+                  "title": "PurchaseOrderAccountingSyncTaskStatusToDisplay",
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Accounting Sync Task Statuses",
+                "type": "array"
+              },
+              "available_for_agreement_linking": {
+                "default": null,
+                "nullable": true,
+                "title": "Available For Agreement Linking",
+                "type": "boolean"
+              },
+              "bill_to_address_ids": {
+                "default": null,
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Bill To Address Ids",
+                "type": "array"
+              },
+              "coordinator_ids": {
+                "default": null,
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Coordinator Ids",
+                "type": "array"
+              },
+              "created_by_user_uuids": {
+                "default": null,
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Created By User Uuids",
+                "type": "array"
+              },
+              "currencies": {
+                "default": null,
+                "items": {
+                  "description": "We attempted to dynamically create this class from the ISO4217Currency and CryptoCurrency enums.\nHowever, mypy was not able to infer the type of the Currency enum; so we manually added the currencies to the enum.",
+                  "enum": [
+                    "AED",
+                    "AFN",
+                    "ALL",
+                    "AMD",
+                    "ANG",
+                    "AOA",
+                    "ARS",
+                    "AUD",
+                    "AWG",
+                    "AZN",
+                    "BAM",
+                    "BBD",
+                    "BDT",
+                    "BGN",
+                    "BHD",
+                    "BIF",
+                    "BMD",
+                    "BND",
+                    "BOB",
+                    "BOV",
+                    "BRL",
+                    "BSD",
+                    "BTN",
+                    "BWP",
+                    "BYN",
+                    "BZD",
+                    "CAD",
+                    "CDF",
+                    "CHE",
+                    "CHF",
+                    "CHW",
+                    "CLF",
+                    "CLP",
+                    "CNH",
+                    "CNY",
+                    "COP",
+                    "COU",
+                    "CRC",
+                    "CUC",
+                    "CUP",
+                    "CVE",
+                    "CZK",
+                    "DJF",
+                    "DKK",
+                    "DOP",
+                    "DZD",
+                    "EGP",
+                    "ERN",
+                    "ETB",
+                    "EUR",
+                    "EURC",
+                    "FJD",
+                    "FKP",
+                    "GBP",
+                    "GEL",
+                    "GHS",
+                    "GIP",
+                    "GMD",
+                    "GNF",
+                    "GTQ",
+                    "GYD",
+                    "HKD",
+                    "HNL",
+                    "HRK",
+                    "HTG",
+                    "HUF",
+                    "IDR",
+                    "ILS",
+                    "INR",
+                    "IQD",
+                    "IRR",
+                    "ISK",
+                    "JMD",
+                    "JOD",
+                    "JPY",
+                    "KES",
+                    "KGS",
+                    "KHR",
+                    "KMF",
+                    "KPW",
+                    "KRW",
+                    "KWD",
+                    "KYD",
+                    "KZT",
+                    "LAK",
+                    "LBP",
+                    "LKR",
+                    "LRD",
+                    "LSL",
+                    "LYD",
+                    "MAD",
+                    "MDL",
+                    "MGA",
+                    "MKD",
+                    "MMK",
+                    "MNT",
+                    "MOP",
+                    "MRU",
+                    "MUR",
+                    "MVR",
+                    "MWK",
+                    "MXN",
+                    "MXV",
+                    "MYR",
+                    "MZN",
+                    "NAD",
+                    "NGN",
+                    "NIO",
+                    "NOK",
+                    "NPR",
+                    "NZD",
+                    "OMR",
+                    "PAB",
+                    "PEN",
+                    "PGK",
+                    "PHP",
+                    "PKR",
+                    "PLN",
+                    "PYG",
+                    "QAR",
+                    "RON",
+                    "RSD",
+                    "RUB",
+                    "RWF",
+                    "SAR",
+                    "SBD",
+                    "SCR",
+                    "SDG",
+                    "SEK",
+                    "SGD",
+                    "SHP",
+                    "SLE",
+                    "SLL",
+                    "SOS",
+                    "SRD",
+                    "SSP",
+                    "STN",
+                    "SVC",
+                    "SYP",
+                    "SZL",
+                    "THB",
+                    "TJS",
+                    "TMT",
+                    "TND",
+                    "TOP",
+                    "TRY",
+                    "TTD",
+                    "TWD",
+                    "TZS",
+                    "UAH",
+                    "UGX",
+                    "USD",
+                    "USDB",
+                    "USDC",
+                    "USN",
+                    "UYI",
+                    "UYU",
+                    "UYW",
+                    "UZS",
+                    "VED",
+                    "VES",
+                    "VND",
+                    "VUV",
+                    "WST",
+                    "XAD",
+                    "XAF",
+                    "XAG",
+                    "XAU",
+                    "XBA",
+                    "XBB",
+                    "XBC",
+                    "XBD",
+                    "XCD",
+                    "XCG",
+                    "XDR",
+                    "XOF",
+                    "XPD",
+                    "XPF",
+                    "XPT",
+                    "XSU",
+                    "XTS",
+                    "XUA",
+                    "XXX",
+                    "YER",
+                    "ZAR",
+                    "ZMW",
+                    "ZWG",
+                    "ZWL"
+                  ],
+                  "title": "Currency",
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Currencies",
+                "type": "array"
+              },
+              "custom_form_response_filters": {
+                "default": null,
+                "items": {
+                  "properties": {
+                    "custom_form_collection_id": {
+                      "title": "Custom Form Collection Id",
+                      "type": "integer"
+                    },
+                    "form_field_filters": {
+                      "additionalProperties": {
+                        "$ref": "#/components/schemas/FormFieldFilterRequestBody"
+                      },
+                      "title": "Form Field Filters",
+                      "type": "object"
+                    }
+                  },
+                  "required": [
+                    "custom_form_collection_id",
+                    "form_field_filters"
+                  ],
+                  "title": "PurchaseOrderCustomFormResponseFilter",
+                  "type": "object"
+                },
+                "nullable": true,
+                "title": "Custom Form Response Filters",
+                "type": "array"
+              },
+              "entity_uuids": {
+                "default": null,
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Entity Uuids",
+                "type": "array"
+              },
+              "has_virtual_card": {
+                "default": null,
+                "nullable": true,
+                "title": "Has Virtual Card",
+                "type": "boolean"
+              },
+              "include_deleted": {
+                "default": false,
+                "title": "Include Deleted",
+                "type": "boolean"
+              },
+              "is_renewal_request": {
+                "default": null,
+                "nullable": true,
+                "title": "Is Renewal Request",
+                "type": "boolean"
+              },
+              "last_emailed_at_after": {
+                "default": null,
+                "nullable": true,
+                "title": "Last Emailed At After",
+                "type": "string"
+              },
+              "last_emailed_at_before": {
+                "default": null,
+                "nullable": true,
+                "title": "Last Emailed At Before",
+                "type": "string"
+              },
+              "latest_version_emailed_to_vendor": {
+                "default": null,
+                "nullable": true,
+                "title": "Latest Version Emailed To Vendor",
+                "type": "boolean"
+              },
+              "next_approver_user_uuids": {
+                "default": null,
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Next Approver User Uuids",
+                "type": "array"
+              },
+              "page_type": {
+                "description": "Represents the type of page where the PurchaseOrders are displayed.",
+                "enum": [
+                  "DEFAULT",
+                  "RECEIVING"
+                ],
+                "title": "PurchaseOrderPageType",
+                "type": "string",
+                "default": null,
+                "nullable": true
+              },
+              "payee": {
+                "properties": {
+                  "include_null": {
+                    "default": false,
+                    "title": "Include Null",
+                    "type": "boolean"
+                  },
+                  "payee_uuids": {
+                    "items": {
+                      "type": "string"
+                    },
+                    "title": "Payee Uuids",
+                    "type": "array"
+                  }
+                },
+                "title": "PurchaseOrderPayeeFilter",
+                "type": "object",
+                "default": null,
+                "nullable": true
+              },
+              "payee_uuids": {
+                "default": null,
+                "deprecated": true,
+                "description": "Deprecated: use payee.payee_uuids",
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Payee Uuids",
+                "type": "array"
+              },
+              "purchase_order_ids": {
+                "default": null,
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Purchase Order Ids",
+                "type": "array"
+              },
+              "purchase_order_statuses": {
+                "default": null,
+                "items": {
+                  "description": "Describes the status of a PurchaseOrder that we display to users\n\nA PO created in Ramp can have the following statuses:\n- OPEN\n- PARTIALLY_BILLED\n- FULLY_BILLED\n- CLOSED\n\nAn Imported PO can have the following statuses:\n- OPEN\n- FULLY_BILLED\n- CLOSED\n- DELETED",
+                  "enum": [
+                    "CLOSED",
+                    "DELETED",
+                    "FULLY_BILLED",
+                    "OPEN",
+                    "PARTIALLY_BILLED"
+                  ],
+                  "title": "PurchaseOrderStatusToDisplay",
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Purchase Order Statuses",
+                "type": "array"
+              },
+              "receipt_statuses": {
+                "default": null,
+                "items": {
+                  "description": "Represents the receipt status of the PO.\nA PO is considered to be `FULLY_RECEIVED` if and only if all of the PO line\nitems have been received.",
+                  "enum": [
+                    "FULLY_RECEIVED",
+                    "NOT_RECEIVED",
+                    "OVER_RECEIVED",
+                    "PARTIALLY_RECEIVED"
+                  ],
+                  "title": "PurchaseOrderReceiptStatus",
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Receipt Statuses",
+                "type": "array"
+              },
+              "requires_user_action": {
+                "default": null,
+                "nullable": true,
+                "title": "Requires User Action",
+                "type": "boolean"
+              },
+              "search": {
+                "title": "Search",
+                "type": "string"
+              },
+              "ship_to_address_ids": {
+                "default": null,
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Ship To Address Ids",
+                "type": "array"
+              },
+              "sources": {
+                "default": null,
+                "items": {
+                  "description": "Represents the creation source of a PurchaseOrder.\n\n- RAMP: PurchaseOrder created in Ramp\n- ACCOUNTING_PROVIDER: PurchaseOrder imported from an accounting provider\n- DEVELOPER_API: PurchaseOrder created via the Developer API",
+                  "enum": [
+                    "ACCOUNTING_PROVIDER",
+                    "DEVELOPER_API",
+                    "RAMP"
+                  ],
+                  "title": "PurchaseOrderCreationSource",
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Sources",
+                "type": "array"
+              },
+              "spend_end_date_after": {
+                "default": null,
+                "nullable": true,
+                "title": "Spend End Date After",
+                "type": "string"
+              },
+              "spend_end_date_before": {
+                "default": null,
+                "nullable": true,
+                "title": "Spend End Date Before",
+                "type": "string"
+              },
+              "spend_intent_uuids": {
+                "default": null,
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Spend Intent Uuids",
+                "type": "array"
+              },
+              "spend_request_owner_uuids": {
+                "default": null,
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Spend Request Owner Uuids",
+                "type": "array"
+              },
+              "spend_request_statuses": {
+                "items": {
+                  "enum": [
+                    "APPROVED",
+                    "DRAFT",
+                    "REJECTED",
+                    "SUBMITTED"
+                  ],
+                  "title": "SpendRequestStatus",
+                  "type": "string"
+                },
+                "title": "Spend Request Statuses",
+                "type": "array"
+              },
+              "spend_request_uuids": {
+                "default": null,
+                "items": {
+                  "type": "string"
+                },
+                "nullable": true,
+                "title": "Spend Request Uuids",
+                "type": "array"
+              },
+              "spend_start_date_after": {
+                "default": null,
+                "nullable": true,
+                "title": "Spend Start Date After",
+                "type": "string"
+              },
+              "spend_start_date_before": {
+                "default": null,
+                "nullable": true,
+                "title": "Spend Start Date Before",
+                "type": "string"
+              },
+              "tags": {
+                "items": {
+                  "properties": {
+                    "id": {
+                      "title": "Id",
+                      "type": "string"
+                    },
+                    "type": {
+                      "description": "This enum represents all possible categories of filters that can be applied to a\ntable search across all of Ramp.\n\nSubsets of these categories are used in different surfaces, such as transactions,\nreimbursements, bills, and reporting. The specific subsets used by each surface\nis declared below.\n\nThe values of these enums are persisted in the database as a part of saved table\nviews and reports, and thus they should never be renamed or deleted without migrating\nall saved table views and reports first, or ensuring that said enums are not\ncurrently being persisted in the database.\n\nSimilarly, each surface should not remove any supported categories without ensuring\nthat the categories are not currently being used in any saved table views or reports\nfor that surface.",
+                      "enum": [
+                        "absolute_approval_group",
+                        "accounting_status",
+                        "accrual_readiness",
+                        "affected_entity_owner",
+                        "ap_entity_type",
+                        "ap_events_currency",
+                        "approval_group",
+                        "approval_policy",
+                        "approval_status",
+                        "approver",
+                        "ar_customer",
+                        "assignee",
+                        "automatic_flag_severity",
+                        "bill",
+                        "bill_approval_status",
+                        "bill_paid_status",
+                        "bill_pay_vendor_owner",
+                        "bill_payment_status",
+                        "booked_by_name",
+                        "budget_column",
+                        "budget_non_ramp_entity",
+                        "business_vendor",
+                        "business_vendor_payee",
+                        "canonical_vendor",
+                        "card_type",
+                        "category",
+                        "compliance_flag",
+                        "department",
+                        "direct_team",
+                        "due_aging_bucket",
+                        "entity",
+                        "event_actor_type",
+                        "expense_group",
+                        "expense_policy_acting_user",
+                        "expense_type",
+                        "external_integration",
+                        "frontend_navigation",
+                        "future_approver",
+                        "healthcare_provider",
+                        "intake_spend_request_owner",
+                        "invoice_ocr",
+                        "invoice_submitter",
+                        "ironclad_workflow_schema",
+                        "limit_currency",
+                        "location",
+                        "manager",
+                        "merchant",
+                        "next_approver",
+                        "paid_in_currency",
+                        "paid_status",
+                        "payee",
+                        "payee_custom_field_string_value",
+                        "payee_custom_record_field_value",
+                        "payee_external_vendor_id",
+                        "payee_internal_vendor_id",
+                        "payee_name",
+                        "payee_owner",
+                        "payee_permissioned",
+                        "payee_request",
+                        "payment_run",
+                        "payment_type",
+                        "physical_card",
+                        "policy_assessment",
+                        "procurement_spend_request_currency",
+                        "procurement_spend_request_vendor",
+                        "program_currency",
+                        "provisional_bill",
+                        "purchase_order_currency",
+                        "purchase_order_spend_intent",
+                        "purchase_order_spend_request",
+                        "purchase_order_status",
+                        "receipt_availability",
+                        "receipt_verification_status",
+                        "received_aging_bucket",
+                        "reimbursement",
+                        "reimbursement_approval_status",
+                        "reimbursement_paid_status",
+                        "reimbursement_paid_status_v2",
+                        "reimbursement_policy_assessment_recommended_decision",
+                        "reimbursement_state",
+                        "reimbursement_status",
+                        "reimbursement_type",
+                        "relative_approval_group",
+                        "repayment_status",
+                        "reporting",
+                        "request_number",
+                        "review_prediction_agreement",
+                        "reviewer_action",
+                        "spend_allocation",
+                        "spend_intent",
+                        "spend_intent_custom_form_field",
+                        "spend_intent_custom_form_response",
+                        "spend_request",
+                        "spend_type",
+                        "statement",
+                        "statement_currency",
+                        "submission_policy",
+                        "submission_policy_requirements_status",
+                        "task_status",
+                        "task_type",
+                        "team",
+                        "tracking_category",
+                        "transaction",
+                        "transaction_approval_status",
+                        "transaction_charge_status",
+                        "transaction_paid_status",
+                        "transaction_policy_assessment_recommended_decision",
+                        "transaction_recommended_reviewer_action",
+                        "transaction_repayment_state",
+                        "travel_confirmation_number",
+                        "travel_location",
+                        "travel_merchant",
+                        "traveler_name",
+                        "trip",
+                        "trip_destination",
+                        "unified_request_coordinator",
+                        "unified_request_currency",
+                        "unified_request_owner",
+                        "user",
+                        "user_approved",
+                        "user_custom_field"
+                      ],
+                      "title": "SearchTagCategory",
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "id",
+                    "type"
+                  ],
+                  "title": "PurchaseOrderQueryV2Tag",
+                  "type": "object"
+                },
+                "title": "Tags",
+                "type": "array"
+              },
+              "three_way_match_enabled": {
+                "default": null,
+                "nullable": true,
+                "title": "Three Way Match Enabled",
+                "type": "boolean"
+              }
+            },
+            "title": "PurchaseOrderQueryV2Filters",
+            "type": "object"
+          },
+          "limit": {
+            "default": 10,
+            "description": "Maximum number of purchase orders to return (max 50)",
+            "maximum": 50,
+            "minimum": 1,
+            "title": "Limit",
+            "type": "integer"
+          },
+          "page_cursor": {
+            "default": null,
+            "description": "Pagination cursor from a previous response's next_page_cursor. The only valid string values are encrypted cursor tokens from a previous response (long strings starting with 'gAAAAA'). For the first page, for no more results, or for anything that is not one of those encrypted tokens, pass None (never the string 'None').",
+            "nullable": true,
+            "title": "Page Cursor",
+            "type": "string"
+          }
+        },
+        "title": "SearchPurchaseOrders"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "search-unified-requests",
+      "description": "Search for unified requests using free-text and structured request filters",
+      "inputSchema": {
+        "type": "object",
+        "properties": {
+          "limit": {
+            "type": "integer"
+          },
+          "page_cursor": {
+            "type": "string",
+            "nullable": true
+          }
+        }
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "search-user",
+      "description": "Search for users within the business by name",
+      "inputSchema": {
+        "type": "object",
+        "description": "Search for users within the business by name.\n\nUse this for attaching attendees to transactions. The search is case-insensitive and matches partial names. Results are ordered by relevance (recent attendees and teammates appear first). If no transaction id is provided, the latest transaction will be used for search.",
+        "properties": {
+          "search": {
+            "description": "Name or partial name to search for (e.g., 'john', 'smith', 'john smith')",
+            "title": "Search",
+            "type": "string"
+          },
+          "transaction_id": {
+            "description": "UUID of the transaction to use as context for the search. If not provided, uses the user's most recent transaction.",
+            "nullable": true,
+            "title": "Transaction Id",
+            "type": "string"
+          }
+        },
+        "required": [
+          "search",
+          "transaction_id"
+        ],
+        "title": "SearchUser"
+      },
+      "hidden": false,
+      "annotations": {
+        "readOnlyHint": true
+      }
+    },
+    {
+      "name": "submit-reimbursement",
+      "description": "Submit a draft out-of-pocket reimbursement for approval",
+      "inputSchema": {
+        "type": "object",
+        "description": "Submit a draft out-of-pocket reimbursement for approval.\n\nIf the submission fails, the agent should follow up with the user based on the error returned from the endpoint.\nIf it is due to outstanding missing items, the agent should recheck missing_items via the GetReimbursements tool and provide suggestions for the user.\nIf only nonsupported missing items are present (trip, attendee, mileage_locations), the agent should provide the reimbursement_link URL as a clickable link in the response.",
+        "properties": {
+          "reimbursement_uuid": {
+            "description": "UUID of the reimbursement to submit for approval. Call GetReimbursements to determine the UUID if it cannot be obtained from context.",
+            "nullable": true,
+            "title": "Reimbursement Uuid",
+            "type": "string"
+          }
+        },
+        "required": [
+          "reimbursement_uuid"
+        ],
+        "title": "SubmitReimbursement"
+      },
+      "hidden": false
+    },
+    {
+      "name": "upload-receipt-file",
+      "description": "Upload a receipt from base64-encoded file content",
+      "inputSchema": {
+        "type": "object",
+        "description": "Upload a receipt from base64-encoded file content.\n\nUse this tool to create a receipt from raw file data (PNG, JPEG, PDF, HEIC, WEBP).\nOptionally attach it to a transaction by providing a transaction UUID.\nThis tool is designed for external callers (CLI, MCP) that have the file content directly.",
+        "properties": {
+          "content_type": {
+            "description": "MIME type of the file, e.g. \"image/png\".",
+            "title": "Content Type",
+            "type": "string"
+          },
+          "file_content_base64": {
+            "description": "Base64-encoded file content (PNG, JPEG, PDF, HEIC, WEBP).",
+            "title": "File Content Base64",
+            "type": "string"
+          },
+          "filename": {
+            "description": "Original filename with extension, e.g. \"receipt.png\".",
+            "title": "Filename",
+            "type": "string"
+          },
+          "transaction_uuid": {
+            "default": null,
+            "description": "Optional UUID of a transaction to auto-attach the receipt to.",
+            "nullable": true,
+            "title": "Transaction Uuid",
+            "type": "string"
+          }
+        },
+        "required": [
+          "content_type",
+          "file_content_base64",
+          "filename"
+        ],
+        "title": "UploadReceiptFile"
+      },
+      "hidden": false
+    }
+  ]
+}