Split (1)

train · 1.89k rows

server_name stringclasses 156 values	category stringclasses 1 value	tool stringlengths 176 38.2k
task-orchestrator	other	{'type': 'function', 'name': 'get_feature', 'description': 'Retrieves a feature by its ID with options for including relationships.\n \n ## Purpose\n\n Fetches a complete feature by its UUID with options to include related entities like \n tasks and task statistics. This tool allows getting detailed information about a specific \n feature when its ID is known.\n \n Note: Features store their detailed content in separate Section entities for efficiency. \n To retrieve the complete feature with all content blocks, make sure to set includeSections=true.\n Otherwise, you\'ll only receive the basic feature metadata and summary.\n \n ## Parameters\n \n \| Parameter \| Type \| Required \| Default \| Description \|\n \| id \| UUID string \| Yes \| - \| The unique ID of the feature to retrieve (e.g., \'550e8400-e29b-41d4-a716-446655440000\') \|\n \| includeTasks \| boolean \| No \| false \| Whether to include basic task information in the response. Set to true when you need to see all tasks associated with this feature. \|\n \| maxTaskCount \| integer \| No \| 10 \| Maximum number of tasks to include (1-100) \|\n \| includeTaskCounts \| boolean \| No \| false \| Whether to include task statistics grouped by status \|\n \| includeTaskDependencies \| boolean \| No \| false \| Whether to include dependency information for tasks when includeTasks is true \|\n \| includeSections \| boolean \| No \| false \| Whether to include sections (detailed content blocks) that contain the full content of the feature. Set to true when you need the complete feature context beyond the basic summary. \|\n \| summaryView \| boolean \| No \| false \| Whether to return a summarized view for context efficiency (truncates text fields) \|\n \| maxsummaryLength \| integer \| No \| 500 \| Maximum length for summary before truncation when in summary view \|\n \n ## Response Format\n \n ### Success Response\n \n ```json\n {\n "success": true,\n "message": "Feature retrieved successfully",\n "data": {\n "id": "661e8511-f30c-41d4-a716-557788990000",\n "name": "REST API Implementation",\n "summary": "Implement the core REST API endpoints...",\n "status": "in-development",\n "priority": "high",\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T15:45:00Z",\n "tags": ["api", "backend"],\n "taskCounts": {\n "total": 15,\n "byStatus": {\n "pending": 5,\n "in-progress": 8,\n "completed": 2\n }\n },\n "sections": [\n {\n "id": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Requirements",\n "content": "The API should support CRUD operations...",\n "contentFormat": "markdown",\n "ordinal": 0\n }\n ],\n "tasks": {\n "items": [\n {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Implement User API",\n "status": "in-progress",\n "priority": "high",\n "complexity": 7,\n "dependencies": {\n "counts": {\n "total": 3,\n "incoming": 1,\n "outgoing": 2\n }\n }\n },\n // More tasks...\n ],\n "total": 15,\n "included": 10,\n "hasMore": true,\n "dependencyStatistics": {\n "totalDependencies": 25,\n "totalIncomingDependencies": 12,\n "totalOutgoingDependencies": 13,\n "tasksWithDependencies": 8\n }\n }\n }\n }\n ```\n \n ## Error Responses\n \n - RESOURCE_NOT_FOUND (404): When no feature exists with the specified ID\n - VALIDATION_ERROR (400): When the provided ID is not a valid UUID\n - DATABASE_ERROR (500): When there\'s an issue retrieving data from the database\n - INTERNAL_ERROR (500): For unexpected system errors during execution\n \n ## Usage Examples\n \n 1. Get basic feature information:\n ```json\n {\n "id": "661e8511-f30c-41d4-a716-557788990000"\n }\n ```\n \n 2. Get feature with tasks and counts:\n ```json\n {\n "id": "661e8511-f30c-41d4-a716-557788990000",\n "includeTasks": true,\n "includeTaskCounts": true\n }\n ```\n \n 3. Get feature with sections (detailed content):\n ```json\n {\n "id": "661e8511-f30c-41d4-a716-557788990000",\n "includeSections": true\n }\n ```\n \n 4. Get complete feature with all relationships:\n ```json\n {\n "id": "661e8511-f30c-41d4-a716-557788990000",\n "includeTasks": true,\n "includeTaskCounts": true,\n "includeSections": true\n }\n ```\n \n 5. Get feature with tasks and their dependency information:\n ```json\n {\n "id": "661e8511-f30c-41d4-a716-557788990000",\n "includeTasks": true,\n "includeTaskDependencies": true\n }\n ```\n \n 6. Get summarized feature information (for context efficiency):\n ```json\n {\n "id": "661e8511-f30c-41d4-a716-557788990000",\n "summaryView": true\n }\n ```', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID of the feature to retrieve'}, 'includeSections': {'type': 'boolean', 'description': 'Whether to include sections (detailed content blocks) that contain the full content of the feature.', 'default': False}, 'includeTaskCounts': {'type': 'boolean', 'description': 'Whether to include task statistics grouped by status. Useful for getting a quick overview of task progress.', 'default': False}, 'includeTaskDependencies': {'type': 'boolean', 'description': 'Whether to include dependency information for tasks when includeTasks is true', 'default': False}, 'includeTasks': {'type': 'boolean', 'description': 'Whether to include basic task information in the response. Set to true when you need to see all tasks associated with this feature.', 'default': False}, 'maxTaskCount': {'type': 'integer', 'description': 'Maximum number of tasks to include', 'default': 10}, 'maxsummaryLength': {'type': 'integer', 'description': 'Maximum length for summary (truncates if longer)', 'default': 500}, 'summaryView': {'type': 'boolean', 'description': 'Whether to return a summarized view for context efficiency', 'default': False}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'get_overview', 'description': 'Retrieves a lightweight, token-efficient overview of tasks and features.\n \n ## Purpose\n This tool provides a hierarchical project overview optimized for context efficiency.\n Essential for understanding current work state and making informed task planning decisions.\n \n ## Usage Guidance\n RECOMMENDED WORKFLOW START: Always begin work sessions with get_overview to:\n - Understand current project state and priorities\n - Identify in-progress tasks that need attention\n - Plan new work based on existing features and tasks\n - Locate orphaned tasks that might need feature association\n \n ## Data Organization\n - Features: Top-level functionality groupings with their associated tasks\n - Orphaned Tasks: Tasks not associated with any feature (may need organization)\n - Hierarchical View: Tasks organized under their parent features for clear context\n - Essential Metadata: Status, priority, complexity without full content for efficiency\n \n ## Context Efficiency Features\n - Configurable summary length (0-200 chars) to control token usage\n - Essential metadata only (no full task content or sections)\n - Hierarchical organization reduces cognitive overhead\n - Count summaries provide quick project metrics\n \n ## Integration with Other Tools\n Use this overview to inform decisions for:\n - `create_task`: Understand existing work before creating new tasks\n - `create_feature`: Identify orphaned tasks that could be grouped\n - `update_task`: Find tasks that need status updates\n - `search_tasks`: Narrow down specific searches based on overview insights\n \n ## Best Practices\n - Run get_overview at the start of work sessions\n - Use summaryLength=0 when you only need structure and metadata\n - Use summaryLength=100-200 when you need content context\n - Pay attention to orphaned tasks - they may need feature association\n - Monitor task status distribution across features\n \n Example response:\n {\n "success": true,\n "message": "Task overview retrieved successfully",\n "data": {\n "features": [\n {\n "id": "661e8511-f30c-41d4-a716-557788990000",\n "name": "User Authentication",\n "status": "in-development",\n "summary": "Implements secure user authentication mechanisms with OAuth 2.0 and JWT tokens...",\n "tasks": [\n {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Implement OAuth Authentication API",\n "summary": "Create secure authentication flow with OAuth 2.0 protocol and JWT token management...",\n "status": "in-progress",\n "priority": "high",\n "complexity": 8,\n "tags": "task-type-feature, oauth, authentication, api"\n }\n ]\n }\n ],\n "orphanedTasks": [\n {\n "id": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Setup CI/CD Pipeline",\n "summary": "Configure automated build and deployment pipeline using GitHub Actions...",\n "status": "pending",\n "priority": "medium",\n "complexity": 6,\n "tags": "task-type-infrastructure, ci-cd, automation"\n }\n ],\n "counts": {\n "features": 5,\n "tasks": 23,\n "orphanedTasks": 7\n }\n }\n }', 'parameters': {'type': 'object', 'properties': {'summaryLength': {'type': 'integer', 'description': 'Maximum length of task/feature summaries (0 to exclude summaries)', 'default': 100, 'minimum': 0, 'maximum': 200}}, 'required': [], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'get_project', 'description': 'Retrieves a project by its ID with options for including relationships.\n\n This tool provides detailed access to a specific project with options to include related entities like \n features, tasks, and sections. Projects are top-level organizational containers that group related work together.\n\n The tool supports progressive loading of details to optimize context usage, allowing you to request only the \n information you need. For large projects, you can limit the number of related entities returned.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID (UUID) of the project to retrieve'}, 'includeFeatures': {'type': 'boolean', 'description': 'Whether to include basic feature information in the response', 'default': False}, 'includeSections': {'type': 'boolean', 'description': 'Whether to include sections (detailed content blocks) in the response', 'default': False}, 'includeTasks': {'type': 'boolean', 'description': 'Whether to include basic task information in the response', 'default': False}, 'maxFeatureCount': {'type': 'integer', 'description': 'Maximum number of features to include (1-100)', 'default': 10}, 'maxTaskCount': {'type': 'integer', 'description': 'Maximum number of tasks to include (1-100)', 'default': 10}, 'summaryView': {'type': 'boolean', 'description': 'Whether to return a summarized view for context efficiency', 'default': False}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'get_sections', 'description': 'Retrieves sections for a task, feature, or project.\n \n ## Purpose\n \n Sections contain detailed content for tasks, features, and projects in a structured format.\n Each section has a specific purpose, content format, and ordering position. This tool\n allows retrieving all sections for a specified entity.\n \n ## Parameters\n \n \| Parameter \| Type \| Required \| Default \| Description \|\n \|-----------\|------\|----------\|---------\|-------------\|\n \| entityType \| string \| Yes \| - \| Type of entity to retrieve sections for: \'PROJECT\', \'TASK\', or \'FEATURE\' \|\n \| entityId \| UUID string \| Yes \| - \| ID of the entity to retrieve sections for (e.g., \'550e8400-e29b-41d4-a716-446655440000\') \|\n \n ## Response Format\n \n ### Success Response\n \n ```json\n {\n "success": true,\n "message": "Sections retrieved successfully",\n "data": {\n "sections": [\n {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Requirements",\n "usageDescription": "Key requirements for this task",\n "content": "1. Must support OAuth2\\\\n2. Handle token refresh\\\\n3. Implement rate limiting",\n "contentFormat": "MARKDOWN",\n "ordinal": 0,\n "tags": ["requirements", "security"],\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T14:30:00Z"\n },\n {\n "id": "661f9511-f30c-52e5-b827-557766551111",\n "title": "Implementation Notes",\n "usageDescription": "Technical details and implementation guidance",\n "content": "Use the AuthLib 2.0 library for OAuth implementation...",\n "contentFormat": "MARKDOWN",\n "ordinal": 1,\n "tags": ["implementation", "technical"],\n "createdAt": "2025-05-10T14:35:00Z",\n "modifiedAt": "2025-05-10T15:20:00Z"\n }\n ],\n "entityType": "TASK",\n "entityId": "772f9622-g41d-52e5-b827-668899101111",\n "count": 2\n }\n }\n ```\n \n ### Empty Result Response\n \n ```json\n {\n "success": true,\n "message": "No sections found for task",\n "data": {\n "sections": [],\n "entityType": "TASK",\n "entityId": "772f9622-g41d-52e5-b827-668899101111",\n "count": 0\n }\n }\n ```\n \n ## Error Responses\n \n - RESOURCE_NOT_FOUND (404): When the specified task or feature doesn\'t exist\n ```json\n {\n "success": false,\n "message": "The specified task was not found",\n "error": {\n "code": "RESOURCE_NOT_FOUND"\n }\n }\n ```\n \n - VALIDATION_ERROR (400): When parameters fail validation\n ```json\n {\n "success": false,\n "message": "Invalid entity type: INVALID. Must be one of: TASK, FEATURE",\n "error": {\n "code": "VALIDATION_ERROR"\n }\n }\n ```\n \n - DATABASE_ERROR (500): When there\'s an issue retrieving sections from the database\n \n - INTERNAL_ERROR (500): For unexpected system errors during execution\n \n ## Usage Examples\n \n 1. Get sections for a task:\n ```json\n {\n "entityType": "TASK",\n "entityId": "550e8400-e29b-41d4-a716-446655440000"\n }\n ```\n \n 2. Get sections for a feature:\n ```json\n {\n "entityType": "FEATURE",\n "entityId": "661e8511-f30c-41d4-a716-557788990000"\n }\n ```\n \n 3. Get sections for a project:\n ```json\n {\n "entityType": "PROJECT",\n "entityId": "772f9622-g41d-52e5-b827-668899101111"\n }\n ```\n \n ## Content Formats\n \n Sections support multiple content formats:\n - MARKDOWN: Formatted text with Markdown syntax (default)\n - PLAIN_TEXT: Unformatted plain text\n - JSON: Structured data in JSON format\n - CODE: Source code and implementation details\n \n ## Common Section Types\n \n While you can create sections with any title, common section types include:\n - Requirements: Task or feature requirements (what needs to be done)\n - Implementation Notes: Technical details on how to implement\n - Testing Strategy: How to test the implementation\n - Reference Information: External links and resources\n - Architecture: Design and architecture details\n - Dependencies: Dependencies on other components', 'parameters': {'type': 'object', 'properties': {'entityId': {'type': 'string', 'description': "ID of the entity to retrieve sections for (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'entityType': {'type': 'string', 'description': "Type of entity to retrieve sections for: 'PROJECT', 'TASK', or 'FEATURE'", 'enum': ['PROJECT', 'FEATURE', 'TASK', 'TEMPLATE', 'SECTION']}}, 'required': ['entityType', 'entityId'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'get_task', 'description': 'Retrieves a task by its ID with options for including relationships.\n \n ## Purpose\n\n Fetches a complete task by its UUID with options to include related entities like \n sections, subtasks, dependencies, and feature information for context. This tool allows\n getting detailed information about a specific task when its ID is known.\n \n Note: Tasks store their detailed content in separate Section entities for efficiency. \n To retrieve the complete task with all content blocks, make sure to set includeSections=true.\n Otherwise, you\'ll only receive the basic task metadata and summary.\n \n ## Parameters\n \n \| Parameter \| Type \| Required \| Default \| Description \|\n \|-----------\|------\|----------\|---------\|-------------\|\n \| id \| UUID string \| Yes \| - \| The unique ID of the task to retrieve (e.g., \'550e8400-e29b-41d4-a716-446655440000\') \|\n \| includeSubtasks \| boolean \| No \| false \| Whether to include subtasks in the response (experimental feature) \|\n \| includeDependencies \| boolean \| No \| false \| Whether to include dependency information (incoming and outgoing dependencies with counts) \|\n \| includeFeature \| boolean \| No \| false \| Whether to include feature information if the task belongs to a feature \|\n \| includeSections \| boolean \| No \| false \| Whether to include sections (detailed content blocks) that contain the full content of the task. Set to true when you need the complete task context beyond the basic summary. \|\n \| summaryView \| boolean \| No \| false \| Whether to return a summarized view for context efficiency (truncates text fields) \|\n \n ## Response Format\n \n ### Success Response\n \n ```json\n {\n "success": true,\n "message": "Task retrieved successfully",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Implement API",\n "summary": "Create REST API endpoints for data access",\n "status": "in-progress",\n "priority": "high",\n "complexity": 7,\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T15:45:00Z",\n "featureId": "661e8511-f30c-41d4-a716-557788990000",\n "tags": ["api", "backend"],\n "feature": {\n "id": "661e8511-f30c-41d4-a716-557788990000",\n "name": "REST API Implementation",\n "status": "in-development"\n },\n "sections": [\n {\n "id": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Requirements",\n "content": "The API should support CRUD operations...",\n "contentFormat": "markdown",\n "ordinal": 0\n }\n ]\n }\n }\n ```\n \n ## Error Responses\n \n - RESOURCE_NOT_FOUND (404): When no task exists with the specified ID \n ```json\n {\n "success": false,\n "message": "Task not found",\n "error": {\n "code": "RESOURCE_NOT_FOUND",\n "details": "No task exists with ID 550e8400-e29b-41d4-a716-446655440000"\n }\n }\n ```\n \n - VALIDATION_ERROR (400): When the provided ID is not a valid UUID\n ```json\n {\n "success": false,\n "message": "Invalid input",\n "error": {\n "code": "VALIDATION_ERROR",\n "details": "Invalid task ID format. Must be a valid UUID."\n }\n }\n ```\n \n - DATABASE_ERROR (500): When there\'s an issue retrieving data from the database\n \n - INTERNAL_ERROR (500): For unexpected system errors during execution\n \n ## Usage Examples\n \n 1. Get basic task information:\n ```json\n {\n "id": "550e8400-e29b-41d4-a716-446655440000"\n }\n ```\n \n 2. Get task with all relationships:\n ```json\n {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "includeFeature": true,\n "includeSections": true,\n "includeSubtasks": true,\n "includeDependencies": true\n }\n ```\n \n 3. Get summarized task information (for context efficiency):\n ```json\n {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "summaryView": true\n }\n ```', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': "The unique ID (UUID) of the task to retrieve (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'includeDependencies': {'type': 'boolean', 'description': 'Whether to include dependency information (incoming and outgoing dependencies with counts)', 'default': False}, 'includeFeature': {'type': 'boolean', 'description': 'Whether to include feature information in the response if the task belongs to a feature', 'default': False}, 'includeSections': {'type': 'boolean', 'description': 'Whether to include sections (detailed content blocks) in the response', 'default': False}, 'includeSubtasks': {'type': 'boolean', 'description': 'Whether to include subtasks in the response (experimental feature)', 'default': False}, 'summaryView': {'type': 'boolean', 'description': 'Whether to return a summarized view for context efficiency (truncates text fields)', 'default': False}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'get_task_dependencies', 'description': 'Retrieves all dependencies for a specific task with filtering options and dependency chain information.\n \n This tool provides comprehensive dependency information for a task, allowing you to understand \n how a task relates to other tasks in the system. It supports filtering by dependency type \n and direction for focused queries.\n \n Example successful response:\n {\n "success": true,\n "message": "Dependencies retrieved successfully",\n "data": {\n "taskId": "550e8400-e29b-41d4-a716-446655440000",\n "dependencies": {\n "incoming": [\n {\n "id": "661e8511-f30c-41d4-a716-557788990000",\n "fromTaskId": "772f9622-g41d-52e5-b827-668899101111",\n "toTaskId": "550e8400-e29b-41d4-a716-446655440000",\n "type": "BLOCKS",\n "createdAt": "2025-05-10T14:30:00Z"\n }\n ],\n "outgoing": [\n {\n "id": "883f0733-h52e-63f6-c938-779900212222",\n "fromTaskId": "550e8400-e29b-41d4-a716-446655440000",\n "toTaskId": "994f1844-i63f-74g7-d049-8800a1323333",\n "type": "BLOCKS",\n "createdAt": "2025-05-10T15:00:00Z"\n }\n ]\n },\n "counts": {\n "total": 2,\n "incoming": 1,\n "outgoing": 1,\n "byType": {\n "BLOCKS": 2,\n "IS_BLOCKED_BY": 0,\n "RELATES_TO": 0\n }\n }\n }\n }\n \n Common error responses:\n - RESOURCE_NOT_FOUND: When the specified task doesn\'t exist\n - VALIDATION_ERROR: When provided parameters fail validation\n - DATABASE_ERROR: When there\'s an issue retrieving dependencies\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'direction': {'type': 'string', 'description': "Filter by dependency direction: 'incoming' (dependencies pointing to this task), 'outgoing' (dependencies from this task), or 'all' (both directions)", 'default': 'all', 'enum': ['incoming', 'outgoing', 'all']}, 'includeTaskInfo': {'type': 'boolean', 'description': 'Whether to include basic task information (title, status) for related tasks', 'default': False}, 'taskId': {'type': 'string', 'description': 'ID of the task to retrieve dependencies for', 'format': 'uuid'}, 'type': {'type': 'string', 'description': "Filter by dependency type: 'BLOCKS', 'IS_BLOCKED_BY', 'RELATES_TO', or 'all' for all types", 'default': 'all', 'enum': ['BLOCKS', 'IS_BLOCKED_BY', 'RELATES_TO', 'all']}}, 'required': ['taskId'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'get_template', 'description': 'Retrieve a complete template by ID with options for including sections', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID of the template to retrieve', 'format': 'uuid'}, 'includeSections': {'type': 'boolean', 'description': 'Whether to include sections in the response', 'default': False}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'list_templates', 'description': 'Retrieve a list of templates with optional filtering.\n \n ## Purpose\n CRITICAL for template-driven workflow: Always check available templates before creating\n tasks or features to ensure consistent documentation structure and comprehensive coverage.\n \n ## Template System Overview\n The system provides focused, composable templates organized into categories:\n \n AI Workflow Instructions (process guidance):\n - Local Git Branching Workflow: Step-by-step git workflow with MCP tool integration\n - GitHub PR Workflow: Complete PR creation and management process\n - Task Implementation Workflow: Structured implementation approach\n - Bug Investigation Workflow: Systematic bug analysis and resolution\n \n Documentation Properties (information capture):\n - Technical Approach: Architecture and implementation strategy\n - Requirements Specification: Detailed requirements and acceptance criteria\n - Context & Background: Project context and background information\n \n Process & Quality (standards and completion):\n - Testing Strategy: Comprehensive testing approach and coverage\n - Definition of Done: Clear completion criteria and quality gates\n \n ## Usage Patterns\n RECOMMENDED WORKFLOW:\n 1. Run `list_templates` with targetEntityType filter (TASK or FEATURE)\n 2. Identify templates from multiple categories for comprehensive coverage\n 3. Apply templates during create_task/create_feature using templateIds parameter\n 4. Use template combinations: Workflow + Documentation + Quality\n \n ## Template Selection Strategy\n For Implementation Tasks:\n - Technical Approach + Task Implementation Workflow + Testing Strategy\n \n For Bug Fixes:\n - Bug Investigation Workflow + Technical Approach + Definition of Done\n \n For Complex Features:\n - Requirements Specification + Technical Approach + Local Git Branching + Testing Strategy\n \n For Feature Planning:\n - Context & Background + Requirements Specification + Testing Strategy\n \n ## Filtering Best Practices\n - Filter by targetEntityType to match your creation needs (TASK vs FEATURE)\n - Use isEnabled=true to only see available templates\n - Filter by tags to find domain-specific templates ("authentication", "api", "testing")\n - Built-in templates (isBuiltIn=true) provide proven workflow patterns\n \n ## Context Efficiency\n Templates are designed for modular composition rather than monolithic coverage:\n - Small, focused templates (3-4 sections each) reduce cognitive overhead\n - Composable design allows mixing based on specific needs\n - Category-based organization helps with systematic selection\n \n Example successful response:\n {\n "success": true,\n "message": "Retrieved 8 templates",\n "data": {\n "templates": [\n {\n "id": "workflow-uuid-001",\n "name": "Task Implementation Workflow",\n "description": "Step-by-step implementation guidance with MCP tool integration",\n "targetEntityType": "TASK",\n "isBuiltIn": true,\n "isProtected": true,\n "isEnabled": true,\n "tags": ["workflow", "implementation", "process"]\n },\n {\n "id": "tech-uuid-002",\n "name": "Technical Approach",\n "description": "Architecture and implementation strategy documentation",\n "targetEntityType": "TASK",\n "isBuiltIn": true,\n "isProtected": true,\n "isEnabled": true,\n "tags": ["technical", "architecture", "documentation"]\n },\n {\n "id": "test-uuid-003",\n "name": "Testing Strategy",\n "description": "Comprehensive testing approach and coverage requirements",\n "targetEntityType": "TASK",\n "isBuiltIn": true,\n "isProtected": true,\n "isEnabled": true,\n "tags": ["testing", "quality", "coverage"]\n }\n ],\n "count": 8,\n "filters": {\n "targetEntityType": "TASK",\n "isBuiltIn": "Any",\n "isEnabled": "true",\n "tags": "Any"\n }\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When targetEntityType is not TASK or FEATURE\n - DATABASE_ERROR: When there\'s an issue retrieving templates\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'isBuiltIn': {'type': 'boolean', 'description': 'Filter for built-in templates only'}, 'isEnabled': {'type': 'boolean', 'description': 'Filter for enabled templates only'}, 'tags': {'type': 'string', 'description': 'Filter by tags (comma-separated)'}, 'targetEntityType': {'type': 'string', 'description': 'Filter by entity type (TASK or FEATURE)', 'enum': ['TASK', 'FEATURE']}}, 'required': [], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'reorder_sections', 'description': 'Reorders sections within a template or other entity.\n This tool changes the display order of sections by updating their ordinal values.\n \n This is useful for reorganizing content without having to send the content itself,\n which is more efficient for context usage.\n \n Parameters:\n - entityType (required): Type of entity (TEMPLATE, TASK, FEATURE)\n - entityId (required): ID of the entity\n - sectionOrder (required): New order of section IDs\n \n Validation Rules:\n - Entity must exist\n - All sections must exist and belong to the entity\n - All sections of the entity must be included', 'parameters': {'type': 'object', 'properties': {'entityId': {'type': 'string', 'description': 'ID of the entity', 'format': 'uuid'}, 'entityType': {'type': 'string', 'description': 'Type of entity (TEMPLATE, TASK, FEATURE)', 'enum': ['TEMPLATE', 'TASK', 'FEATURE']}, 'sectionOrder': {'type': 'string', 'description': 'Comma-separated list of section IDs in the desired order'}}, 'required': ['entityType', 'entityId', 'sectionOrder'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'search_features', 'description': 'Find features matching specified criteria', 'parameters': {'type': 'object', 'properties': {'createdAfter': {'type': 'string', 'description': 'Filter by creation date after this ISO-8601 date (e.g., 2025-05-10T14:30:00Z)'}, 'createdBefore': {'type': 'string', 'description': 'Filter by creation date before this ISO-8601 date (e.g., 2025-05-10T14:30:00Z)'}, 'limit': {'type': 'integer', 'description': 'Maximum number of results to return', 'default': 20, 'minimum': 1, 'maximum': 100}, 'offset': {'type': 'integer', 'description': 'Number of results to skip (for pagination)', 'default': 0, 'minimum': 0}, 'priority': {'type': 'string', 'description': 'Filter by priority (high, medium, low)'}, 'projectId': {'type': 'string', 'description': 'Filter by project ID (UUID) to get only features for a specific project', 'format': 'uuid'}, 'query': {'type': 'string', 'description': 'Text to search for in feature names and descriptions'}, 'sortBy': {'type': 'string', 'description': 'Sort results by this field (createdAt, modifiedAt, name, status, priority)', 'default': 'modifiedAt'}, 'sortDirection': {'type': 'string', 'description': 'Sort direction (asc, desc)', 'default': 'desc'}, 'status': {'type': 'string', 'description': 'Filter by feature status (planning, in-development, completed, archived)'}, 'tag': {'type': 'string', 'description': 'Filter by tag (features containing this tag)'}}, 'required': [], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'search_projects', 'description': 'Find projects matching specified criteria', 'parameters': {'type': 'object', 'properties': {'createdAfter': {'type': 'string', 'description': 'Filter by creation date after this ISO-8601 date (e.g., 2025-05-10T14:30:00Z)'}, 'createdBefore': {'type': 'string', 'description': 'Filter by creation date before this ISO-8601 date (e.g., 2025-05-10T14:30:00Z)'}, 'limit': {'type': 'integer', 'description': 'Maximum number of results to return', 'default': 20, 'minimum': 1, 'maximum': 100}, 'offset': {'type': 'integer', 'description': 'Number of results to skip (for pagination)', 'default': 0, 'minimum': 0}, 'query': {'type': 'string', 'description': 'Text to search for in project names and summaries'}, 'sortBy': {'type': 'string', 'description': 'Sort results by this field (createdAt, modifiedAt, name, status)', 'default': 'modifiedAt'}, 'sortDirection': {'type': 'string', 'description': 'Sort direction (asc, desc)', 'default': 'desc'}, 'status': {'type': 'string', 'description': 'Filter by project status (planning, in-development, completed, archived)'}, 'tag': {'type': 'string', 'description': 'Filter by tag (projects containing this tag)'}}, 'required': [], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'search_tasks', 'description': 'Searches for tasks based on various criteria.\n \n ## Purpose\n Provides flexible task discovery and filtering capabilities for project management,\n work planning, and task analysis. Essential for finding specific tasks or analyzing\n work patterns across the project.\n \n ## Search Strategy Guidelines\n \n Start Broad, Narrow Down:\n 1. Begin with no parameters to see all tasks\n 2. Add status filter to focus on specific work states\n 3. Add priority filter for urgency-based searches\n 4. Use tag filters for domain-specific searches\n 5. Combine multiple filters for precise targeting\n \n Common Search Patterns:\n \n Finding Work to Do:\n ```json\n {\n "status": "pending",\n "priority": "high",\n "sortBy": "priority",\n "sortDirection": "desc"\n }\n ```\n \n Reviewing In-Progress Work:\n ```json\n {\n "status": "in-progress",\n "sortBy": "modifiedAt",\n "sortDirection": "desc"\n }\n ```\n \n Finding Feature-Specific Tasks:\n ```json\n {\n "featureId": "feature-uuid",\n "sortBy": "complexity",\n "sortDirection": "asc"\n }\n ```\n \n Tag-Based Searches (using consistent tagging conventions):\n ```json\n {\n "tag": "task-type-bug",\n "priority": "high"\n }\n ```\n \n Text-Based Discovery:\n ```json\n {\n "query": "authentication oauth",\n "sortBy": "modifiedAt"\n }\n ```\n \n ## Filter Combinations for Different Use Cases\n \n Sprint Planning:\n - Filter by status="pending" and priority="high" or "medium"\n - Sort by complexity to group similar-sized work\n - Use pagination to handle large backlogs\n \n Bug Triage:\n - Filter by tag="task-type-bug"\n - Sort by priority and modifiedAt\n - Review high priority bugs first\n \n Feature Development:\n - Filter by featureId to see all related tasks\n - Sort by status to see progression\n - Check complexity distribution for estimation\n \n Technical Debt Management:\n - Filter by tag="technical-debt" or tag="refactoring"\n - Sort by complexity to tackle manageable items\n - Combine with priority for impact assessment\n \n ## Pagination Best Practices\n \n Default Behavior: No parameters returns all tasks, newest first, 20 per page\n \n Efficiency Guidelines:\n - Use limit=5-10 for quick overviews\n - Use limit=50-100 for comprehensive analysis\n - Use offset for paging through large result sets\n - Sort by modifiedAt for recent activity\n - Sort by priority for work planning\n - Sort by complexity for estimation analysis\n \n ## Integration with Other Tools\n \n After Search Results:\n - Use `get_task` with includeSections=true for detailed task info\n - Use `update_task` to modify status, priority, or assignments\n - Use `create_dependency` to link related tasks found in search\n - Use `get_feature` to understand feature context for tasks\n \n Complement get_overview:\n - get_overview: High-level project state and hierarchical view\n - search_tasks: Detailed filtering and analysis of specific task subsets\n \n ## Context Efficiency Features\n \n Lightweight Results: Returns essential metadata without full content or sections\n Paginated Results: Controls token usage for large datasets\n Flexible Sorting: Enables different analytical perspectives\n Multiple Filters: Precise targeting reduces noise\n \n Example successful response:\n {\n "success": true,\n "message": "Found 12 tasks",\n "data": {\n "items": [\n {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Implement OAuth Authentication API",\n "summary": "Create secure authentication flow with OAuth 2.0 and JWT tokens...",\n "status": "in-progress",\n "priority": "high",\n "complexity": 8,\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T15:45:00Z",\n "featureId": "661e8511-f30c-41d4-a716-557788990000",\n "tags": ["task-type-feature", "oauth", "authentication", "api", "security"]\n }\n ],\n "pagination": {\n "page": 1,\n "pageSize": 20,\n "totalItems": 12,\n "totalPages": 1,\n "hasNext": false,\n "hasPrevious": false\n }\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation (invalid status, priority, UUID)\n - DATABASE_ERROR: When there\'s an issue searching for tasks\n - INTERNAL_ERROR: For unexpected system errors\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'featureId': {'type': 'string', 'description': "Filter by feature ID (UUID) to get only tasks for a specific feature (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'limit': {'type': 'integer', 'description': 'Maximum number of results to return', 'default': 20, 'minimum': 1, 'maximum': 100}, 'offset': {'type': 'integer', 'description': 'Number of results to skip (for pagination)', 'default': 0, 'minimum': 0}, 'priority': {'type': 'string', 'description': "Filter by task priority. Valid values: 'high', 'medium', 'low'", 'enum': ['high', 'medium', 'low']}, 'projectId': {'type': 'string', 'description': "Filter by project ID (UUID) to get only tasks for a specific project (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'query': {'type': 'string', 'description': 'Text to search for in task titles and descriptions (searches both fields for partial matches)'}, 'sortBy': {'type': 'string', 'description': "Field to sort results by: 'createdAt', 'modifiedAt', 'priority', 'status', or 'complexity'", 'default': 'modifiedAt', 'enum': ['createdAt', 'modifiedAt', 'priority', 'status', 'complexity']}, 'sortDirection': {'type': 'string', 'description': "Sort direction: 'asc' (ascending) or 'desc' (descending)", 'default': 'desc', 'enum': ['asc', 'desc']}, 'status': {'type': 'string', 'description': "Filter by task status. Valid values: 'pending', 'in-progress', 'completed', 'cancelled', 'deferred'", 'enum': ['pending', 'in-progress', 'completed', 'cancelled', 'deferred']}, 'tag': {'type': 'string', 'description': 'Filter by tag to find tasks containing this specific tag (case insensitive)'}}, 'required': [], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'update_feature', 'description': "Update an existing feature's properties", 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID of the feature to update'}, 'name': {'type': 'string', 'description': 'New feature name'}, 'priority': {'type': 'string', 'description': 'New priority level (high, medium, low)'}, 'projectId': {'type': 'string', 'description': 'New project ID (UUID) to associate this feature with', 'format': 'uuid'}, 'status': {'type': 'string', 'description': 'New status (planning, in-development, completed, archived)'}, 'summary': {'type': 'string', 'description': 'New feature summary'}, 'tags': {'type': 'string', 'description': 'New comma-separated list of tags'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'update_project', 'description': 'Updates an existing project\'s properties.\n \n This tool modifies properties of an existing project. It supports partial updates, meaning you only need to specify \n the fields you want to change. Any fields not included in the request will retain their current values.\n \n Projects are top-level organizational containers that group related features and tasks together. Updating a project \n allows you to change its name, summary, status, or tags without affecting its relationships with features and tasks.\n \n Example successful response:\n {\n "success": true,\n "message": "Project updated successfully",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "name": "Mobile App Redesign 2.0",\n "summary": "Updated project scope with additional accessibility features",\n "status": "in-development",\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-15T16:20:00Z",\n "tags": ["mobile", "ui", "accessibility", "2025-roadmap"]\n },\n "error": null,\n "metadata": {\n "timestamp": "2025-05-15T16:20:00Z"\n }\n }\n \n Common error responses:\n - RESOURCE_NOT_FOUND: When no project exists with the specified ID\n - VALIDATION_ERROR: When parameters fail validation (e.g., empty name)\n - DATABASE_ERROR: When there\'s an issue storing the updated project\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID of the project to update'}, 'name': {'type': 'string', 'description': 'New project name'}, 'status': {'type': 'string', 'description': "New project status. Valid values: 'planning', 'in-development', 'completed', 'archived'", 'enum': ['planning', 'in-development', 'completed', 'archived']}, 'summary': {'type': 'string', 'description': 'New project summary describing its purpose and scope'}, 'tags': {'type': 'string', 'description': 'New comma-separated list of tags for categorization'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'update_section', 'description': 'Updates an existing section by its ID', 'parameters': {'type': 'object', 'properties': {'content': {'type': 'string', 'description': 'New section content'}, 'contentFormat': {'type': 'string', 'description': 'New format of the content (MARKDOWN, PLAIN_TEXT, JSON, CODE)', 'enum': ['PLAIN_TEXT', 'MARKDOWN', 'JSON', 'CODE']}, 'id': {'type': 'string', 'description': 'The unique ID of the section to update', 'format': 'uuid'}, 'ordinal': {'type': 'integer', 'description': 'New display order position (0-based)', 'minimum': 0}, 'tags': {'type': 'string', 'description': 'Comma-separated list of new tags'}, 'title': {'type': 'string', 'description': 'New section title'}, 'usageDescription': {'type': 'string', 'description': 'New usage description for the section'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'update_section_metadata', 'description': "Updates a section's metadata (title, usage description, format, ordinal, tags)\n without affecting its content.\n \n This tool allows you to update specific metadata fields without having to provide\n the entire section content, which is more efficient for context usage.\n \n Parameters:\n - id (required): UUID of the section to update\n - title (optional): New section title\n - usageDescription (optional): New usage description for the section\n - contentFormat (optional): New format of the content\n - ordinal (optional): New display order position (0-based)\n - tags (optional): Comma-separated list of new tags\n \n Validation Rules:\n - Section must exist\n - Parent template must not be protected\n - Title must not be empty if provided\n - Ordinal must be a non-negative integer", 'parameters': {'type': 'object', 'properties': {'contentFormat': {'type': 'string', 'description': 'New format of the content (MARKDOWN, PLAIN_TEXT, JSON, CODE)', 'enum': ['PLAIN_TEXT', 'MARKDOWN', 'JSON', 'CODE']}, 'id': {'type': 'string', 'description': 'The unique ID of the section to update', 'format': 'uuid'}, 'ordinal': {'type': 'integer', 'description': 'New display order position (0-based)', 'minimum': 0}, 'tags': {'type': 'string', 'description': 'Comma-separated list of new tags'}, 'title': {'type': 'string', 'description': 'New section title'}, 'usageDescription': {'type': 'string', 'description': 'New usage description for the section'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'update_section_text', 'description': 'Updates specific text within a section without requiring the entire content.\n This tool allows changing portions of section content by providing the text to replace\n and its replacement.\n \n ## Context Efficiency Strategy\n \n PREFERRED for targeted content updates in large sections:\n - Only send the specific text segment to replace and its replacement\n - Much more efficient than sending entire content for small changes\n - Ideal for correcting typos, updating specific paragraphs, or modifying parts of documentation\n - Significantly reduces token usage compared to full content updates\n \n When to Use:\n - Correcting typos in template-generated content\n - Updating specific values or references within larger documentation\n - Making incremental improvements to existing sections\n - Modifying parts of sections without affecting the overall structure\n \n Usage Examples:\n - Fixing typos: `oldText: "straegy"` → `newText: "strategy"`\n - Updating references: `oldText: "version 1.0"` → `newText: "version 2.0"`\n - Modifying template placeholders: `oldText: "[Insert details here]"` → `newText: "Actual implementation details"`\n \n Compared to Other Update Tools:\n - Use `update_section_text` for content changes (most efficient for partial updates)\n - Use `update_section_metadata` for title, format, ordinal, or tag changes\n - Use `update_section` for complete content replacement (less efficient)\n \n Parameters:\n - id (required): UUID of the section to update\n - oldText (required): The text segment to be replaced (must match exactly)\n - newText (required): The new text to replace the matched segment with\n \n Validation Rules:\n - Section must exist\n - Old text must exist in the section content\n - Both oldText and newText parameters must be provided', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID of the section to update', 'format': 'uuid'}, 'newText': {'type': 'string', 'description': 'The new text to replace the matched segment with'}, 'oldText': {'type': 'string', 'description': 'The text segment to be replaced (must match exactly)'}}, 'required': ['id', 'oldText', 'newText'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'update_task', 'description': 'Updates an existing task with the specified properties.\n \n ## Purpose\n Modifies specific fields of an existing task without affecting other properties.\n Critical for task lifecycle management and maintaining accurate project state.\n \n ## Common Update Patterns\n \n Status Progression (typical workflow):\n 1. `pending` → `in_progress` (when starting work)\n 2. `in_progress` → `completed` (when finished)\n 3. `pending` → `deferred` (when postponing)\n 4. Any status → `cancelled` (when no longer needed)\n \n Priority Adjustments:\n - Increase to `high` when blockers are resolved or deadlines approach\n - Decrease to `low` when other priorities take precedence\n - Use `medium` as default for most standard work\n \n Complexity Refinement:\n - Increase complexity (1-10) as unknowns are discovered during implementation\n - Decrease complexity when simpler solutions are found\n - Update complexity to inform future estimation accuracy\n \n ## Workflow Integration Best Practices\n \n Before Starting Work:\n ```json\n {\n "id": "task-uuid",\n "status": "in_progress"\n }\n ```\n \n When Completing Work:\n ```json\n {\n "id": "task-uuid",\n "status": "completed"\n }\n ```\n \n When Reassigning to Feature:\n ```json\n {\n "id": "orphaned-task-uuid",\n "featureId": "feature-uuid"\n }\n ```\n \n When Requirements Change:\n ```json\n {\n "id": "task-uuid",\n "title": "Updated Task Title",\n "summary": "Updated comprehensive summary with new requirements",\n "complexity": 8\n }\n ```\n \n ## Field Update Guidelines\n \n Partial Updates: Only specify fields you want to change. Unspecified fields remain unchanged.\n \n Title Updates: Keep titles concise but descriptive. Update when scope or focus changes.\n \n Summary Updates: Update summaries when requirements change or acceptance criteria evolve.\n \n Tag Management: Replace the entire tag set. To add a tag, include all existing tags plus the new one.\n \n Feature Association: Set featureId to associate task with a feature, or null to make orphaned.\n \n ## Locking System Integration\n This tool respects the locking system to prevent concurrent modifications.\n Updates may be queued if the task is currently locked by another operation.\n \n ## Error Handling\n - RESOURCE_NOT_FOUND: Task with specified ID doesn\'t exist\n - VALIDATION_ERROR: Invalid status, priority, complexity, or UUID format\n - LOCK_ERROR: Task is currently locked by another operation\n - DATABASE_ERROR: Issue persisting the update', 'parameters': {'type': 'object', 'properties': {'complexity': {'type': 'integer', 'description': 'Task complexity on a scale from 1-10', 'minimum': 1, 'maximum': 10}, 'description': {'type': 'string', 'description': 'Detailed description of the task'}, 'featureId': {'type': 'string', 'description': 'Optional ID of the feature this task belongs to', 'format': 'uuid'}, 'id': {'type': 'string', 'description': 'The unique ID of the task to update', 'format': 'uuid'}, 'priority': {'type': 'string', 'description': 'Task priority (high, medium, low)', 'enum': ['high', 'medium', 'low']}, 'status': {'type': 'string', 'description': 'Task status (pending, in-progress, completed, cancelled, deferred)', 'enum': ['pending', 'in_progress', 'completed', 'cancelled', 'deferred']}, 'tags': {'type': 'string', 'description': 'Comma-separated list of tags'}, 'title': {'type': 'string', 'description': 'The title of the task'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'update_template_metadata', 'description': "Updates a template's metadata (name, description, tags, etc.) \n without affecting its sections. Protected templates cannot be updated.\n \n This tool allows you to update specific metadata fields without having to provide\n the entire template content, which is more efficient for context usage.\n \n Parameters:\n - id (required): UUID of the template to update\n - name (optional): New template name\n - description (optional): New template description\n - targetEntityType (optional): New target entity type (TASK, FEATURE)\n - isEnabled (optional): Whether the template is enabled\n - tags (optional): Comma-separated list of new tags\n \n Validation Rules:\n - Template must exist\n - Protected templates cannot be updated\n - Name must not be empty if provided\n - No name conflict with existing templates", 'parameters': {'type': 'object', 'properties': {'description': {'type': 'string', 'description': 'New template description'}, 'id': {'type': 'string', 'description': 'The unique ID of the template to update', 'format': 'uuid'}, 'isEnabled': {'type': 'boolean', 'description': 'Whether the template is enabled'}, 'name': {'type': 'string', 'description': 'New template name'}, 'tags': {'type': 'string', 'description': 'Comma-separated list of new tags'}, 'targetEntityType': {'type': 'string', 'description': 'New target entity type (TASK, FEATURE)', 'enum': ['TASK', 'FEATURE']}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
tavily	other	{'type': 'function', 'name': 'tavily-crawl', 'description': 'A powerful web crawler that initiates a structured web crawl starting from a specified base URL. The crawler expands from that point like a tree, following internal links across pages. You can control how deep and wide it goes, and guide it to focus on specific sections of the site.', 'parameters': {'type': 'object', 'properties': {'allow_external': {'type': 'boolean', 'description': 'Whether to allow following links that go to external domains', 'default': False}, 'categories': {'type': 'array', 'description': 'Filter URLs using predefined categories like documentation, blog, api, etc', 'default': [], 'items': {'type': 'string', 'enum': ['Careers', 'Blog', 'Documentation', 'About', 'Pricing', 'Community', 'Developers', 'Contact', 'Media']}}, 'extract_depth': {'type': 'string', 'description': 'Advanced extraction retrieves more data, including tables and embedded content, with higher success but may increase latency', 'default': 'basic', 'enum': ['basic', 'advanced']}, 'format': {'type': 'string', 'description': 'The format of the extracted web page content. markdown returns content in markdown format. text returns plain text and may increase latency.', 'default': 'markdown', 'enum': ['markdown', 'text']}, 'include_favicon': {'type': 'boolean', 'description': 'Whether to include the favicon URL for each result', 'default': False}, 'instructions': {'type': 'string', 'description': 'Natural language instructions for the crawler'}, 'limit': {'type': 'integer', 'description': 'Total number of links the crawler will process before stopping', 'default': 50, 'minimum': 1}, 'max_breadth': {'type': 'integer', 'description': 'Max number of links to follow per level of the tree (i.e., per page)', 'default': 20, 'minimum': 1}, 'max_depth': {'type': 'integer', 'description': 'Max depth of the crawl. Defines how far from the base URL the crawler can explore.', 'default': 1, 'minimum': 1}, 'select_domains': {'type': 'array', 'description': 'Regex patterns to select crawling to specific domains or subdomains (e.g., ^docs\\.example\\.com$)', 'default': [], 'items': {'type': 'string'}}, 'select_paths': {'type': 'array', 'description': 'Regex patterns to select only URLs with specific path patterns (e.g., /docs/., /api/v1.)', 'default': [], 'items': {'type': 'string'}}, 'url': {'type': 'string', 'description': 'The root URL to begin the crawl'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}
tavily	other	{'type': 'function', 'name': 'tavily-extract', 'description': 'A powerful web content extraction tool that retrieves and processes raw content from specified URLs, ideal for data collection, content analysis, and research tasks.', 'parameters': {'type': 'object', 'properties': {'extract_depth': {'type': 'string', 'description': "Depth of extraction - 'basic' or 'advanced', if usrls are linkedin use 'advanced' or if explicitly told to use advanced", 'default': 'basic', 'enum': ['basic', 'advanced']}, 'format': {'type': 'string', 'description': 'The format of the extracted web page content. markdown returns content in markdown format. text returns plain text and may increase latency.', 'default': 'markdown', 'enum': ['markdown', 'text']}, 'include_favicon': {'type': 'boolean', 'description': 'Whether to include the favicon URL for each result', 'default': False}, 'include_images': {'type': 'boolean', 'description': 'Include a list of images extracted from the urls in the response', 'default': False}, 'urls': {'type': 'array', 'description': 'List of URLs to extract content from', 'items': {'type': 'string'}}}, 'required': ['urls'], 'additionalProperties': False}, 'strict': True}
tavily	other	{'type': 'function', 'name': 'tavily-map', 'description': 'A powerful web mapping tool that creates a structured map of website URLs, allowing you to discover and analyze site structure, content organization, and navigation paths. Perfect for site audits, content discovery, and understanding website architecture.', 'parameters': {'type': 'object', 'properties': {'allow_external': {'type': 'boolean', 'description': 'Whether to allow following links that go to external domains', 'default': False}, 'categories': {'type': 'array', 'description': 'Filter URLs using predefined categories like documentation, blog, api, etc', 'default': [], 'items': {'type': 'string', 'enum': ['Careers', 'Blog', 'Documentation', 'About', 'Pricing', 'Community', 'Developers', 'Contact', 'Media']}}, 'instructions': {'type': 'string', 'description': 'Natural language instructions for the crawler'}, 'limit': {'type': 'integer', 'description': 'Total number of links the crawler will process before stopping', 'default': 50, 'minimum': 1}, 'max_breadth': {'type': 'integer', 'description': 'Max number of links to follow per level of the tree (i.e., per page)', 'default': 20, 'minimum': 1}, 'max_depth': {'type': 'integer', 'description': 'Max depth of the mapping. Defines how far from the base URL the crawler can explore', 'default': 1, 'minimum': 1}, 'select_domains': {'type': 'array', 'description': 'Regex patterns to select crawling to specific domains or subdomains (e.g., ^docs\\.example\\.com$)', 'default': [], 'items': {'type': 'string'}}, 'select_paths': {'type': 'array', 'description': 'Regex patterns to select only URLs with specific path patterns (e.g., /docs/., /api/v1.)', 'default': [], 'items': {'type': 'string'}}, 'url': {'type': 'string', 'description': 'The root URL to begin the mapping'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}
tavily	other	{'type': 'function', 'name': 'tavily-search', 'description': "A powerful web search tool that provides comprehensive, real-time results using Tavily's AI search engine. Returns relevant web content with customizable parameters for result count, content type, and domain filtering. Ideal for gathering current information, news, and detailed web content analysis.", 'parameters': {'type': 'object', 'properties': {'country': {'type': 'string', 'description': 'Boost search results from a specific country. This will prioritize content from the selected country in the search results. Available only if topic is general. Country names MUST be written in lowercase, plain English, with spaces and no underscores.', 'default': '', 'enum': ['afghanistan', 'albania', 'algeria', 'andorra', 'angola', 'argentina', 'armenia', 'australia', 'austria', 'azerbaijan', 'bahamas', 'bahrain', 'bangladesh', 'barbados', 'belarus', 'belgium', 'belize', 'benin', 'bhutan', 'bolivia', 'bosnia and herzegovina', 'botswana', 'brazil', 'brunei', 'bulgaria', 'burkina faso', 'burundi', 'cambodia', 'cameroon', 'canada', 'cape verde', 'central african republic', 'chad', 'chile', 'china', 'colombia', 'comoros', 'congo', 'costa rica', 'croatia', 'cuba', 'cyprus', 'czech republic', 'denmark', 'djibouti', 'dominican republic', 'ecuador', 'egypt', 'el salvador', 'equatorial guinea', 'eritrea', 'estonia', 'ethiopia', 'fiji', 'finland', 'france', 'gabon', 'gambia', 'georgia', 'germany', 'ghana', 'greece', 'guatemala', 'guinea', 'haiti', 'honduras', 'hungary', 'iceland', 'india', 'indonesia', 'iran', 'iraq', 'ireland', 'israel', 'italy', 'jamaica', 'japan', 'jordan', 'kazakhstan', 'kenya', 'kuwait', 'kyrgyzstan', 'latvia', 'lebanon', 'lesotho', 'liberia', 'libya', 'liechtenstein', 'lithuania', 'luxembourg', 'madagascar', 'malawi', 'malaysia', 'maldives', 'mali', 'malta', 'mauritania', 'mauritius', 'mexico', 'moldova', 'monaco', 'mongolia', 'montenegro', 'morocco', 'mozambique', 'myanmar', 'namibia', 'nepal', 'netherlands', 'new zealand', 'nicaragua', 'niger', 'nigeria', 'north korea', 'north macedonia', 'norway', 'oman', 'pakistan', 'panama', 'papua new guinea', 'paraguay', 'peru', 'philippines', 'poland', 'portugal', 'qatar', 'romania', 'russia', 'rwanda', 'saudi arabia', 'senegal', 'serbia', 'singapore', 'slovakia', 'slovenia', 'somalia', 'south africa', 'south korea', 'south sudan', 'spain', 'sri lanka', 'sudan', 'sweden', 'switzerland', 'syria', 'taiwan', 'tajikistan', 'tanzania', 'thailand', 'togo', 'trinidad and tobago', 'tunisia', 'turkey', 'turkmenistan', 'uganda', 'ukraine', 'united arab emirates', 'united kingdom', 'united states', 'uruguay', 'uzbekistan', 'venezuela', 'vietnam', 'yemen', 'zambia', 'zimbabwe']}, 'days': {'type': 'number', 'description': "The number of days back from the current date to include in the search results. This specifies the time frame of data to be retrieved. Please note that this feature is only available when using the 'news' search topic", 'default': 3}, 'end_date': {'type': 'string', 'description': 'Will return all results before the specified end date. Required to be written in the format YYYY-MM-DD', 'default': ''}, 'exclude_domains': {'type': 'array', 'description': 'List of domains to specifically exclude, if the user asks to exclude a domain set this to the domain of the site', 'default': [], 'items': {'type': 'string'}}, 'include_domains': {'type': 'array', 'description': 'A list of domains to specifically include in the search results, if the user asks to search on specific sites set this to the domain of the site', 'default': [], 'items': {'type': 'string'}}, 'include_favicon': {'type': 'boolean', 'description': 'Whether to include the favicon URL for each result', 'default': False}, 'include_image_descriptions': {'type': 'boolean', 'description': 'Include a list of query-related images and their descriptions in the response', 'default': False}, 'include_images': {'type': 'boolean', 'description': 'Include a list of query-related images in the response', 'default': False}, 'include_raw_content': {'type': 'boolean', 'description': 'Include the cleaned and parsed HTML content of each search result', 'default': False}, 'max_results': {'type': 'number', 'description': 'The maximum number of search results to return', 'default': 10, 'minimum': 5, 'maximum': 20}, 'query': {'type': 'string', 'description': 'Search query'}, 'search_depth': {'type': 'string', 'description': "The depth of the search. It can be 'basic' or 'advanced'", 'default': 'basic', 'enum': ['basic', 'advanced']}, 'start_date': {'type': 'string', 'description': 'Will return all results after the specified start date. Required to be written in the format YYYY-MM-DD.', 'default': ''}, 'time_range': {'type': 'string', 'description': "The time range back from the current date to include in the search results. This feature is available for both 'general' and 'news' search topics", 'enum': ['day', 'week', 'month', 'year', 'd', 'w', 'm', 'y']}, 'topic': {'type': 'string', 'description': 'The category of the search. This will determine which of our agents will be used for the search', 'default': 'general', 'enum': ['general', 'news']}}, 'required': ['query'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-add_project_member', 'description': "Add a user to a project in Teamwork.com. In the context of Teamwork.com, a project member is a user who is assigned to a specific project. Project members can have different roles and permissions within the project, allowing them to collaborate on tasks, view project details, and contribute to the project's success. Managing project members effectively is crucial for ensuring that the right people are involved in the right tasks, and it helps maintain accountability and clarity throughout the project's lifecycle.", 'parameters': {'type': 'object', 'properties': {'project_id': {'type': 'number', 'description': 'The ID of the project to add the member to.'}, 'user_ids': {'type': 'array', 'description': 'A list of user IDs to add to the project.', 'items': {'type': 'integer'}}}, 'required': ['project_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-complete_timer', 'description': 'Complete an existing timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the timer to complete.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_comment', 'description': 'Create a new comment in Teamwork.com. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.', 'parameters': {'type': 'object', 'properties': {'body': {'type': 'string', 'description': 'The content of the comment. The content can be added as text or HTML.'}, 'content_type': {'type': 'string', 'description': "The content type of the comment. It can be either 'TEXT' or 'HTML'."}, 'object': {'type': 'object', 'description': 'The object to create the comment for. It can be a tasks, milestones, files or notebooks.', 'properties': {'id': {'type': 'number', 'description': 'The ID of the object to create the comment for.'}, 'type': {'type': 'string', 'description': 'The type of object to create the comment for.', 'enum': ['tasks', 'milestones', 'files', 'notebooks']}}}}, 'required': ['object', 'body'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_company', 'description': 'Create a new company in Teamwork.com. In the context of Teamwork.com, a company represents an organization or business entity that can be associated with users, projects, and tasks within the platform, and it is often referred to as a “client.” It serves as a way to group related users and projects under a single organizational umbrella, making it easier to manage permissions, assign responsibilities, and organize work. Companies (or clients) are frequently used to distinguish between internal teams and external collaborators, enabling teams to work efficiently while maintaining clear boundaries around ownership, visibility, and access levels across different projects.', 'parameters': {'type': 'object', 'properties': {'address_one': {'type': 'string', 'description': 'The first line of the address of the company.'}, 'address_two': {'type': 'string', 'description': 'The second line of the address of the company.'}, 'city': {'type': 'string', 'description': 'The city of the company.'}, 'country_code': {'type': 'string', 'description': "The country code of the company, e.g., 'US' for the United States."}, 'email_one': {'type': 'string', 'description': 'The primary email address of the company.'}, 'email_three': {'type': 'string', 'description': 'The tertiary email address of the company.'}, 'email_two': {'type': 'string', 'description': 'The secondary email address of the company.'}, 'fax': {'type': 'string', 'description': 'The fax number of the company.'}, 'industry_id': {'type': 'number', 'description': 'The ID of the industry the company belongs to.'}, 'manager_id': {'type': 'number', 'description': 'The ID of the user who manages the company.'}, 'name': {'type': 'string', 'description': 'The name of the company.'}, 'phone': {'type': 'string', 'description': 'The phone number of the company.'}, 'profile': {'type': 'string', 'description': 'A profile description for the company.'}, 'state': {'type': 'string', 'description': 'The state of the company.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to associate with the company.', 'items': {'type': 'integer'}}, 'website': {'type': 'string', 'description': 'The website of the company.'}, 'zip': {'type': 'string', 'description': 'The ZIP or postal code of the company.'}}, 'required': ['name'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_milestone', 'description': "Create a new milestone in Teamwork.com. In the context of Teamwork.com, a milestone represents a significant point or goal within a project that marks the completion of a major phase or a key deliverable. It acts as a high-level indicator of progress, helping teams track whether work is advancing according to plan. Milestones are typically used to coordinate efforts across different tasks and task lists, providing a clear deadline or objective that multiple team members or departments can align around. They don't contain individual tasks themselves but serve as checkpoints to ensure the project is moving in the right direction.", 'parameters': {'type': 'object', 'properties': {'assignees': {'type': 'object', 'description': 'An object containing assignees for the milestone. MUST contain at least one of: user_ids, company_ids or team_ids with non-empty arrays.', 'minProperties': 1, 'maxProperties': 3, 'properties': {'company_ids': {'type': 'array', 'description': 'List of company IDs assigned to the milestone.', 'items': {'type': 'integer'}, 'minItems': 1}, 'team_ids': {'type': 'array', 'description': 'List of team IDs assigned to the milestone.', 'items': {'type': 'integer'}, 'minItems': 1}, 'user_ids': {'type': 'array', 'description': 'List of user IDs assigned to the milestone.', 'items': {'type': 'integer'}, 'minItems': 1}}, 'additionalProperties': False, 'anyOf': [{'required': ['user_ids']}, {'required': ['company_ids']}, {'required': ['team_ids']}]}, 'description': {'type': 'string', 'description': 'A description of the milestone.'}, 'due_date': {'type': 'string', 'description': 'The due date of the milestone in the format YYYYMMDD. This date will be used in all tasks without a due date related to this milestone.'}, 'name': {'type': 'string', 'description': 'The name of the milestone.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project to create the milestone in.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to associate with the milestone.', 'items': {'type': 'integer'}}, 'tasklist_ids': {'type': 'array', 'description': 'A list of tasklist IDs to associate with the milestone.', 'items': {'type': 'integer'}}}, 'required': ['name', 'project_id', 'due_date', 'assignees'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_notebook', 'description': 'Create a new notebook in Teamwork.com. Notebook is a space where teams can create, share, and organize written content in a structured way. It’s commonly used for documenting processes, storing meeting notes, capturing research, or drafting ideas that need to be revisited and refined over time. Unlike quick messages or task comments, notebooks provide a more permanent and organized format that can be easily searched and referenced, helping teams maintain a centralized source of knowledge and ensuring important information remains accessible to everyone who needs it.', 'parameters': {'type': 'object', 'properties': {'contents': {'type': 'string', 'description': 'The contents of the notebook.'}, 'description': {'type': 'string', 'description': 'A description of the notebook.'}, 'name': {'type': 'string', 'description': 'The name of the notebook.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project to create the notebook in.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to associate with the notebook.', 'items': {'type': 'integer'}}, 'type': {'type': 'string', 'description': "The type of the notebook. Valid values are 'MARKDOWN' and 'HTML'.", 'enum': ['MARKDOWN', 'HTML']}}, 'required': ['name', 'project_id', 'contents', 'type'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_project', 'description': "Create a new project in Teamwork.com. The project feature in Teamwork.com serves as the central workspace for organizing and managing a specific piece of work or initiative. Each project provides a dedicated area where teams can plan tasks, assign responsibilities, set deadlines, and track progress toward shared goals. Projects include tools for communication, file sharing, milestones, and time tracking, allowing teams to stay aligned and informed throughout the entire lifecycle of the work. Whether it's a product launch, client engagement, or internal initiative, projects in Teamwork.com help teams structure their efforts, collaborate more effectively, and deliver results with greater visibility and accountability.", 'parameters': {'type': 'object', 'properties': {'company_id': {'type': 'number', 'description': 'The ID of the company associated with the project.'}, 'description': {'type': 'string', 'description': 'The description of the project.'}, 'end_at': {'type': 'string', 'description': 'The end date of the project in the format YYYYMMDD.'}, 'name': {'type': 'string', 'description': 'The name of the project.'}, 'owned_id': {'type': 'number', 'description': 'The ID of the user who owns the project.'}, 'start_at': {'type': 'string', 'description': 'The start date of the project in the format YYYYMMDD.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to associate with the project.', 'items': {'type': 'integer'}}}, 'required': ['name'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_tag', 'description': 'Create a new tag in Teamwork.com. In the context of Teamwork.com, a tag is a customizable label that can be applied to various items such as tasks, projects, milestones, messages, and more, to help categorize and organize work efficiently. Tags provide a flexible way to filter, search, and group related items across the platform, making it easier for teams to manage complex workflows, highlight priorities, or track themes and statuses. Since tags are user-defined, they adapt to each team’s specific needs and can be color-coded for better visual clarity.', 'parameters': {'type': 'object', 'properties': {'name': {'type': 'string', 'description': 'The name of the tag. It must have less than 50 characters.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project to associate the tag with. This is for project-scoped tags.'}}, 'required': ['name'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_task', 'description': "Create a new task in Teamwork.com. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.", 'parameters': {'type': 'object', 'properties': {'assignees': {'type': 'object', 'description': 'An object containing assignees for the task.', 'minProperties': 1, 'maxProperties': 3, 'properties': {'company_ids': {'type': 'array', 'description': 'List of company IDs assigned to the task.', 'items': {'type': 'integer'}, 'minItems': 1}, 'team_ids': {'type': 'array', 'description': 'List of team IDs assigned to the task.', 'items': {'type': 'integer'}, 'minItems': 1}, 'user_ids': {'type': 'array', 'description': 'List of user IDs assigned to the task.', 'items': {'type': 'integer'}, 'minItems': 1}}, 'additionalProperties': False, 'anyOf': [{'required': ['user_ids']}, {'required': ['company_ids']}, {'required': ['team_ids']}]}, 'description': {'type': 'string', 'description': 'The description of the task.'}, 'due_date': {'type': 'string', 'description': 'The due date of the task in ISO 8601 format (YYYY-MM-DD). When this is not provided, it will fallback to the milestone due date if a milestone is set.'}, 'estimated_minutes': {'type': 'number', 'description': 'The estimated time to complete the task in minutes.'}, 'name': {'type': 'string', 'description': 'The name of the task.'}, 'parent_task_id': {'type': 'number', 'description': 'The ID of the parent task if creating a subtask.'}, 'predecessors': {'type': 'array', 'description': 'List of task dependencies that must be completed before this task can start, defining its position in the project workflow and ensuring proper sequencing of work.', 'items': {'type': 'object', 'properties': {'task_id': {'type': 'integer', 'description': 'The ID of the predecessor task.'}, 'type': {'type': 'string', 'description': "The type of dependency. Possible values are: start or complete. 'start' means this task can complete when the predecessor starts, 'complete' means this task can complete when the predecessor is completed.", 'enum': ['start', 'complete']}}}}, 'priority': {'type': 'string', 'description': 'The priority of the task. Possible values are: low, medium, high.'}, 'progress': {'type': 'number', 'description': 'The progress of the task, as a percentage (0-100). Only whole numbers are allowed.'}, 'start_date': {'type': 'string', 'description': 'The start date of the task in ISO 8601 format (YYYY-MM-DD).'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to assign to the task.', 'items': {'type': 'integer'}}, 'tasklist_id': {'type': 'number', 'description': 'The ID of the tasklist.'}}, 'required': ['name', 'tasklist_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_tasklist', 'description': 'Create a new tasklist in Teamwork.com. In the context of Teamwork.com, a task list is a way to group related tasks within a project, helping teams organize their work into meaningful sections such as phases, categories, or deliverables. Each task list belongs to a specific project and can include multiple tasks that are typically aligned with a common goal. Task lists can be associated with milestones, and they support privacy settings that control who can view or interact with the tasks they contain. This structure helps teams manage progress, assign responsibilities, and maintain clarity across complex projects.', 'parameters': {'type': 'object', 'properties': {'description': {'type': 'string', 'description': 'The description of the tasklist.'}, 'milestone_id': {'type': 'number', 'description': 'The ID of the milestone to associate with the tasklist.'}, 'name': {'type': 'string', 'description': 'The name of the tasklist.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project to create the tasklist in.'}}, 'required': ['name', 'project_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_team', 'description': 'Create a new team in Teamwork.com. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.', 'parameters': {'type': 'object', 'properties': {'company_id': {'type': 'number', 'description': 'The ID of the company. This is used to create a team scoped for a specific company.'}, 'description': {'type': 'string', 'description': 'The description of the team.'}, 'handle': {'type': 'string', 'description': 'The handle of the team. It is a unique identifier for the team. It must not have spaces or special characters.'}, 'name': {'type': 'string', 'description': 'The name of the team.'}, 'parent_team_id': {'type': 'number', 'description': 'The ID of the parent team. This is used to create a hierarchy of teams.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project. This is used to create a team scoped for a specific project.'}, 'user_ids': {'type': 'array', 'description': 'A list of user IDs to add to the team.', 'items': {'type': 'integer'}}}, 'required': ['name'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_timelog', 'description': 'Create a new timelog in Teamwork.com. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.', 'parameters': {'type': 'object', 'properties': {'billable': {'type': 'boolean', 'description': 'If true, the timelog is billable. Defaults to false.'}, 'date': {'type': 'string', 'description': 'The date of the timelog in the format YYYY-MM-DD.'}, 'description': {'type': 'string', 'description': 'A description of the timelog.'}, 'hours': {'type': 'number', 'description': 'The number of hours spent on the timelog. Must be a positive integer.'}, 'is_utc': {'type': 'boolean', 'description': 'If true, the time is in UTC. Defaults to false.'}, 'minutes': {'type': 'number', 'description': 'The number of minutes spent on the timelog. Must be a positive integer less than 60, otherwise the hours attribute should be incremented.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project to associate the timelog with. Either project_id or task_id must be provided, but not both.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to associate with the timelog.', 'items': {'type': 'number'}}, 'task_id': {'type': 'number', 'description': 'The ID of the task to associate the timelog with. Either project_id or task_id must be provided, but not both.'}, 'time': {'type': 'string', 'description': 'The time of the timelog in the format HH:MM:SS.'}, 'user_id': {'type': 'number', 'description': 'The ID of the user to associate the timelog with. Defaults to the authenticated user if not provided.'}}, 'required': ['date', 'time', 'hours', 'minutes'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_timer', 'description': 'Create a new timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.', 'parameters': {'type': 'object', 'properties': {'billable': {'type': 'boolean', 'description': 'If true, the timer is billable. Defaults to false.'}, 'description': {'type': 'string', 'description': 'A description of the timer.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project to associate the timer with.'}, 'running': {'type': 'boolean', 'description': 'If true, the timer will start running immediately.'}, 'seconds': {'type': 'number', 'description': 'The number of seconds to set the timer for.'}, 'stop_running_timers': {'type': 'boolean', 'description': 'If true, any other running timers will be stopped when this timer is created.'}, 'task_id': {'type': 'number', 'description': 'The ID of the task to associate the timer with.'}}, 'required': ['project_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-create_user', 'description': 'Create a new user in Teamwork.com. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.', 'parameters': {'type': 'object', 'properties': {'admin': {'type': 'boolean', 'description': 'Indicates whether the user is an administrator.'}, 'company_id': {'type': 'number', 'description': 'The ID of the client/company to which the user belongs.'}, 'email': {'type': 'string', 'description': 'The email address of the user.'}, 'first_name': {'type': 'string', 'description': 'The first name of the user.'}, 'last_name': {'type': 'string', 'description': 'The last name of the user.'}, 'title': {'type': 'string', 'description': "The job title of the user, such as 'Project Manager' or 'Senior Software Developer'."}, 'type': {'type': 'string', 'description': "The type of user, such as 'account', 'collaborator', or 'contact'."}}, 'required': ['first_name', 'last_name', 'email'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_comment', 'description': 'Get an existing comment in Teamwork.com. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the comment to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_company', 'description': 'Get an existing company in Teamwork.com. In the context of Teamwork.com, a company represents an organization or business entity that can be associated with users, projects, and tasks within the platform, and it is often referred to as a “client.” It serves as a way to group related users and projects under a single organizational umbrella, making it easier to manage permissions, assign responsibilities, and organize work. Companies (or clients) are frequently used to distinguish between internal teams and external collaborators, enabling teams to work efficiently while maintaining clear boundaries around ownership, visibility, and access levels across different projects.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the company to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_milestone', 'description': "Get an existing milestone in Teamwork.com. In the context of Teamwork.com, a milestone represents a significant point or goal within a project that marks the completion of a major phase or a key deliverable. It acts as a high-level indicator of progress, helping teams track whether work is advancing according to plan. Milestones are typically used to coordinate efforts across different tasks and task lists, providing a clear deadline or objective that multiple team members or departments can align around. They don't contain individual tasks themselves but serve as checkpoints to ensure the project is moving in the right direction.", 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the milestone to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_notebook', 'description': 'Get an existing notebook in Teamwork.com. Notebook is a space where teams can create, share, and organize written content in a structured way. It’s commonly used for documenting processes, storing meeting notes, capturing research, or drafting ideas that need to be revisited and refined over time. Unlike quick messages or task comments, notebooks provide a more permanent and organized format that can be easily searched and referenced, helping teams maintain a centralized source of knowledge and ensuring important information remains accessible to everyone who needs it.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the notebook to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_project', 'description': "Get an existing project in Teamwork.com. The project feature in Teamwork.com serves as the central workspace for organizing and managing a specific piece of work or initiative. Each project provides a dedicated area where teams can plan tasks, assign responsibilities, set deadlines, and track progress toward shared goals. Projects include tools for communication, file sharing, milestones, and time tracking, allowing teams to stay aligned and informed throughout the entire lifecycle of the work. Whether it's a product launch, client engagement, or internal initiative, projects in Teamwork.com help teams structure their efforts, collaborate more effectively, and deliver results with greater visibility and accountability.", 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the project to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_tag', 'description': 'Get an existing tag in Teamwork.com. In the context of Teamwork.com, a tag is a customizable label that can be applied to various items such as tasks, projects, milestones, messages, and more, to help categorize and organize work efficiently. Tags provide a flexible way to filter, search, and group related items across the platform, making it easier for teams to manage complex workflows, highlight priorities, or track themes and statuses. Since tags are user-defined, they adapt to each team’s specific needs and can be color-coded for better visual clarity.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the tag to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_task', 'description': "Get an existing task in Teamwork.com. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.", 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the task to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_tasklist', 'description': 'Get an existing tasklist in Teamwork.com. In the context of Teamwork.com, a task list is a way to group related tasks within a project, helping teams organize their work into meaningful sections such as phases, categories, or deliverables. Each task list belongs to a specific project and can include multiple tasks that are typically aligned with a common goal. Task lists can be associated with milestones, and they support privacy settings that control who can view or interact with the tasks they contain. This structure helps teams manage progress, assign responsibilities, and maintain clarity across complex projects.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the tasklist to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_team', 'description': 'Get an existing team in Teamwork.com. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the team to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_timelog', 'description': 'Get an existing timelog in Teamwork.com. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the timelog to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_timer', 'description': 'Get an existing timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the timer to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_user', 'description': 'Get an existing user in Teamwork.com. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the user to get.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-get_user_me', 'description': 'Get the logged user in Teamwork.com. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_activities', 'description': 'List activities in Teamwork.com. Activity is a record of actions and updates that occur across your projects, tasks, and communications, giving you a clear view of what’s happening within your workspace. Activities capture changes such as task completions, activities added, files uploaded, or milestones updated, and present them in a chronological feed so teams can stay aligned without needing to check each individual project or task. This stream of information helps improve transparency, ensures accountability, and keeps everyone aware of progress and decisions as they happen.', 'parameters': {'type': 'object', 'properties': {'end_date': {'type': 'string', 'description': 'End date to filter activities. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.'}, 'log_item_types': {'type': 'array', 'description': 'Filter activities by item types.', 'items': {'type': 'string', 'enum': ['message', 'comment', 'task', 'tasklist', 'taskgroup', 'milestone', 'file', 'form', 'notebook', 'timelog', 'task_comment', 'notebook_comment', 'file_comment', 'link_comment', 'milestone_comment', 'project', 'link', 'billingInvoice', 'risk', 'projectUpdate', 'reacted', 'budget']}}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'start_date': {'type': 'string', 'description': 'Start date to filter activities. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.'}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_activities_by_project', 'description': 'List activities in Teamwork.com by project. Activity is a record of actions and updates that occur across your projects, tasks, and communications, giving you a clear view of what’s happening within your workspace. Activities capture changes such as task completions, activities added, files uploaded, or milestones updated, and present them in a chronological feed so teams can stay aligned without needing to check each individual project or task. This stream of information helps improve transparency, ensures accountability, and keeps everyone aware of progress and decisions as they happen.', 'parameters': {'type': 'object', 'properties': {'end_date': {'type': 'string', 'description': 'End date to filter activities. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.'}, 'log_item_types': {'type': 'array', 'description': 'Filter activities by item types.', 'items': {'type': 'string', 'enum': ['message', 'comment', 'task', 'tasklist', 'taskgroup', 'milestone', 'file', 'form', 'notebook', 'timelog', 'task_comment', 'notebook_comment', 'file_comment', 'link_comment', 'milestone_comment', 'project', 'link', 'billingInvoice', 'risk', 'projectUpdate', 'reacted', 'budget']}}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project to retrieve activities from.'}, 'start_date': {'type': 'string', 'description': 'Start date to filter activities. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.'}}, 'required': ['project_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_comments', 'description': 'List comments in Teamwork.com. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.', 'parameters': {'type': 'object', 'properties': {'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter comments by name.'}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_comments_by_file_version', 'description': 'List comments in Teamwork.com by file version. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.', 'parameters': {'type': 'object', 'properties': {'file_version_id': {'type': 'number', 'description': 'The ID of the file version to retrieve comments for. Each file can have multiple versions, and comments can be associated with specific versions.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter comments by name.'}}, 'required': ['file_version_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_comments_by_milestone', 'description': 'List comments in Teamwork.com by milestone. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.', 'parameters': {'type': 'object', 'properties': {'milestone_id': {'type': 'number', 'description': 'The ID of the milestone to retrieve comments for.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter comments by name.'}}, 'required': ['milestone_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_comments_by_notebook', 'description': 'List comments in Teamwork.com by notebook. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.', 'parameters': {'type': 'object', 'properties': {'notebook_id': {'type': 'number', 'description': 'The ID of the notebook to retrieve comments for.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter comments by name.'}}, 'required': ['notebook_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_comments_by_task', 'description': 'List comments in Teamwork.com by task. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.', 'parameters': {'type': 'object', 'properties': {'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter comments by name.'}, 'task_id': {'type': 'number', 'description': 'The ID of the task to retrieve comments for.'}}, 'required': ['task_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_companies', 'description': 'List companies in Teamwork.com. In the context of Teamwork.com, a company represents an organization or business entity that can be associated with users, projects, and tasks within the platform, and it is often referred to as a “client.” It serves as a way to group related users and projects under a single organizational umbrella, making it easier to manage permissions, assign responsibilities, and organize work. Companies (or clients) are frequently used to distinguish between internal teams and external collaborators, enabling teams to work efficiently while maintaining clear boundaries around ownership, visibility, and access levels across different projects.', 'parameters': {'type': 'object', 'properties': {'match_all_tags': {'type': 'boolean', 'description': 'If true, the search will match companies that have all the specified tags. If false, the search will match companies that have any of the specified tags. Defaults to false.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter companies by name. Each word from the search term is used to match against the company name.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to filter companies by tags', 'items': {'type': 'integer'}}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_industries', 'description': "List industries in Teamwork.com. Industry refers to the business sector or market category that a company belongs to, such as technology, healthcare, finance, or education. It helps provide context about the nature of a company's work and can be used to better organize and filter data across the platform. By associating companies and projects with specific industries, Teamwork.com allows teams to gain clearer insights, tailor communication, and segment information in ways that make it easier to manage relationships and understand the broader business landscape in which their clients and partners operate.", 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_milestones', 'description': "List milestones in Teamwork.com. In the context of Teamwork.com, a milestone represents a significant point or goal within a project that marks the completion of a major phase or a key deliverable. It acts as a high-level indicator of progress, helping teams track whether work is advancing according to plan. Milestones are typically used to coordinate efforts across different tasks and task lists, providing a clear deadline or objective that multiple team members or departments can align around. They don't contain individual tasks themselves but serve as checkpoints to ensure the project is moving in the right direction.", 'parameters': {'type': 'object', 'properties': {'match_all_tags': {'type': 'boolean', 'description': 'If true, the search will match milestones that have all the specified tags. If false, the search will match milestones that have any of the specified tags. Defaults to false.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter milestones by name. Each word from the search term is used to match against the milestone name and description. The milestone will be selected if each word of the term matches the milestone name or description, not requiring that the word matches are in the same field.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to filter milestones by tags', 'items': {'type': 'integer'}}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_milestones_by_project', 'description': "List milestones in Teamwork.com by project. In the context of Teamwork.com, a milestone represents a significant point or goal within a project that marks the completion of a major phase or a key deliverable. It acts as a high-level indicator of progress, helping teams track whether work is advancing according to plan. Milestones are typically used to coordinate efforts across different tasks and task lists, providing a clear deadline or objective that multiple team members or departments can align around. They don't contain individual tasks themselves but serve as checkpoints to ensure the project is moving in the right direction.", 'parameters': {'type': 'object', 'properties': {'match_all_tags': {'type': 'boolean', 'description': 'If true, the search will match milestones that have all the specified tags. If false, the search will match milestones that have any of the specified tags. Defaults to false.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project from which to retrieve milestones.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter milestones by name. Each word from the search term is used to match against the milestone name and description. The milestone will be selected if each word of the term matches the milestone name or description, not requiring that the word matches are in the same field.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to filter milestones by tags', 'items': {'type': 'integer'}}}, 'required': ['project_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_notebooks', 'description': 'List notebooks in Teamwork.com. Notebook is a space where teams can create, share, and organize written content in a structured way. It’s commonly used for documenting processes, storing meeting notes, capturing research, or drafting ideas that need to be revisited and refined over time. Unlike quick messages or task comments, notebooks provide a more permanent and organized format that can be easily searched and referenced, helping teams maintain a centralized source of knowledge and ensuring important information remains accessible to everyone who needs it.', 'parameters': {'type': 'object', 'properties': {'include_contents': {'type': 'boolean', 'description': 'If true, the contents of the notebook will be included in the response. Defaults to true.', 'default': True}, 'match_all_tags': {'type': 'boolean', 'description': 'If true, the search will match notebooks that have all the specified tags. If false, the search will match notebooks that have any of the specified tags. Defaults to false.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'project_ids': {'type': 'array', 'description': 'A list of project IDs to filter notebooks by projects', 'items': {'type': 'integer'}}, 'search_term': {'type': 'string', 'description': 'A search term to filter notebooks by name or description. The notebook will be selected if each word of the term matches the notebook name or description, not requiring that the word matches are in the same field.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to filter notebooks by tags', 'items': {'type': 'integer'}}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_projects', 'description': "List projects in Teamwork.com. The project feature in Teamwork.com serves as the central workspace for organizing and managing a specific piece of work or initiative. Each project provides a dedicated area where teams can plan tasks, assign responsibilities, set deadlines, and track progress toward shared goals. Projects include tools for communication, file sharing, milestones, and time tracking, allowing teams to stay aligned and informed throughout the entire lifecycle of the work. Whether it's a product launch, client engagement, or internal initiative, projects in Teamwork.com help teams structure their efforts, collaborate more effectively, and deliver results with greater visibility and accountability.", 'parameters': {'type': 'object', 'properties': {'match_all_tags': {'type': 'boolean', 'description': 'If true, the search will match projects that have all the specified tags. If false, the search will match projects that have any of the specified tags. Defaults to false.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter projects by name or description.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to filter projects by tags', 'items': {'type': 'integer'}}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_tags', 'description': 'List tags in Teamwork.com. In the context of Teamwork.com, a tag is a customizable label that can be applied to various items such as tasks, projects, milestones, messages, and more, to help categorize and organize work efficiently. Tags provide a flexible way to filter, search, and group related items across the platform, making it easier for teams to manage complex workflows, highlight priorities, or track themes and statuses. Since tags are user-defined, they adapt to each team’s specific needs and can be color-coded for better visual clarity.', 'parameters': {'type': 'object', 'properties': {'item_type': {'type': 'string', 'description': "The type of item to filter tags by. Valid values are 'project', 'task', 'tasklist', 'milestone', 'message', 'timelog', 'notebook', 'file', 'company' and 'link'."}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'project_ids': {'type': 'array', 'description': 'A list of project IDs to filter tags by projects', 'items': {'type': 'integer'}}, 'search_term': {'type': 'string', 'description': 'A search term to filter tags by name. Each word from the search term is used to match against the tag name.'}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_tasklists', 'description': 'List tasklists in Teamwork.com. In the context of Teamwork.com, a task list is a way to group related tasks within a project, helping teams organize their work into meaningful sections such as phases, categories, or deliverables. Each task list belongs to a specific project and can include multiple tasks that are typically aligned with a common goal. Task lists can be associated with milestones, and they support privacy settings that control who can view or interact with the tasks they contain. This structure helps teams manage progress, assign responsibilities, and maintain clarity across complex projects.', 'parameters': {'type': 'object', 'properties': {'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter tasklists by name.'}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_tasklists_by_project', 'description': 'List tasklists in Teamwork.com by project. In the context of Teamwork.com, a task list is a way to group related tasks within a project, helping teams organize their work into meaningful sections such as phases, categories, or deliverables. Each task list belongs to a specific project and can include multiple tasks that are typically aligned with a common goal. Task lists can be associated with milestones, and they support privacy settings that control who can view or interact with the tasks they contain. This structure helps teams manage progress, assign responsibilities, and maintain clarity across complex projects.', 'parameters': {'type': 'object', 'properties': {'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project from which to retrieve tasklists.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter tasklists by name.'}}, 'required': ['project_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_tasks', 'description': "List tasks in Teamwork.com. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.", 'parameters': {'type': 'object', 'properties': {'match_all_tags': {'type': 'boolean', 'description': 'If true, the search will match tasks that have all the specified tags. If false, the search will match tasks that have any of the specified tags. Defaults to false.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter tasks by name.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to filter tasks by tags', 'items': {'type': 'integer'}}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_tasks_by_project', 'description': "List tasks in Teamwork.com by project. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.", 'parameters': {'type': 'object', 'properties': {'match_all_tags': {'type': 'boolean', 'description': 'If true, the search will match tasks that have all the specified tags. If false, the search will match tasks that have any of the specified tags. Defaults to false.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project from which to retrieve tasks.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter tasks by name.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to filter tasks by tags', 'items': {'type': 'integer'}}}, 'required': ['project_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_tasks_by_tasklist', 'description': "List tasks in Teamwork.com by tasklist. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.", 'parameters': {'type': 'object', 'properties': {'match_all_tags': {'type': 'boolean', 'description': 'If true, the search will match tasks that have all the specified tags. If false, the search will match tasks that have any of the specified tags. Defaults to false.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter tasks by name.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to filter tasks by tags', 'items': {'type': 'integer'}}, 'tasklist_id': {'type': 'number', 'description': 'The ID of the tasklist from which to retrieve tasks.'}}, 'required': ['tasklist_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_teams', 'description': 'List teams in Teamwork.com. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.', 'parameters': {'type': 'object', 'properties': {'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter teams by name or handle.'}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_teams_by_company', 'description': 'List teams in Teamwork.com by client/company. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.', 'parameters': {'type': 'object', 'properties': {'company_id': {'type': 'number', 'description': 'The ID of the company from which to retrieve teams.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter teams by name or handle.'}}, 'required': ['company_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_teams_by_project', 'description': 'List teams in Teamwork.com by project. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.', 'parameters': {'type': 'object', 'properties': {'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project from which to retrieve teams.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter teams by name or handle.'}}, 'required': ['project_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_timelogs', 'description': 'List timelogs in Teamwork.com. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.', 'parameters': {'type': 'object', 'properties': {'assigned_company_ids': {'type': 'array', 'description': 'A list of company IDs to filter timelogs by assigned companies', 'items': {'type': 'integer'}}, 'assigned_team_ids': {'type': 'array', 'description': 'A list of team IDs to filter timelogs by assigned teams', 'items': {'type': 'integer'}}, 'assigned_user_ids': {'type': 'array', 'description': 'A list of user IDs to filter timelogs by assigned users', 'items': {'type': 'integer'}}, 'end_date': {'type': 'string', 'description': 'End date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.'}, 'match_all_tags': {'type': 'boolean', 'description': 'If true, the search will match timelogs that have all the specified tags. If false, the search will match timelogs that have any of the specified tags. Defaults to false.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'start_date': {'type': 'string', 'description': 'Start date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to filter timelogs by tags', 'items': {'type': 'number'}}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_timelogs_by_project', 'description': 'List timelogs in Teamwork.com by project. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.', 'parameters': {'type': 'object', 'properties': {'assigned_company_ids': {'type': 'array', 'description': 'A list of company IDs to filter timelogs by assigned companies', 'items': {'type': 'integer'}}, 'assigned_team_ids': {'type': 'array', 'description': 'A list of team IDs to filter timelogs by assigned teams', 'items': {'type': 'integer'}}, 'assigned_user_ids': {'type': 'array', 'description': 'A list of user IDs to filter timelogs by assigned users', 'items': {'type': 'integer'}}, 'end_date': {'type': 'string', 'description': 'End date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.'}, 'match_all_tags': {'type': 'boolean', 'description': 'If true, the search will match timelogs that have all the specified tags. If false, the search will match timelogs that have any of the specified tags. Defaults to false.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project from which to retrieve timelogs.'}, 'start_date': {'type': 'string', 'description': 'Start date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to filter timelogs by tags', 'items': {'type': 'number'}}}, 'required': ['project_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_timelogs_by_task', 'description': 'List timelogs in Teamwork.com by task. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.', 'parameters': {'type': 'object', 'properties': {'assigned_company_ids': {'type': 'array', 'description': 'A list of company IDs to filter timelogs by assigned companies', 'items': {'type': 'integer'}}, 'assigned_team_ids': {'type': 'array', 'description': 'A list of team IDs to filter timelogs by assigned teams', 'items': {'type': 'integer'}}, 'assigned_user_ids': {'type': 'array', 'description': 'A list of user IDs to filter timelogs by assigned users', 'items': {'type': 'integer'}}, 'end_date': {'type': 'string', 'description': 'End date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.'}, 'match_all_tags': {'type': 'boolean', 'description': 'If true, the search will match timelogs that have all the specified tags. If false, the search will match timelogs that have any of the specified tags. Defaults to false.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'start_date': {'type': 'string', 'description': 'Start date to filter timelogs. The date format follows RFC3339 - YYYY-MM-DDTHH:MM:SSZ.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to filter timelogs by tags', 'items': {'type': 'number'}}, 'task_id': {'type': 'number', 'description': 'The ID of the task from which to retrieve timelogs.'}}, 'required': ['task_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_timers', 'description': 'List timers in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.', 'parameters': {'type': 'object', 'properties': {'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project to filter timers by. Only timers associated with this project will be returned.'}, 'running_timers_only': {'type': 'boolean', 'description': 'If true, only running timers will be returned. Defaults to false, which returns all timers.'}, 'task_id': {'type': 'number', 'description': 'The ID of the task to filter timers by. Only timers associated with this task will be returned.'}, 'user_id': {'type': 'number', 'description': 'The ID of the user to filter timers by. Only timers associated with this user will be returned.'}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_users', 'description': 'List users in Teamwork.com. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.', 'parameters': {'type': 'object', 'properties': {'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter users by first or last names, or e-mail. The user will be selected if each word of the term matches the first or last name, or e-mail, not requiring that the word matches are in the same field.'}, 'type': {'type': 'number', 'description': 'Type of user to filter by. The available options are account, collaborator or contact.'}}, 'required': [], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-list_users_by_project', 'description': 'List users in Teamwork.com by project. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.', 'parameters': {'type': 'object', 'properties': {'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project from which to retrieve users.'}, 'search_term': {'type': 'string', 'description': 'A search term to filter users by first or last names, or e-mail. The user will be selected if each word of the term matches the first or last name, or e-mail, not requiring that the word matches are in the same field.'}, 'type': {'type': 'number', 'description': 'Type of user to filter by. The available options are account, collaborator or contact.'}}, 'required': ['project_id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-pause_timer', 'description': 'Pause an existing timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the timer to pause.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-resume_timer', 'description': 'Resume an existing timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the timer to resume.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_comment', 'description': 'Update an existing comment in Teamwork.com. In the Teamwork.com context, a comment is a way for users to communicate and collaborate directly within tasks, milestones, files, or other project items. Comments allow team members to provide updates, ask questions, give feedback, or share relevant information in a centralized and contextual manner. They support rich text formatting, file attachments, and @mentions to notify specific users or teams, helping keep discussions organized and easily accessible within the project. Comments are visible to all users with access to the item, promoting transparency and keeping everyone aligned.', 'parameters': {'type': 'object', 'properties': {'body': {'type': 'string', 'description': 'The content of the comment. The content can be added as text or HTML.'}, 'content_type': {'type': 'string', 'description': "The content type of the comment. It can be either 'TEXT' or 'HTML'."}, 'id': {'type': 'number', 'description': 'The ID of the comment to update.'}}, 'required': ['id', 'body'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_company', 'description': 'Update an existing company in Teamwork.com. In the context of Teamwork.com, a company represents an organization or business entity that can be associated with users, projects, and tasks within the platform, and it is often referred to as a “client.” It serves as a way to group related users and projects under a single organizational umbrella, making it easier to manage permissions, assign responsibilities, and organize work. Companies (or clients) are frequently used to distinguish between internal teams and external collaborators, enabling teams to work efficiently while maintaining clear boundaries around ownership, visibility, and access levels across different projects.', 'parameters': {'type': 'object', 'properties': {'address_one': {'type': 'string', 'description': 'The first line of the address of the company.'}, 'address_two': {'type': 'string', 'description': 'The second line of the address of the company.'}, 'city': {'type': 'string', 'description': 'The city of the company.'}, 'country_code': {'type': 'string', 'description': "The country code of the company, e.g., 'US' for the United States."}, 'email_one': {'type': 'string', 'description': 'The primary email address of the company.'}, 'email_three': {'type': 'string', 'description': 'The tertiary email address of the company.'}, 'email_two': {'type': 'string', 'description': 'The secondary email address of the company.'}, 'fax': {'type': 'string', 'description': 'The fax number of the company.'}, 'id': {'type': 'number', 'description': 'The ID of the company to update.'}, 'industry_id': {'type': 'number', 'description': 'The ID of the industry the company belongs to.'}, 'manager_id': {'type': 'number', 'description': 'The ID of the user who manages the company.'}, 'name': {'type': 'string', 'description': 'The name of the company.'}, 'phone': {'type': 'string', 'description': 'The phone number of the company.'}, 'profile': {'type': 'string', 'description': 'A profile description for the company.'}, 'state': {'type': 'string', 'description': 'The state of the company.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to associate with the company.', 'items': {'type': 'integer'}}, 'website': {'type': 'string', 'description': 'The website of the company.'}, 'zip': {'type': 'string', 'description': 'The ZIP or postal code of the company.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_milestone', 'description': "Update an existing milestone in Teamwork.com. In the context of Teamwork.com, a milestone represents a significant point or goal within a project that marks the completion of a major phase or a key deliverable. It acts as a high-level indicator of progress, helping teams track whether work is advancing according to plan. Milestones are typically used to coordinate efforts across different tasks and task lists, providing a clear deadline or objective that multiple team members or departments can align around. They don't contain individual tasks themselves but serve as checkpoints to ensure the project is moving in the right direction.", 'parameters': {'type': 'object', 'properties': {'assignees': {'type': 'object', 'description': 'An object containing assignees for the milestone.', 'minProperties': 1, 'maxProperties': 3, 'properties': {'company_ids': {'type': 'array', 'description': 'List of company IDs assigned to the milestone.', 'items': {'type': 'integer'}, 'minItems': 1}, 'team_ids': {'type': 'array', 'description': 'List of team IDs assigned to the milestone.', 'items': {'type': 'integer'}, 'minItems': 1}, 'user_ids': {'type': 'array', 'description': 'List of user IDs assigned to the milestone.', 'items': {'type': 'integer'}, 'minItems': 1}}, 'additionalProperties': False, 'anyOf': [{'required': ['user_ids']}, {'required': ['company_ids']}, {'required': ['team_ids']}]}, 'description': {'type': 'string', 'description': 'A description of the milestone.'}, 'due_date': {'type': 'string', 'description': 'The due date of the milestone in the format YYYYMMDD. This date will be used in all tasks without a due date related to this milestone.'}, 'id': {'type': 'number', 'description': 'The ID of the milestone to update.'}, 'name': {'type': 'string', 'description': 'The name of the milestone.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to associate with the milestone.', 'items': {'type': 'integer'}}, 'tasklist_ids': {'type': 'array', 'description': 'A list of tasklist IDs to associate with the milestone.', 'items': {'type': 'integer'}}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_notebook', 'description': 'Update an existing notebook in Teamwork.com. Notebook is a space where teams can create, share, and organize written content in a structured way. It’s commonly used for documenting processes, storing meeting notes, capturing research, or drafting ideas that need to be revisited and refined over time. Unlike quick messages or task comments, notebooks provide a more permanent and organized format that can be easily searched and referenced, helping teams maintain a centralized source of knowledge and ensuring important information remains accessible to everyone who needs it.', 'parameters': {'type': 'object', 'properties': {'contents': {'type': 'string', 'description': 'The contents of the notebook.'}, 'description': {'type': 'string', 'description': 'A description of the notebook.'}, 'id': {'type': 'number', 'description': 'The ID of the notebook to update.'}, 'name': {'type': 'string', 'description': 'The name of the notebook.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to associate with the notebook.', 'items': {'type': 'integer'}}, 'type': {'type': 'string', 'description': "The type of the notebook. Valid values are 'MARKDOWN' and 'HTML'.", 'enum': ['MARKDOWN', 'HTML']}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_project', 'description': "Update an existing project in Teamwork.com. The project feature in Teamwork.com serves as the central workspace for organizing and managing a specific piece of work or initiative. Each project provides a dedicated area where teams can plan tasks, assign responsibilities, set deadlines, and track progress toward shared goals. Projects include tools for communication, file sharing, milestones, and time tracking, allowing teams to stay aligned and informed throughout the entire lifecycle of the work. Whether it's a product launch, client engagement, or internal initiative, projects in Teamwork.com help teams structure their efforts, collaborate more effectively, and deliver results with greater visibility and accountability.", 'parameters': {'type': 'object', 'properties': {'company_id': {'type': 'number', 'description': 'The ID of the company associated with the project.'}, 'description': {'type': 'string', 'description': 'The description of the project.'}, 'end_at': {'type': 'string', 'description': 'The end date of the project in the format YYYYMMDD.'}, 'id': {'type': 'number', 'description': 'The ID of the project to update.'}, 'name': {'type': 'string', 'description': 'The name of the project.'}, 'owned_id': {'type': 'number', 'description': 'The ID of the user who owns the project.'}, 'start_at': {'type': 'string', 'description': 'The start date of the project in the format YYYYMMDD.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to associate with the project.', 'items': {'type': 'integer'}}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_tag', 'description': 'Update an existing tag in Teamwork.com. In the context of Teamwork.com, a tag is a customizable label that can be applied to various items such as tasks, projects, milestones, messages, and more, to help categorize and organize work efficiently. Tags provide a flexible way to filter, search, and group related items across the platform, making it easier for teams to manage complex workflows, highlight priorities, or track themes and statuses. Since tags are user-defined, they adapt to each team’s specific needs and can be color-coded for better visual clarity.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'number', 'description': 'The ID of the tag to update.'}, 'name': {'type': 'string', 'description': 'The name of the tag. It must have less than 50 characters.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project to associate the tag with. This is for project-scoped tags.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_task', 'description': "Update an existing task in Teamwork.com. In Teamwork.com, a task represents an individual unit of work assigned to one or more team members within a project. Each task can include details such as a title, description, priority, estimated time, assignees, and due date, along with the ability to attach files, leave comments, track time, and set dependencies on other tasks. Tasks are organized within task lists, helping structure and sequence work logically. They serve as the building blocks of project management in Teamwork, allowing teams to collaborate, monitor progress, and ensure accountability throughout the project's lifecycle.", 'parameters': {'type': 'object', 'properties': {'assignees': {'type': 'object', 'description': 'An object containing assignees for the task.', 'minProperties': 1, 'maxProperties': 3, 'properties': {'company_ids': {'type': 'array', 'description': 'List of company IDs assigned to the task.', 'items': {'type': 'integer'}, 'minItems': 1}, 'team_ids': {'type': 'array', 'description': 'List of team IDs assigned to the task.', 'items': {'type': 'integer'}, 'minItems': 1}, 'user_ids': {'type': 'array', 'description': 'List of user IDs assigned to the task.', 'items': {'type': 'integer'}, 'minItems': 1}}, 'additionalProperties': False, 'anyOf': [{'required': ['user_ids']}, {'required': ['company_ids']}, {'required': ['team_ids']}]}, 'description': {'type': 'string', 'description': 'The description of the task.'}, 'due_date': {'type': 'string', 'description': 'The due date of the task in ISO 8601 format (YYYY-MM-DD). When this is not provided, it will fallback to the milestone due date if a milestone is set.'}, 'estimated_minutes': {'type': 'number', 'description': 'The estimated time to complete the task in minutes.'}, 'id': {'type': 'number', 'description': 'The ID of the task to update.'}, 'name': {'type': 'string', 'description': 'The name of the task.'}, 'parent_task_id': {'type': 'number', 'description': 'The ID of the parent task if creating a subtask.'}, 'predecessors': {'type': 'array', 'description': 'List of task dependencies that must be completed before this task can start, defining its position in the project workflow and ensuring proper sequencing of work.', 'items': {'type': 'object', 'properties': {'task_id': {'type': 'integer', 'description': 'The ID of the predecessor task.'}, 'type': {'type': 'string', 'description': "The type of dependency. Possible values are: start or complete. 'start' means this task can complete when the predecessor starts, 'complete' means this task can complete when the predecessor is completed.", 'enum': ['start', 'complete']}}}}, 'priority': {'type': 'string', 'description': 'The priority of the task. Possible values are: low, medium, high.'}, 'progress': {'type': 'number', 'description': 'The progress of the task, as a percentage (0-100). Only whole numbers are allowed.'}, 'start_date': {'type': 'string', 'description': 'The start date of the task in ISO 8601 format (YYYY-MM-DD).'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to assign to the task.', 'items': {'type': 'integer'}}, 'tasklist_id': {'type': 'number', 'description': 'The ID of the tasklist. When provided, the task will be moved to this tasklist.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_tasklist', 'description': 'Update an existing tasklist in Teamwork.com. In the context of Teamwork.com, a task list is a way to group related tasks within a project, helping teams organize their work into meaningful sections such as phases, categories, or deliverables. Each task list belongs to a specific project and can include multiple tasks that are typically aligned with a common goal. Task lists can be associated with milestones, and they support privacy settings that control who can view or interact with the tasks they contain. This structure helps teams manage progress, assign responsibilities, and maintain clarity across complex projects.', 'parameters': {'type': 'object', 'properties': {'description': {'type': 'string', 'description': 'The description of the tasklist.'}, 'id': {'type': 'number', 'description': 'The ID of the tasklist to update.'}, 'milestone_id': {'type': 'number', 'description': 'The ID of the milestone to associate with the tasklist.'}, 'name': {'type': 'string', 'description': 'The name of the tasklist.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_team', 'description': 'Update an existing team in Teamwork.com. In the context of Teamwork.com, a team is a group of users who are organized together to collaborate more efficiently on projects and tasks. Teams help structure work by grouping individuals with similar roles, responsibilities, or departmental functions, making it easier to assign work, track progress, and manage communication. By using teams, organizations can streamline project planning and ensure the right people are involved in the right parts of a project, enhancing clarity and accountability across the platform.', 'parameters': {'type': 'object', 'properties': {'company_id': {'type': 'number', 'description': 'The ID of the company. This is used to create a team scoped for a specific company.'}, 'description': {'type': 'string', 'description': 'The description of the team.'}, 'handle': {'type': 'string', 'description': 'The handle of the team. It is a unique identifier for the team. It must not have spaces or special characters.'}, 'id': {'type': 'number', 'description': 'The ID of the team to update.'}, 'name': {'type': 'string', 'description': 'The name of the team.'}, 'parent_team_id': {'type': 'number', 'description': 'The ID of the parent team. This is used to create a hierarchy of teams.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project. This is used to create a team scoped for a specific project.'}, 'user_ids': {'type': 'array', 'description': 'A list of user IDs to add to the team.', 'items': {'type': 'integer'}}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_timelog', 'description': 'Update an existing timelog in Teamwork.com. Timelog refers to a recorded entry that tracks the amount of time a person has spent working on a specific task, project, or piece of work. These entries typically include details such as the duration of time worked, the date and time it was logged, who logged it, and any optional notes describing what was done during that period. Timelogs are essential for understanding how time is being allocated across projects, enabling teams to manage resources more effectively, invoice clients accurately, and assess productivity. They can be created manually or with timers, and are often used for reporting and billing purposes.', 'parameters': {'type': 'object', 'properties': {'billable': {'type': 'boolean', 'description': 'If true, the timelog is billable.'}, 'date': {'type': 'string', 'description': 'The date of the timelog in the format YYYY-MM-DD.'}, 'description': {'type': 'string', 'description': 'A description of the timelog.'}, 'hours': {'type': 'number', 'description': 'The number of hours spent on the timelog. Must be a positive integer.'}, 'id': {'type': 'number', 'description': 'The ID of the timelog to update.'}, 'is_utc': {'type': 'boolean', 'description': 'If true, the time is in UTC.'}, 'minutes': {'type': 'number', 'description': 'The number of minutes spent on the timelog. Must be a positive integer less than 60, otherwise the hours attribute should be incremented.'}, 'tag_ids': {'type': 'array', 'description': 'A list of tag IDs to associate with the timelog.', 'items': {'type': 'number'}}, 'time': {'type': 'string', 'description': 'The time of the timelog in the format HH:MM:SS.'}, 'user_id': {'type': 'number', 'description': 'The ID of the user to associate the timelog with.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_timer', 'description': 'Update an existing timer in Teamwork.com. Timer is a built-in tool that allows users to accurately track the time they spend working on specific tasks, projects, or client work. Instead of manually recording hours, users can start, pause, and stop timers directly within the platform or through the desktop and mobile apps, ensuring precise time logs without interrupting their workflow. Once recorded, these entries are automatically linked to the relevant task or project, making it easier to monitor productivity, manage billable hours, and generate detailed reports for both internal tracking and client invoicing.', 'parameters': {'type': 'object', 'properties': {'billable': {'type': 'boolean', 'description': 'If true, the timer is billable.'}, 'description': {'type': 'string', 'description': 'A description of the timer.'}, 'id': {'type': 'number', 'description': 'The ID of the timer to update.'}, 'project_id': {'type': 'number', 'description': 'The ID of the project to associate the timer with.'}, 'running': {'type': 'boolean', 'description': 'If true, the timer will start running immediately.'}, 'task_id': {'type': 'number', 'description': 'The ID of the task to associate the timer with.'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-update_user', 'description': 'Update an existing user in Teamwork.com. A user is an individual who has access to one or more projects within a Teamwork site, typically as a team member, collaborator, or administrator. Users can be assigned tasks, participate in discussions, log time, share files, and interact with other members depending on their permission levels. Each user has a unique profile that defines their role, visibility, and access to features and project data. Users can belong to clients/companies or teams within the system, and their permissions can be customized to control what actions they can perform or what information they can see.', 'parameters': {'type': 'object', 'properties': {'admin': {'type': 'boolean', 'description': 'Indicates whether the user is an administrator.'}, 'company_id': {'type': 'number', 'description': 'The ID of the client/company to which the user belongs.'}, 'email': {'type': 'string', 'description': 'The email address of the user.'}, 'first_name': {'type': 'string', 'description': 'The first name of the user.'}, 'id': {'type': 'number', 'description': 'The ID of the user to update.'}, 'last_name': {'type': 'string', 'description': 'The last name of the user.'}, 'title': {'type': 'string', 'description': "The job title of the user, such as 'Project Manager' or 'Senior Software Developer'."}, 'type': {'type': 'string', 'description': "The type of user, such as 'account', 'collaborator', or 'contact'."}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
teamwork	other	{'type': 'function', 'name': 'twprojects-users_workload', 'description': 'Workload is a visual representation of how tasks are distributed across team members, helping you understand who is overloaded, who has capacity, and how work is balanced within a project or across multiple projects. It takes into account assigned tasks, due dates, estimated time, and working hours to give managers and teams a clear picture of availability and resource allocation. By providing this insight, workload makes it easier to plan effectively, prevent burnout, and ensure that deadlines are met without placing too much pressure on any single person.', 'parameters': {'type': 'object', 'properties': {'end_date': {'type': 'string', 'description': 'The end date of the workload period. The date must be in the format YYYY-MM-DD.'}, 'page': {'type': 'number', 'description': 'Page number for pagination of results.'}, 'page_size': {'type': 'number', 'description': 'Number of results per page for pagination.'}, 'project_ids': {'type': 'array', 'description': 'List of project IDs to filter the workload by.', 'items': {'type': 'number'}}, 'start_date': {'type': 'string', 'description': 'The start date of the workload period. The date must be in the format YYYY-MM-DD.'}, 'user_company_ids': {'type': 'array', 'description': "List of users' client/company IDs to filter the workload by.", 'items': {'type': 'number'}}, 'user_ids': {'type': 'array', 'description': 'List of user IDs to filter the workload by.', 'items': {'type': 'number'}}, 'user_team_ids': {'type': 'array', 'description': "List of users' team IDs to filter the workload by.", 'items': {'type': 'number'}}}, 'required': ['start_date', 'end_date'], 'additionalProperties': False}, 'strict': True}
tembo	other	{'type': 'function', 'name': 'ask_tembo', 'description': 'Ask a question to Tembo Docs', 'parameters': {'type': 'object', 'properties': {'query': {'type': 'string', 'description': 'The ask query. For example, "how to create a Tembo instance"'}}, 'required': ['query'], 'additionalProperties': False}, 'strict': True}
tembo	other	{'type': 'function', 'name': 'create_instance', 'description': 'Create a new Tembo instance', 'parameters': {'type': 'object', 'properties': {'cpu': {'type': 'string', 'enum': ['0.25', '0.5', '1', '2', '4', '6', '8', '12', '16', '32']}, 'environment': {'type': 'string', 'enum': ['dev', 'test', 'prod']}, 'instance_name': {'type': 'string'}, 'memory': {'type': 'string', 'enum': ['512Mi', '1Gi', '2Gi', '4Gi', '8Gi', '12Gi', '16Gi', '24Gi', '32Gi', '64Gi']}, 'org_id': {'type': 'string', 'description': 'Organization ID that owns the Tembo instance'}, 'replicas': {'type': 'integer'}, 'spot': {'type': 'boolean'}, 'stack_type': {'type': 'string', 'enum': ['Analytics', 'Geospatial', 'MachineLearning', 'MessageQueue', 'MongoAlternative', 'OLTP', 'ParadeDB', 'Standard', 'Timeseries', 'VectorDB']}, 'storage': {'type': 'string', 'enum': ['10Gi', '50Gi', '100Gi', '200Gi', '300Gi', '400Gi', '500Gi', '1Ti', '1.5Ti', '2Ti']}}, 'required': ['org_id', 'instance_name', 'stack_type', 'cpu', 'memory', 'storage', 'environment'], 'additionalProperties': False}, 'strict': True}
tembo	other	{'type': 'function', 'name': 'delete_instance', 'description': 'Delete an existing Tembo instance', 'parameters': {'type': 'object', 'properties': {'instance_id': {'type': 'string', 'description': 'Delete this instance id'}, 'org_id': {'type': 'string', 'description': 'Organization id of the instance to delete'}}, 'required': ['org_id', 'instance_id'], 'additionalProperties': False}, 'strict': True}
tembo	other	{'type': 'function', 'name': 'get_all_apps', 'description': 'Get attributes for all apps', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
tembo	other	{'type': 'function', 'name': 'get_all_instances', 'description': 'Get all Tembo instances in an organization', 'parameters': {'type': 'object', 'properties': {'org_id': {'type': 'string', 'description': 'Organization id for the request'}}, 'required': ['org_id'], 'additionalProperties': False}, 'strict': True}
tembo	other	{'type': 'function', 'name': 'get_app', 'description': 'Get the attributes of a single App', 'parameters': {'type': 'object', 'properties': {'type': {'type': 'string', 'description': 'The app type to get details for'}}, 'required': ['type'], 'additionalProperties': False}, 'strict': True}
tembo	other	{'type': 'function', 'name': 'get_instance', 'description': 'Get an existing Tembo instance', 'parameters': {'type': 'object', 'properties': {'instance_id': {'type': 'string'}, 'org_id': {'type': 'string', 'description': 'Organization ID that owns the instance'}}, 'required': ['org_id', 'instance_id'], 'additionalProperties': False}, 'strict': True}

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.