solve360_account
ChatGPTThis is a Solve360 CRM read only tool. Retrieve information about the currently logged in user and user defined name for records with type ID = 2 (blog/project blog). Always run this tool if user asks to do something with other than contacts, companies, blogs or tickets. The user defined name for blogs (record type ID = 2) is returned in "Blog Label". This tool returns details about your user account: - user ID - collaborator ID (either user ID or collaborator ID can be non-zero) - bloglabel: the name you MUST use instead of default "blog" or "project blog" name, email, - overridenzoneinfo: an IANA timezone string defining user's time zone - customfilters: array of user's custom filters to search for records CRITICAL: For other user info such as email and name you MUST use solve360_ownership tool. Never use the email used to log in to Claude! Great for questions like: - Who am I in solve360? - What is my user email? - Am I an admin? - Show me my user information - What user ID am I? - Am I a collaborator? Args: ctx: MCP context (auto-injected) IMPORTANT: - do NOT display any IDs to user unless they explicitly ask for them, even if they are included in the API response.
solve360_activities
ChatGPTThis is a Solve360 CRM read only tool. List activities matching many different criteria. DO NOT use this tool to load activities for a specific record, use solve360_batch tool instead. Useful for questions like: - Show me all activities created/updated in a date range - What tasks were completed last week? - Show me all calls from a specific user - List activities for a contact/company - What events are scheduled? - Show me all tasks assigned/created by a user - Show me all activities in companies tagged with tags VIP, Lead, etc. Args: ctx: MCP context (auto-injected) user_timezone: User's IANA timezone string (e.g. "America/Edmonton") start: Start date (YYYY-MM-DD) for the range. end: End date (YYYY-MM-DD) for the range. last: Which date field to filter by: "created" - activities created in the range "updated" - activities updated/modified in the range "changed" - either created or updated in the range "completed" - completed in the range Empty = all activities in range. types (CRITICAL: it MUST NOT BE EMPTY. Add all activity type IDs comma-separated to NOT filter by activity type): Comma-separated activity type IDs to filter. Options: 3=Note, 4=Event, 6=Follow-up, 14=Task, 23=File, 24=Photo, 32=Opportunity, 61=Event (non-linked), 73=Interaction/Call Log, 88=Scheduled Email. users: Comma-separated user IDs to filter by (creator|updater|completer). Empty = all users. categories: Comma-separated category IDs to filter activities' items by. CRITICAL: If it is not empty, itemtypes MUST be one of: 1, 2, or 40, to specify which items' categories to filter by. Empty = do not filter by categories. itemtypes: Comma-separated parent item type IDs: 1=contact, 2=company, 40=projectblog. Empty = all item types. CRITICAL: - user_timezone should be an IANA timezone string (e.g. "America/Edmonton") - if you don't know user's timezone you MUST run solve360_account tool to retrieve it. You must ask user for their timezone if the tool doesn't return it and pass it in the user_timezone parameter for correct date formatting IMPORTANT: - do NOT display any IDs to user unless they explicitly ask for them, even if they are included in the API response.
solve360_batch
ChatGPTExecute multiple Solve360 API requests in a single batch call to search for category tags and/or full data for records (contacts, blogs, companies, tickets) including record activities only. Use solve360_search to find record IDs if you don't have them. CRITICAL: Don't invent format of argument requests' entries, use schemas described below You MUST use this tool only to load full record data Use this tool when: - You need to perform multiple Solve360 operations, eg 2 or more of the following: fetching categories and/or records - You want to reduce API calls IMPORTANT RULES: - Use correct API paths (see examples below) - Use GET for fetching ARGUMENTS: - requests: list of dicts with 'method', 'endpoint', 'params' (optional) - user_timezone: User's IANA timezone string (e.g. "America/Edmonton") IMPORTANT: user_timezone is only required if any of the requests fetches a record, eg contacts/{CONTACT_ID} or tickets/{TICKET_ID} SUPPORTED REQUESTS (DO NOT use this tool for any other requests): - Fetch full data for a record including all its activities request entry scheme: { endpoint: "/contacts/{CONTACT_ID}", "/companies/{COMPANY_ID}", "/tickets/{TICKET_ID}", or "/projectblogs/{BLOG_ID}", method: "GET" } Gets full details of a single record (contact, company, project blog, or ticket) from Solve360 CRM. Returns all data for the specific record including: all fields, category tags, related items (linked contacts, companies, project blogs), and all activities (tasks, notes, deals, follow-ups, files, events, interactions, time records, etc.) with their hierarchical structure. Typical activity hierarchy in a record: - Task List → Task → File, Google Doc, Comment, Time Record - Deal → Comment - Follow-up → Comment - Note → Comment - Interaction → Comment, Time Record - Photo List → Photo, Comment - File → Comment - Website → Comment - Fetch categories request entry scheme: { endpoint: "/contacts/categories", "/companies/categories", "/tickets/categories", or "/projectblogs/categories", method: "GET" } Gets all available category tags for contacts in Solve360 CRM. Categories (also called tags) are labels used to classify contacts. Each contact can have multiple tags. This tool returns all available contact category tags with their IDs and names. EXAMPLES: Example 1: Get contact and company fields and categories { "requests": [ {"endpoint": "/contacts/12346358", "method": "GET"}, {"endpoint": "/companies/categories", "method": "GET"} ] }
solve360_calendar
ChatGPTThis is a Solve360 CRM read only tool. Retrieve calendar report from Solve360 CRM. Returns events, tasks and milestones within a date range. IMPORTANT: You MUST always display results as a visual calendar grid (rows = weeks, columns = Sun–Sat), with item titles placed inside their corresponding date cells. Do NOT use tables, lists, or any other format unless the user explicitly requests it. Show it in the chat, do NOT create any html files or attachments. Args: ctx: MCP context (auto-injected) user_timezone: User's IANA timezone string (e.g. "America/Edmonton") start: Start date (YYYY-MM-DD) for the range. end: End date (YYYY-MM-DD) for the range. filter: A comma-separated list of user IDs to filter by. It can include "0" (no attendees/unassigned to anybody) or just be equal to "0" if only entries with no attendees are required. The value can be empty to not filter by user. CRITICAL: Never use separate searches for each user, you MUST combine user IDs into argument "filter". CRITICAL: - user_timezone should be an IANA timezone string (e.g. "America/Edmonton") - if you don't know user's timezone you MUST run solve360_account tool to retrieve it. You must ask user for their timezone if the tool doesn't return it and pass it in the user_timezone parameter for correct date formatting IMPORTANT: - do NOT display any IDs to user unless they explicitly ask for them, even if they are included in the API response.
solve360_commit_activity
ChatGPTCommit an uploaded file or photo in Solve360 CRM. This is the final step of a file or photo upload: call it only after the file was successfully uploaded to the URL returned by solve360_create_activity. Args: ctx: MCP context (auto-injected) record_type_id: Type of parent record (contact=1, company=40, projectblog=2, ticket=50) activity_type: "file" or "photo", the same as passed to solve360_create_activity activity_id: ID of the file or photo activity returned by solve360_create_activity Returns: Success message, or error message.
solve360_create_activity
ChatGPTCreate a new activity (task, note, event, file, etc.) linked to a parent record or activity in Solve360 CRM. Activities represent different types of work items and communications linked to contacts, companies, project blogs, and tickets. Each activity type has specific fields. CRITICAL: you MUST run tool solve360_docs("activity") to load required instructions before using this tool. To attach a file (activity_type "file") or a photo (activity_type "photo") you MUST do these steps precisely for each file, any deviation from these steps will result in an error, NEVER start the next step until the previous one is completed successfully: 1. Check the file. A file must be a PDF. A photo must be a GIF, JPEG or PNG image and can be added to a Photo List only. If not, skip it and tell the user 2. Use this tool to create a new activity entry and a short-lived URL for the future file upload 3. After calling this tool send exactly one multipart/form-data POST request to URL from its response's data.action field Put the file in the file form field and include every field from the response'sdata.data[0]. If using curl use one --form-string per key in data.data[0], values copied exactly, in order (never -F for these), and the file line last: curl -sS -w '\nHTTP %{http_code}\n' '<data.action>' \ --form-string '<key>=<value>' \ -F 'file=@"<path>";type=<MIME type: application/pdf, image/gif, image/jpeg or image/png>' Files are limited to 20 Mb for a single file upload 4. HTTP 200 with an empty body means success. On any other status, show the error. 5. After a successful upload call solve360_commit_activity with the same record_type_id and activity_type, and activity_id set to id from this tool's response. The upload is not complete until this succeeds. Args: ctx: MCP context (auto-injected) parent_id: ID of the parent record or activity to attach this to record_type_id: Type of parent record (contact=1, company=40, projectblog=2, ticket=50) activity_type: Activity segment name data: Dict of activity-specific fields and values before: (Optional) Position this before the activity with this ID after: (Optional) Position this after the activity with this ID Returns: JSON object with the action URL and data for file upload/success message with the new activity ID for other activities, or error message.
solve360_create_record
ChatGPTCreate a new record (contact, company, project blog, or ticket) in Solve360 CRM. CRITICAL: you MUST run tool solve360_docs("record") to load CRITICAL instructions before using this tool. It is STRICTLY PROHIBITED to proceed without loading them. CRTITICAL: if argument "ownership" is not set you MUST ask user to confirm that they want to create a private record. VIOLATION is STRICTLY PROHIBITED. CRITICAL: when creating a record you MUST provide all values for the record in a single call to this tool. Calling solve360_update_record tool right after it to set some values separately is STRICTLY PROHIBITED. Args: ctx: MCP context (auto-injected) record_type_id: Type of record to create (contact=1, company=40, projectblog=2, ticket=50) fields: Optional dictionary of field names and values to set on the new record CRITICAL: fields named "company" and "relatedto" MUST NEVER be set in "fields" dictionary. VIOLATION is STRICTLY PROHIBITED. ownership: Optional user/group ID to own the record (defaults to current user) Defines who has access to the record. When set to a group ID, all members of that group can read and edit it — this is the standard pattern for team-shared records. When set to a user ID, only that user (and admins) can see the record. categories: Optional list of category tag IDs to assign to the record related_items: Optional list of records as dicts with 'id' and 'note' fields to make related CRITICAL: tickets are NOT allowed as related items Violation of this rule is STRICTLY PROHIBITED. primaryRelation: TICKETS ONLY Optional contact ID the ticket is to be created for
solve360_deals
ChatGPTThis is a Solve360 CRM read only tool. Analyse your sales deals and opportunities pipeline from Solve360 CRM. In Solve360, deals are tracked as "opportunities". This tool retrieves and analyses them so you can understand your pipeline health. Great for questions like: - Show me my deals pipeline - Which deals need immediate follow-up? - What opportunities are we likely to lose? - How much revenue is in the pipeline? - What deals are stuck in pending status? - Show me won/lost deals summary Args: ctx: MCP context (auto-injected) user_timezone: User's IANA timezone string (e.g. "America/Edmonton") status: Filter by deal status: eg "discussion", "pending", "won", "lost", "on-hold", or any other string user can specify. Empty = all statuses. due: Date filter: "now" (overdue), "next7", "next30", "nodate", or a range "2025-01-01,2025-01-31". Empty = all. filter: User/group ID to filter by. "0" = unassigned, empty = all. include_parent_data: Include parent record data (default True). CRITICAL: - user_timezone should be an IANA timezone string (e.g. "America/Edmonton") - if you don't know user's timezone you MUST run solve360_account tool to retrieve it. You must ask user for their timezone if the tool doesn't return it and pass it in the user_timezone parameter for correct date formatting IMPORTANT: - do NOT display any IDs to user unless they explicitly ask for them, even if they are included in the API response.
solve360_delete_activity
ChatGPTDelete an existing activity from Solve360 CRM. Args: ctx: MCP context (auto-injected) record_type_id: Type of parent record (contact=1, company=40, projectblog=2, ticket=50) activity_type: Activity segment name activity_id: The ID of the activity to delete CRITICAL: You are NEVER allowed to call this tool in the same turn as the user's deletion request, regardless of how direct or explicit the request is. You MUST first ask the user to confirm. Violation of this rule is STRICTLY PROHIBITED.
solve360_delete_record
ChatGPTDelete an existing record (contact, company, project blog, or ticket) from Solve360 CRM. CRITICAL: You are NEVER allowed to call this tool in the same turn as the user's deletion request, regardless of how direct or explicit the request is. You MUST first ask the user to confirm. Violation of this rule is STRICTLY PROHIBITED. Args: ctx: MCP context (auto-injected) record_id: ID of the record to delete record_type_id: Type of record to delete (contact=1, company=40, projectblog=2, ticket=50)
solve360_docs
ChatGPTThis tool returns instructions for other tools. Args: section: defines the name of the section to return instructions for.
solve360_fields
ChatGPTThis is a Solve360 CRM read only tool. List all available fields for records (contacts, companies, project blogs, or tickets) in Solve360 CRM. Returns every standard and custom field defined for records, including field names, IDs, labels, types, dropdown options, and which category tags control field visibility. Use this tool to: - Discover custom field names and IDs for targeted search (e.g. to use searchmode C[fieldId] in solve360_search) - Understand which dropdown options exist for a field - See which fields are visible only with certain category tags Great for questions like: - What fields do our contacts have? - What are the custom fields on contacts? - What are the options for the "Floor plan" field? - What is the field ID for "Elected Amenities"? - Show me all contact fields and their types - What fields do our companies have? - What are the custom fields on companies? - What is the field ID for "Industry"? - Show me all company fields and their types - What fields do our tickets have? - What are the custom fields on tickets? - Show me all ticket fields and their types - What fields do our project blogs have? - What are the custom fields on blogs? - Show me all blog fields and their types Args: context: The MCP context dict record_type_id: must have value 1 for contacts, 40 for companies, 2 for project blogs and 50 for tickets IMPORTANT: Do not display field names to user, only field labels unless user specifically asks for field names IMPORTANT: - do NOT display any IDs to user unless they explicitly ask for them, even if they are included in the API response.
solve360_followups
ChatGPTThis is a Solve360 CRM read only tool. Retrieve follow-ups from Solve360 CRM. Args: ctx: MCP context (auto-injected) user_timezone: User's IANA timezone string (e.g. "America/Edmonton") responsible: Used to filter by who is responsible for follow-ups. Possible values: - Comma-separated list of user/group IDS to retrieve follow-ups with these users/groups set as responsible. - Empty string ("") to not filter by responsible (anyone can be responsible). - 0 to find follow-ups with no responsible assigned. due: Date range filter Possible values: - "now" - follow-ups queued up to now - "next7" - queued up to next 7 days from now - "next30" - queued up to next 30 days from now - "nodate" - follow-ups with no date set - date range in format "YYYY-MM-DD,YYYY-MM-DD" - Empty string ("") to not filter by date (any date is fine). CRITICAL: - user_timezone should be an IANA timezone string (e.g. "America/Edmonton") - if you don't know user's timezone you MUST run solve360_account tool to retrieve it. You must ask user for their timezone if the tool doesn't return it and pass it in the user_timezone parameter for correct date formatting IMPORTANT: - do NOT display any IDs to user unless they explicitly ask for them, even if they are included in the API response.
solve360_next_actions
ChatGPTThis is a Solve360 CRM read only tool. Retrieve and analyse next actions from Solve360 CRM. Returns tasks, events, and milestones that need attention. Great for questions like: - What should I focus on today? - Which deals need immediate follow-up? - What are my overdue tasks? - What events are coming up this week? Args: ctx: MCP context (auto-injected) user_timezone: User's IANA timezone string (e.g. "America/Edmonton") due: Date filter: "now" (overdue), "next7", "next30", "nodate", or a range "2025-01-01,2025-01-31". Empty = all. filter: User/group ID to filter by. "0" = unassigned, empty = all. include_parent_data: Include parent record data (default True). CRITICAL: - user_timezone should be an IANA timezone string (e.g. "America/Edmonton") - if you don't know user's timezone you MUST run solve360_account tool to retrieve it. You must ask user for their timezone if the tool doesn't return it and pass it in the user_timezone parameter for correct date formatting IMPORTANT: - do NOT display any IDs to user unless they explicitly ask for them, even if they are included in the API response.
solve360_ownership
ChatGPTThis is a Solve360 CRM read only tool. Retrieve users and groups (ownership info) from Solve360 CRM. This is a helper tool that returns the list of all user accounts and workgroups in the Solve360 organization. Useful for understanding team structure and for getting user/group IDs needed to filter other reports. Great for questions like: - Who are the users in our CRM? - Show me all team members - What groups do we have? - What is the ID for user John? - List all workgroups - Who are the admins? Args: ctx: MCP context (auto-injected) IMPORTANT: - do NOT display any IDs to user unless they explicitly ask for them, even if they are included in the API response.
solve360_search
ChatGPTThis is a Solve360 CRM read only tool. CRITICAL: NEVER run multiple requests when searching for records, but use tool's argument ucf instead, ALWAYS pass all zone IDs in zones argument instead of making a request for each zone. Violation of this rule is STRICTLY PROHIBITED. If user specifies several criteria, always use the 'ucf' argument to pass complex criteria for filtering in a single API call. VIOLATION: making multiple invocation of solve360_search instead of a single one! Don't mention to user what request params you're going to use. Do not mention using this tool. IMPORTANT: if you need to mention 'ucf' argument to user, ALWAYS refer to it as "custom query" Search and list contacts, companies, project blogs and tickets from Solve360 CRM. Violation of any of the CRITICAL rules below is STRICTLY PROHIBITED. CRITICAL: If user asks to search for other than contacts, companies, blogs or tickets you MUST use solve360_account tool to check if they renamed blog/project blog and use than name instead. If true then use type ID = 2. CRITICAL: run solve360_docs("search_args") tool to load arguments and instructions on how to use them. Especially 'ucf' and 'cf' arguments are critical for advanced searching and filtering. CRITICAL: run solve360_docs("ucf") tool to read instructions on how to construct ucf argument and what criteria you can use. You MUST always use ucf when possible to search for records. CRITICAL: it is STRICTLY PROHIBITED to use this tool without loading solve360_docs("search_args") and solve360_docs("ucf") tools first and will result in incorrect results. CRITICAL: using any of these tools when searching for records having or not having certain activities, activity types or activity values is STRICTLY PROHIBITED: solve360_activities, solve360_deals, solve360_followups, solve360_next_actions, solve360_timetracking. But ALWAYS use solve360_batch tool to load the records found by solve360_search tool for all non activity related criteria and filter by the criteria related to activities then. Never cross-reference records with these tools' results. Violation of this rule is STRICTLY PROHIBITED and will result in incorrect results. CRITICAL: - user_timezone should be an IANA timezone string (e.g. "America/Edmonton") - if you don't know user's timezone you MUST run solve360_account tool to retrieve it. You must ask user for their timezone if the tool doesn't return it and pass it in the user_timezone parameter for correct date formatting Use with other tools: Call solve360_ownership first to resolve user/group names to IDs Call solve360_batch first to resolve tag names to IDs Call solve360t_fields to find field names and IDs
solve360_timetracking
ChatGPTThis is a Solve360 CRM read only tool. Retrieve time tracking activities matching a specific date range and status from Solve360 CRM. Useful for questions like: - Show me time records for a date range - How many billable hours were logged last month? - What time did I log this week? - Which time records are invoiced or non-billable? Args: ctx: MCP context (auto-injected) start: Start date (YYYY-MM-DD) for the time range. end: End date (YYYY-MM-DD) for the time range. filter: Defines how to filter records: "invoiced" - returned time tracking activities which are billable and invoiced only (use this value even if user asks for invoiced time records and doesn't mention billable), "billable" - billable only and nont marked as invoiced, "non-billable" - non billable only "" - return all time tracking activities. itemtypes: item type id (1=contact, 2=company, or 40=project blog). IMPORTANT: Show total times recorded and a breakdown of billable vs non-billable hours IMPORTANT: - do NOT display any IDs to user unless they explicitly ask for them, even if they are included in the API response.
solve360_update_activity
ChatGPTUpdate an existing activity in Solve360 CRM. CRITICAL: you MUST run tool solve360_docs("activity") to load required instructions before using this tool. Args: ctx: MCP context (auto-injected) record_type_id: Type of parent record (contact=1, company=40, projectblog=2, ticket=50) activity_type: Activity segment name activity_id: The ID of the activity to update data: Dict of activity-specific fields and values parent_id: (Optional) ID of the parent record or activity to move this to before: (Optional) Position this before the activity with this ID after: (Optional) Position this after the activity with this ID Returns: Success message with the new activity ID, or error message.
solve360_update_record
ChatGPTUpdate an existing record (contact, company, project blog, or ticket) in Solve360 CRM. CRITICAL: It is STRICTLY PROHIBITED to make multiple calls of this tool for the same record, you MUST pass all updates for the record in a single call. CRITICAL: you MUST run tool solve360_docs("record") to load CRITICAL instructions before using this tool. It is STRICTLY PROHIBITED to proceed without loading them. Args: ctx: MCP context (auto-injected) record_id: ID of the record to update record_type_id: Type of record to create (contact=1, company=40, projectblog=2, ticket=50) fields: Optional dictionary of field names and values to set on the new record ownership: Optional user/group ID to own the record (must be ID of the currently logged-in user to make the record private) categories_to_add: Optional list of category tag IDs to assign to the record categories_to_remove: Optional list of category tag IDs to remove from the record related_items_to_add: Optional list of related records as dicts with 'id' and 'note' fields CRITICAL: tickets are NOT allowed as related items Violation of this rule is STRICTLY PROHIBITED. related_items_to_remove: Optional list of related records as IDs to remove relationship
solve360_zones
ChatGPTThis is a Solve360 CRM read only tool. Retrieve zones from Solve360 CRM. User can define spatial zones in Solve360 and this tool allows you to retrieve them. Each zone has an ID, name, and coordinates defining its boundaries. You can use zones to search for records located within specific zones. Args: ctx: MCP context (auto-injected) IMPORTANT: - do NOT display any IDs to user unless they explicitly ask for them, even if they are included in the API response.