cor_add_task_attachment
ChatGPTAdd an attachment to a COR task from an external source (Google Drive, Dropbox, or OneDrive). Uses COR's dedicated attachment API.
cor_assign_task_collaborators
ChatGPTAssign collaborators to a COR task. IMPORTANT: This is a sync/replace operation — the array you provide becomes the complete new list. Any collaborator currently assigned but not in the array will be REMOVED. To add a collaborator without removing existing ones, first call cor_get_task_collaborators to get the current list, then include those IDs plus the new one in collaborator_ids. Pass an empty array [] to remove all collaborators.
cor_assign_task_label
ChatGPTAssign or unassign a label/tag on a COR task. Use cor_list_available_labels to find label IDs, and cor_get_task_labels to see current labels before making changes.
cor_create_project
ChatGPTCreate a new project in COR. Requires name and client_id. Optionally set brief, start/end dates, PM, estimated time, billable flag, status, and more.
cor_create_task
ChatGPTCreate a new task in COR. Requires title and project_id. Optionally set description, start date (datetime), deadline, priority (0=Low,1=Medium,2=High,3=Urgent), status, estimated hours, subtask hierarchy (task_root/task_father), and deliverable settings.
cor_delete_task_message
ChatGPTDelete one task message. The message_id is the (ID: N) value from cor_get_task_messages. COR does not check authorship. Anyone who can see the message and has messages.delete can delete it. The message stops appearing in cor_get_task_messages. Any files attached to the message are permanently removed. There is no confirmation step.
cor_get_client
ChatGPTGet full details of a single COR client by ID. Use this when the user asks about a specific client, wants to see client details, or references a client by number/ID. Returns contact info, business name, website, and description.
cor_get_hours_report
ChatGPTReporte de horas. The only tool for reading logged hours in COR. Use it for reporte de horas, horas cargadas, horas trabajadas, time logs, time entries, and hours by project, client, or user. date_start and date_end are required (YYYY-MM-DD). Maximum 3 months per call. If the asked range is longer, split it into consecutive calls and add the totals. Resolve a project or client name to an id with the list tools, then pass project_id or client_id. Omit user_id for the whole workspace.
cor_get_me
ChatGPTGet the authenticated user's profile from COR, including name, email, role, position, daily hours, plan info, and company/organization details (name, subdomain).
cor_get_my_pending_tasks
ChatGPTGet MY pending tasks — the default tool when the user asks for 'my tasks', 'mis tareas', 'tareas pendientes', or 'tareas asignadas a mí'. Returns active (non-archived), non-finished tasks for the authenticated user. By default returns only tasks where the user is a collaborator (directly assigned). Supports the same filters as cor_list_tasks (project, client, search, dates) to narrow results, e.g. 'my tasks in project X' or 'my tasks with [BUG] in the title'. The ui_locale parameter is REQUIRED on every call and must always reflect the language of the user's latest message — never reuse the prior call's value and never infer it from the language of the returned task titles.
cor_get_project
ChatGPTGet full details of a single COR project by ID. Use this when the user asks about a specific project, wants to see project details, health, budget, or references a project by number/ID. Returns comprehensive information including client, PM, dates, hours, profitability, and billing info.
cor_get_task
ChatGPTGet full details of a single COR task by ID. Use this when the user asks about a specific task, wants to see task details, or references a task by number/ID. Returns comprehensive information including description, dates, collaborators, project info, and subtask hierarchy.
cor_get_task_collaborators
ChatGPTGet the current list of collaborators assigned to a COR task. Use this before calling cor_assign_task_collaborators if you want to add or remove individual collaborators without affecting the rest.
cor_get_task_labels
ChatGPTGet the labels/tags currently assigned to a COR task. Use this to see which labels a task has before adding or removing labels.
cor_get_task_messages
ChatGPTList the messages (comments) on a COR task. Use this to understand the task conversation before replying with cor_post_task_message. Returns the most recent messages as plain text (author, timestamp, reply quote, and attachment names). Deleted messages are omitted. Default order is chronological: oldest message of the selected window first.
cor_get_time_logs
ChatGPTSearch time entries (logged hours) across COR with filters by user, project, client, date range, and approval status. Returns a list of time entries with totals.
cor_get_url
ChatGPTGenerate a direct URL to a COR entity (task, project, or client). Use this when the user wants a link to open in the browser, or when you need to provide a clickable reference to a COR entity.
cor_get_user
ChatGPTGet full details of a single COR user by ID. Use this instead of cor_list_users when you already know the user ID — it's a direct lookup and avoids paginating the full user list. Returns name, email, role, position, daily hours, remaining hours, plan, and labels.
cor_get_user_leaves
ChatGPTThis is the tool for vacations and other leave in a date range, including leave that already ended. It is not the current-leave flag on the user list. user_id is optional. start and end are required YYYY-MM-DD dates. The leave type name comes from the company catalog, so a vacation is whatever name that company stored.
cor_list_available_labels
ChatGPTList all available label categories and their labels in the COR organization. Supports models: task (default), user, project. Use this to discover label IDs before assigning them.
cor_list_clients
ChatGPTList clients from COR. Returns a paginated list of clients with their IDs and names.
cor_list_projects
ChatGPTList projects from COR with optional filtering by name, client, PM, status, health, work order, archived state, and date range. Returns a paginated list.
cor_list_task_attachments
ChatGPTList attachments for a COR task. Returns a paginated list with file details.
cor_list_tasks
ChatGPTSearch tasks across the entire COR organization with powerful filtering: by project, client, status, text search (title substring), date ranges, and archived state. Use cor_get_my_pending_tasks instead when the user asks for their own tasks. This tool does NOT filter by the current user by default.
cor_list_users
ChatGPTList users in the COR account with optional filtering. Returns a paginated list including name, email, role, and position.
cor_log_time
ChatGPTLog worked hours on a COR task. Creates a time entry for the given task, date, and duration. If user_id is omitted, hours are logged for the authenticated user. The ui_locale parameter is REQUIRED on every call and must always reflect the language of the user's latest message — never reuse the prior call's value and never infer it from the language of the returned task data.
cor_post_task_message
ChatGPTPost a message/comment on a COR task. Supports @mentions — provide a mentions array with user details and use @Name in the message text.
cor_update_project
ChatGPTUpdate an existing project in COR. Only provided fields will be changed. Supports name, brief, start/end dates, PM, status, estimated time, billable, and archived.
cor_update_task
ChatGPTUpdate an existing task in COR. Only provided fields will be changed. Supports title, description, start date (datetime), deadline, status, priority, archived, estimated hours, subtask hierarchy (task_root/task_father), and deliverable settings.
cor_update_task_message
ChatGPTReplace the entire text of one task message. The message_id is the (ID: N) value from cor_get_task_messages. COR does not check authorship. Anyone who can see the message and has messages.edit can replace it. Your text is stored as a single paragraph, using the same mention markup as cor_post_task_message, so bold, lists, and existing line breaks are dropped. To notify people, pass mentions and include @Name in the text for each name. COR notifies again only when that mention id list changes. Omitting mentions leaves stored mentions in place and notifies nobody. This does not bookmark the message and does not change its files. An empty text is refused and is not sent to COR. The read tool shows mentions as plain @Name. If you copy that text and do not pass those people in mentions again, the stored message keeps the words but the mention markup is removed and those people are not notified.
create_knowledge_patch
Claudecreate_tutorial_draft
Claudeget_authoring_guidance
Claudeget_knowledge_patch
Claudeget_session_transcript
Claudeget_tutorial
Claudeget_use_cases
Claudelist_findings
Claudelist_knowledge_patches
Claudelist_sessions
Claudelist_tutorials
Claudesearch_knowledge
Claudeupdate_knowledge_patch
Claudeupdate_tutorial_draft
Claude