smolagents/tool-scraping · Datasets at Hugging Face

server_name stringclasses 156 values	category stringclasses 1 value	tool stringlengths 176 38.2k
schogini-mcp-image-border	other	{'type': 'function', 'name': 'add-two-numbers', 'description': 'A simple tool to add two numbers.', 'parameters': {'type': 'object', 'properties': {'num1': {'type': 'string', 'description': 'First number to add'}, 'num2': {'type': 'string', 'description': 'Second number to add'}}, 'required': ['num1', 'num2'], 'additionalProperties': False}, 'strict': True}
schogini-mcp-image-border	other	{'type': 'function', 'name': 'image-border', 'description': 'Add a colored border to an image from a URL', 'parameters': {'type': 'object', 'properties': {'border_color': {'type': 'string', 'description': 'e.g., black, red, #FF0000'}, 'border_thickness': {'type': 'integer', 'minimum': 0}, 'image_url': {'type': 'string', 'description': 'Public image URL'}}, 'required': ['image_url', 'border_thickness', 'border_color'], 'additionalProperties': False}, 'strict': True}
schogini-mcp-image-border	other	{'type': 'function', 'name': 'image-meta', 'description': 'Get image metadata from a public image URL. Returns width, height, file size in bytes, image mode (e.g., RGB), and image format (e.g., PNG, JPEG).', 'parameters': {'type': 'object', 'properties': {'image_url': {'type': 'string', 'description': 'The public URL of the image.'}}, 'required': ['image_url'], 'additionalProperties': False}, 'strict': True}
scrapegraph	other	{'type': 'function', 'name': 'markdownify', 'description': 'Convert a webpage into clean, formatted markdown.\n\n Args:\n website_url: URL of the webpage to convert\n\n Returns:\n Dictionary containing the markdown result', 'parameters': {'type': 'object', 'properties': {'website_url': {'type': 'string', 'title': 'Website Url'}}, 'required': ['website_url'], 'additionalProperties': False}, 'strict': True}
scrapegraph	other	{'type': 'function', 'name': 'searchscraper', 'description': 'Perform AI-powered web searches with structured results.\n\n Args:\n user_prompt: Search query or instructions\n num_results: Number of websites to search (optional, default: 3 websites = 30 credits)\n number_of_scrolls: Number of infinite scrolls to perform on each website (optional)\n\n Returns:\n Dictionary containing search results and reference URLs', 'parameters': {'type': 'object', 'properties': {'num_results': {'type': 'integer', 'title': 'Num Results', 'default': None}, 'number_of_scrolls': {'type': 'integer', 'title': 'Number Of Scrolls', 'default': None}, 'user_prompt': {'type': 'string', 'title': 'User Prompt'}}, 'required': ['user_prompt'], 'additionalProperties': False}, 'strict': True}
scrapegraph	other	{'type': 'function', 'name': 'smartcrawler_fetch_results', 'description': 'Fetch the results of a SmartCrawler operation.\n\n Args:\n request_id: The request ID returned by smartcrawler_initiate\n\n Returns:\n Dictionary containing the crawled data (structured extraction or markdown)\n and metadata about processed pages', 'parameters': {'type': 'object', 'properties': {'request_id': {'type': 'string', 'title': 'Request Id'}}, 'required': ['request_id'], 'additionalProperties': False}, 'strict': True}
scrapegraph	other	{'type': 'function', 'name': 'smartcrawler_initiate', 'description': 'Initiate a SmartCrawler request for intelligent multi-page web crawling.\n \n SmartCrawler supports two modes:\n - AI Extraction Mode (10 credits per page): Extracts structured data based on your prompt\n - Markdown Conversion Mode (2 credits per page): Converts pages to clean markdown\n\n Args:\n url: Starting URL to crawl\n prompt: AI prompt for data extraction (required for AI mode)\n extraction_mode: "ai" for AI extraction or "markdown" for markdown conversion (default: "ai")\n depth: Maximum link traversal depth (optional)\n max_pages: Maximum number of pages to crawl (optional)\n same_domain_only: Whether to crawl only within the same domain (optional)\n\n Returns:\n Dictionary containing the request ID for async processing', 'parameters': {'type': 'object', 'properties': {'depth': {'type': 'integer', 'title': 'Depth', 'default': None}, 'extraction_mode': {'type': 'string', 'title': 'Extraction Mode', 'default': 'ai'}, 'max_pages': {'type': 'integer', 'title': 'Max Pages', 'default': None}, 'prompt': {'type': 'string', 'title': 'Prompt', 'default': None}, 'same_domain_only': {'type': 'boolean', 'title': 'Same Domain Only', 'default': None}, 'url': {'type': 'string', 'title': 'Url'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}
scrapegraph	other	{'type': 'function', 'name': 'smartscraper', 'description': 'Extract structured data from a webpage using AI.\n\n Args:\n user_prompt: Instructions for what data to extract\n website_url: URL of the webpage to scrape\n number_of_scrolls: Number of infinite scrolls to perform (optional)\n markdown_only: Whether to return only markdown content without AI processing (optional)\n\n Returns:\n Dictionary containing the extracted data or markdown content', 'parameters': {'type': 'object', 'properties': {'markdown_only': {'type': 'boolean', 'title': 'Markdown Only', 'default': None}, 'number_of_scrolls': {'type': 'integer', 'title': 'Number Of Scrolls', 'default': None}, 'user_prompt': {'type': 'string', 'title': 'User Prompt'}, 'website_url': {'type': 'string', 'title': 'Website Url'}}, 'required': ['user_prompt', 'website_url'], 'additionalProperties': False}, 'strict': True}
scrapezy	other	{'type': 'function', 'name': 'extract-structured-data', 'description': 'Extract structured data from a website.', 'parameters': {'type': 'object', 'properties': {'prompt': {'type': 'string', 'description': 'Prompt to extract data from the website'}, 'url': {'type': 'string', 'description': 'URL of the website to extract data from', 'format': 'uri'}}, 'required': ['url', 'prompt'], 'additionalProperties': False}, 'strict': True}
securenote-link-mcp-server	other	{'type': 'function', 'name': 'check_api_health', 'description': 'Check if the secure notes API is running and healthy.', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
securenote-link-mcp-server	other	{'type': 'function', 'name': 'get_instructions', 'description': 'Provides a comprehensive guide on how to use this secure note sharing service, intended for both humans and AI agents.\n\nThis guide explains the encryption process, the different methods for sharing secrets, and the tools available.', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
securenote-link-mcp-server	other	{'type': 'function', 'name': 'retrieve_and_decrypt_secret', 'description': 'Retrieve and decrypt a secret from the API.\n\nArgs:\n secret_id: The ID of the secret to retrieve\n decryption_key: The decryption key (base64 encoded)\n password: Optional password if the secret is password protected', 'parameters': {'type': 'object', 'properties': {'decryption_key': {'type': 'string', 'title': 'Decryption Key'}, 'password': {'title': 'Password', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}, 'secret_id': {'type': 'string', 'title': 'Secret Id'}}, 'required': ['secret_id', 'decryption_key'], 'additionalProperties': False}, 'strict': True}
securenote-link-mcp-server	other	{'type': 'function', 'name': 'send_secure_note', 'description': "Encrypt a message, send it to the secure notes API, and generate a single, shareable URL (default app behavior).\n\nThis function creates a user-friendly link that embeds both the secret ID and the decryption key.\nThe recipient can simply click the link to view the message—no need to copy/paste keys separately.\n\nThis is the default and recommended way to share secure notes in this app.\n\nArgs:\n message: The secret message to encrypt and send\n password: Optional password for additional protection\n expires_in: Expiration time in hours (1, 24, 72, or 168)\n\nReturns:\n A formatted message containing the shareable URL and security notes.\n\nSecurity Note:\n The decryption key is included in the URL fragment (after '#'), which is not sent to the server,\n but may be visible in browser history or if the link is shared insecurely.\n For maximum security, consider sharing the key separately.", 'parameters': {'type': 'object', 'properties': {'expires_in': {'type': 'integer', 'title': 'Expires In', 'default': 24}, 'message': {'type': 'string', 'title': 'Message'}, 'password': {'title': 'Password', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['message'], 'additionalProperties': False}, 'strict': True}
securenote-link-mcp-server	other	{'type': 'function', 'name': 'send_secure_note_return_api_url_and_key', 'description': "Encrypt a message, store it via the API, and return the retrieval URL and decryption key separately.\n\nThis function is for advanced workflows where you want to handle retrieval and decryption yourself.\nIt returns:\n - The API URL to retrieve the encrypted message (returns JSON, not a user-facing page)\n - The decryption key (base64-encoded, to be used separately)\n\nAfter calling this function, you (or your code) must:\n - Use your own code to fetch the encrypted message from the API and decrypt it using the key,\n OR\n - Use the provided 'retrieve_and_decrypt_secret' method to fetch and decrypt the message via the API.\n\nArgs:\n message: The secret message to encrypt and send.\n password: Optional password for additional protection.\n expires_in: Expiration time in hours (1, 24, 72, or 168).\n\nReturns:\n A formatted message containing:\n - The retrieval URL (API endpoint)\n - The decryption key (base64-encoded)\n - Security notes and usage instructions\n\nSecurity Note:\n For maximum security, share the URL and decryption key through different channels.\n If you want a single, user-friendly link, use 'send_secure_note' instead.\n\n---\nDecryption process specifics:\n- The encryption algorithm used is AES-256-GCM.\n- The encrypted data is base64-encoded, with a separate IV (also base64-encoded).\n- The API's response structure is JSON with fields like 'encryptedData' and 'iv'.\n- The key is base64-encoded.\n\nAnyone writing their own decryption code must:\n- Correctly parse the API response (get 'encryptedData' and 'iv').\n- Base64-decode the key, iv, and encryptedData.\n- Use AES-256-GCM to decrypt, using the key and iv.", 'parameters': {'type': 'object', 'properties': {'expires_in': {'type': 'integer', 'title': 'Expires In', 'default': 24}, 'message': {'type': 'string', 'title': 'Message'}, 'password': {'title': 'Password', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['message'], 'additionalProperties': False}, 'strict': True}
semgrep	other	{'type': 'function', 'name': 'get_abstract_syntax_tree', 'description': 'Returns the Abstract Syntax Tree (AST) for the provided code file in JSON format\n\n Use this tool when you need to:\n - get the Abstract Syntax Tree (AST) for the provided code file - get the AST of a file\n - understand the structure of the code in a more granular way\n - see what a parser sees in the code', 'parameters': {'type': 'object', 'properties': {'code': {'type': 'string', 'title': 'Code', 'description': 'The code to get the AST for'}, 'language': {'type': 'string', 'title': 'Language', 'description': 'The programming language of the code'}}, 'required': ['code', 'language'], 'additionalProperties': False}, 'strict': True}
semgrep	other	{'type': 'function', 'name': 'get_supported_languages', 'description': 'Returns a list of supported languages by Semgrep\n\n Only use this tool if you are not sure what languages Semgrep supports.', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
semgrep	other	{'type': 'function', 'name': 'security_check', 'description': "Runs a fast security check on code and returns any issues found.\n\n Use this tool when you need to:\n - scan code for security vulnerabilities\n - verify that code is secure\n - double check that code is secure before committing\n - get a second opinion on code security\n\n If there are any issues found, you MUST fix them or offer to fix them and\n explain to the user why it's important to fix.\n If there are no issues, you can be reasonably confident that the code is secure.", 'parameters': {'type': 'object', 'properties': {'code_files': {'type': 'array', 'title': 'Code Files', 'description': "List of dictionaries with 'filename' and 'content' keys", 'items': {'type': 'object', 'additionalProperties': {'type': 'string'}}}}, 'required': ['code_files'], 'additionalProperties': False}, 'strict': True}
semgrep	other	{'type': 'function', 'name': 'semgrep_findings', 'description': 'Fetches findings from the Semgrep AppSec Platform Findings API.\n\n This function retrieves security, code quality, and supply chain findings that have already been\n identified by previous Semgrep scans and uploaded to the Semgrep AppSec platform. It does NOT\n perform a new scan or analyze code directly. Instead, it queries the Semgrep API to access\n historical scan results for a given repository or set of repositories.\n\n DEFAULT BEHAVIOR: By default, this tool should filter by the current repository. The model\n should determine the current repository name and pass it in the \'repos\' parameter to ensure\n findings are scoped to the relevant codebase. However, users may explicitly request findings\n from other repositories, in which case the model should respect that request.\n\n Use this function when a prompt requests a summary, list, or analysis of existing findings,\n such as:\n - "Please list the top 10 security findings and propose solutions for them."\n - "Show all open critical vulnerabilities in this repository."\n - "Summarize the most recent Semgrep scan results."\n - "Get findings from repository X" (explicitly requesting different repo)\n\n This function is ideal for:\n - Reviewing, listing, or summarizing findings from past scans.\n - Providing actionable insights or remediation advice based on existing scan data.\n\n Do NOT use this function to perform a new scan or check code that has not yet been analyzed by\n Semgrep. For new scans, use the appropriate scanning function.\n\n Args:\n issue_type (Optional[List[str]]): Filter findings by type. Use \'sast\' for code analysis\n findings and \'sca\' for supply chain analysis findings (e.g., [\'sast\'], [\'sca\']).\n status (Optional[str]): Filter findings by status (default: \'open\').\n repos (Optional[List[str]]): List of repository names to filter results. By default, should\n include the current repository name to scope findings appropriately. Can be overridden\n when users explicitly request findings from other repositories.\n severities (Optional[List[str]]): Filter findings by severity (e.g., [\'critical\', \'high\']).\n confidence (Optional[List[str]]): Filter findings by confidence level (e.g., [\'high\']).\n autotriage_verdict (Optional[str]): Filter findings by auto-triage verdict\n (default: \'true_positive\').\n page (Optional[int]): Page number for paginated results. (default: 0)\n page_size (int): Number of findings per page (default: 100, min: 100, max: 3000).\n\n Returns:\n List[Finding]: A list of findings matching the specified filters, where each finding\n contains details such as rule ID, description, severity, file location, and remediation\n guidance if available.', 'parameters': {'type': 'object', 'properties': {'autotriage_verdict': {'type': 'string', 'title': 'Autotriage Verdict', 'default': 'true_positive'}, 'confidence': {'type': 'array', 'title': 'Confidence', 'default': None, 'items': {'type': 'string'}}, 'issue_type': {'type': 'array', 'title': 'Issue Type', 'default': ['sast', 'sca'], 'items': {'type': 'string'}}, 'page': {'type': 'integer', 'title': 'Page', 'default': 0}, 'page_size': {'type': 'integer', 'title': 'Page Size', 'default': 100}, 'repos': {'type': 'array', 'title': 'Repos', 'default': None, 'items': {'type': 'string'}}, 'severities': {'type': 'array', 'title': 'Severities', 'default': None, 'items': {'type': 'string'}}, 'status': {'type': 'string', 'title': 'Status', 'default': 'open'}}, 'required': [], 'additionalProperties': False}, 'strict': True}
semgrep	other	{'type': 'function', 'name': 'semgrep_rule_schema', 'description': 'Get the schema for a Semgrep rule\n\n Use this tool when you need to:\n - get the schema required to write a Semgrep rule\n - need to see what fields are available for a Semgrep rule\n - verify what fields are available for a Semgrep rule\n - verify the syntax for a Semgrep rule is correct', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
semgrep	other	{'type': 'function', 'name': 'semgrep_scan', 'description': 'Runs a Semgrep scan on provided code content and returns the findings in JSON format\n\n Use this tool when you need to:\n - scan code files for security vulnerabilities\n - scan code files for other issues', 'parameters': {'type': 'object', 'properties': {'code_files': {'type': 'array', 'title': 'Code Files', 'description': "List of dictionaries with 'filename' and 'content' keys", 'items': {'type': 'object', 'additionalProperties': {'type': 'string'}}}, 'config': {'title': 'Config', 'description': "Optional Semgrep configuration string (e.g. 'p/docker', 'p/xss', 'auto')", 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['code_files'], 'additionalProperties': False}, 'strict': True}
semgrep	other	{'type': 'function', 'name': 'semgrep_scan_local', 'description': 'Runs a Semgrep scan locally on provided code files returns the findings in JSON format.\n\n Files are expected to be in the current paths are absolute paths to the code files.\n\n Use this tool when you need to:\n - scan code files for security vulnerabilities\n - scan code files for other issues', 'parameters': {'type': 'object', 'properties': {'code_files': {'type': 'array', 'title': 'Code Files', 'description': "List of dictionaries with 'path' pointing to the absolute path of the code file", 'items': {'type': 'object', 'additionalProperties': {'type': 'string'}}}, 'config': {'title': 'Config', 'description': "Optional Semgrep configuration string (e.g. 'p/docker', 'p/xss', 'auto')", 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['code_files'], 'additionalProperties': False}, 'strict': True}
semgrep	other	{'type': 'function', 'name': 'semgrep_scan_with_custom_rule', 'description': 'Runs a Semgrep scan with a custom rule on provided code content\n and returns the findings in JSON format\n\n Use this tool when you need to:\n - scan code files for specific security vulnerability not covered by the default Semgrep rules\n - scan code files for specific issue not covered by the default Semgrep rules', 'parameters': {'type': 'object', 'properties': {'code_files': {'type': 'array', 'title': 'Code Files', 'description': "List of dictionaries with 'filename' and 'content' keys", 'items': {'type': 'object', 'additionalProperties': {'type': 'string'}}}, 'rule': {'type': 'string', 'title': 'Rule', 'description': 'Semgrep YAML rule string'}}, 'required': ['code_files', 'rule'], 'additionalProperties': False}, 'strict': True}
sentry	other	{'type': 'function', 'name': 'get_sentry_issue', 'description': 'Retrieve and analyze a Sentry issue by ID or URL. Use this tool when you need to:\n - Investigate production errors and crashes\n - Access detailed stacktraces from Sentry\n - Analyze error patterns and frequencies\n - Get information about when issues first/last occurred\n - Review error counts and status', 'parameters': {'type': 'object', 'properties': {'issue_id_or_url': {'type': 'string', 'description': 'Sentry issue ID or URL to analyze'}}, 'required': ['issue_id_or_url'], 'additionalProperties': False}, 'strict': True}
sequentialthinking	other	{'type': 'function', 'name': 'sequentialthinking', 'description': 'A detailed tool for dynamic and reflective problem-solving through thoughts.\nThis tool helps analyze problems through a flexible thinking process that can adapt and evolve.\nEach thought can build on, question, or revise previous insights as understanding deepens.\n\nWhen to use this tool:\n- Breaking down complex problems into steps\n- Planning and design with room for revision\n- Analysis that might need course correction\n- Problems where the full scope might not be clear initially\n- Problems that require a multi-step solution\n- Tasks that need to maintain context over multiple steps\n- Situations where irrelevant information needs to be filtered out\n\nKey features:\n- You can adjust total_thoughts up or down as you progress\n- You can question or revise previous thoughts\n- You can add more thoughts even after reaching what seemed like the end\n- You can express uncertainty and explore alternative approaches\n- Not every thought needs to build linearly - you can branch or backtrack\n- Generates a solution hypothesis\n- Verifies the hypothesis based on the Chain of Thought steps\n- Repeats the process until satisfied\n- Provides a correct answer\n\nParameters explained:\n- thought: Your current thinking step, which can include:\n* Regular analytical steps\n* Revisions of previous thoughts\n* Questions about previous decisions\n* Realizations about needing more analysis\n* Changes in approach\n* Hypothesis generation\n* Hypothesis verification\n- next_thought_needed: True if you need more thinking, even if at what seemed like the end\n- thought_number: Current number in sequence (can go beyond initial total if needed)\n- total_thoughts: Current estimate of thoughts needed (can be adjusted up/down)\n- is_revision: A boolean indicating if this thought revises previous thinking\n- revises_thought: If is_revision is true, which thought number is being reconsidered\n- branch_from_thought: If branching, which thought number is the branching point\n- branch_id: Identifier for the current branch (if any)\n- needs_more_thoughts: If reaching end but realizing more thoughts needed\n\nYou should:\n1. Start with an initial estimate of needed thoughts, but be ready to adjust\n2. Feel free to question or revise previous thoughts\n3. Don\'t hesitate to add more thoughts if needed, even at the "end"\n4. Express uncertainty when present\n5. Mark thoughts that revise previous thinking or branch into new paths\n6. Ignore information that is irrelevant to the current step\n7. Generate a solution hypothesis when appropriate\n8. Verify the hypothesis based on the Chain of Thought steps\n9. Repeat the process until satisfied with the solution\n10. Provide a single, ideally correct answer as the final output\n11. Only set next_thought_needed to false when truly done and a satisfactory answer is reached', 'parameters': {'type': 'object', 'properties': {'branchFromThought': {'type': 'integer', 'description': 'Branching point thought number', 'minimum': 1}, 'branchId': {'type': 'string', 'description': 'Branch identifier'}, 'isRevision': {'type': 'boolean', 'description': 'Whether this revises previous thinking'}, 'needsMoreThoughts': {'type': 'boolean', 'description': 'If more thoughts are needed'}, 'nextThoughtNeeded': {'type': 'boolean', 'description': 'Whether another thought step is needed'}, 'revisesThought': {'type': 'integer', 'description': 'Which thought is being reconsidered', 'minimum': 1}, 'thought': {'type': 'string', 'description': 'Your current thinking step'}, 'thoughtNumber': {'type': 'integer', 'description': 'Current thought number', 'minimum': 1}, 'totalThoughts': {'type': 'integer', 'description': 'Estimated total thoughts needed', 'minimum': 1}}, 'required': ['thought', 'nextThoughtNeeded', 'thoughtNumber', 'totalThoughts'], 'additionalProperties': False}, 'strict': True}
short-io	other	{'type': 'function', 'name': 'create-short-link', 'description': 'Create short link from the original URL', 'parameters': {'type': 'object', 'properties': {'allowDuplicates': {'type': 'boolean'}, 'androidURL': {'type': 'string'}, 'archived': {'type': 'boolean'}, 'clicksLimit': {'type': 'number'}, 'cloaking': {'type': 'boolean'}, 'createdAt': {'type': ['string', 'number']}, 'domain': {'type': 'string'}, 'expiredURL': {'type': 'string'}, 'expiresAt': {'type': ['string', 'number']}, 'folderId': {'type': 'string'}, 'integrationAdroll': {'type': 'string'}, 'integrationFB': {'type': 'string'}, 'integrationGA': {'type': 'string'}, 'integrationGTM': {'type': 'string'}, 'iphoneURL': {'type': 'string'}, 'originalURL': {'type': 'string'}, 'password': {'type': 'string'}, 'passwordContact': {'type': 'boolean'}, 'path': {'type': 'string'}, 'redirectType': {'type': 'number', 'enum': [301, 302, 307, 308]}, 'skipQS': {'type': 'boolean'}, 'splitPercent': {'type': 'number'}, 'splitURL': {'type': 'string'}, 'tags': {'type': 'array', 'items': {'type': 'string'}}, 'title': {'type': 'string'}, 'ttl': {'type': ['string', 'number']}, 'utmCampaign': {'type': 'string'}, 'utmContent': {'type': 'string'}, 'utmMedium': {'type': 'string'}, 'utmSource': {'type': 'string'}, 'utmTerm': {'type': 'string'}}, 'required': ['domain', 'originalURL'], 'additionalProperties': False}, 'strict': True}
short-io	other	{'type': 'function', 'name': 'domain-statistics', 'description': 'Get detailed statistics for domain in given period', 'parameters': {'type': 'object', 'properties': {'clicksChartInterval': {'type': 'string', 'enum': ['hour', 'day', 'week', 'month']}, 'domainId': {'type': 'number'}, 'endDate': {'type': 'string'}, 'exclude': {'type': 'object', 'additionalProperties': False}, 'include': {'type': 'object', 'additionalProperties': False}, 'period': {'type': 'string', 'enum': ['custom', 'today', 'yesterday', 'total', 'week', 'month', 'lastmonth', 'last7', 'last30']}, 'skipTops': {'type': 'boolean'}, 'startDate': {'type': 'string'}, 'tz': {'type': 'string'}}, 'required': ['domainId', 'period'], 'additionalProperties': False}, 'strict': True}
short-io	other	{'type': 'function', 'name': 'get-domains', 'description': 'Get list of domains in the account', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
short-io	other	{'type': 'function', 'name': 'get-link-list', 'description': 'Get list of links for a domain', 'parameters': {'type': 'object', 'properties': {'afterDate': {'type': 'string'}, 'beforeDate': {'type': 'string'}, 'createAt': {'type': 'string'}, 'dateSortOrder': {'type': 'string', 'enum': ['asc', 'desc']}, 'domainId': {'type': 'number'}, 'folderId': {'type': 'string'}, 'limit': {'type': 'number'}}, 'required': ['domainId'], 'additionalProperties': False}, 'strict': True}
short-io	other	{'type': 'function', 'name': 'link-statistics', 'description': 'Get detailed statistics for link in given period', 'parameters': {'type': 'object', 'properties': {'clicksChartInterval': {'type': 'string', 'enum': ['hour', 'day', 'week', 'month']}, 'endDate': {'type': 'string'}, 'exclude': {'type': 'object', 'additionalProperties': False}, 'include': {'type': 'object', 'additionalProperties': False}, 'linkId': {'type': 'string'}, 'period': {'type': 'string', 'enum': ['custom', 'today', 'yesterday', 'total', 'week', 'month', 'lastmonth', 'last7', 'last30']}, 'skipTops': {'type': 'boolean'}, 'startDate': {'type': 'string'}, 'tz': {'type': 'string'}}, 'required': ['linkId'], 'additionalProperties': False}, 'strict': True}
short-io	other	{'type': 'function', 'name': 'search-links', 'description': 'Search for links in a domain', 'parameters': {'type': 'object', 'properties': {'afterDate': {'type': 'string'}, 'beforeDate': {'type': 'string'}, 'dateSortOrder': {'type': 'string', 'enum': ['asc', 'desc']}, 'domainId': {'type': 'number'}, 'folderId': {'type': 'string'}, 'limit': {'type': 'number'}, 'q': {'type': 'string', 'description': 'Search query'}, 'tz': {'type': 'string'}}, 'required': ['domainId'], 'additionalProperties': False}, 'strict': True}
short-io	other	{'type': 'function', 'name': 'top-by-interval-column', 'description': 'Get top clicks values by interval and counts for specified column', 'parameters': {'type': 'object', 'properties': {'column': {'type': 'string', 'enum': ['path', 'path_404', 'method', 'st', 'proto', 'human', 'browser', 'browser_version', 'country', 'city', 'social', 'refhost', 'os', 'utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'goal_completed', 'ab_path']}, 'domainId': {'type': 'number'}, 'endDate': {'type': 'string'}, 'exclude': {'type': 'object', 'additionalProperties': False}, 'include': {'type': 'object', 'additionalProperties': False}, 'interval': {'type': 'string', 'enum': ['hour', 'day', 'week', 'month']}, 'limit': {'type': 'number'}, 'period': {'type': 'string', 'enum': ['custom', 'today', 'yesterday', 'total', 'week', 'month', 'lastmonth', 'last7', 'last30']}, 'startDate': {'type': 'string'}, 'tz': {'type': 'string'}}, 'required': ['domainId', 'column', 'interval'], 'additionalProperties': False}, 'strict': True}
short-io	other	{'type': 'function', 'name': 'top-column-by-link-statistics', 'description': 'Get top column values for link in given period', 'parameters': {'type': 'object', 'properties': {'column': {'type': 'string', 'enum': ['path', 'path_404', 'method', 'st', 'proto', 'human', 'browser', 'browser_version', 'country', 'city', 'social', 'refhost', 'os', 'utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'goal_completed', 'ab_path']}, 'endDate': {'type': 'string'}, 'exclude': {'type': 'object', 'additionalProperties': False}, 'include': {'type': 'object', 'additionalProperties': False}, 'limit': {'type': 'number'}, 'linkId': {'type': 'string'}, 'period': {'type': 'string', 'enum': ['custom', 'today', 'yesterday', 'total', 'week', 'month', 'lastmonth', 'last7', 'last30']}, 'prefix': {'type': 'string'}, 'startDate': {'type': 'string'}, 'tz': {'type': 'string'}}, 'required': ['linkId', 'column'], 'additionalProperties': False}, 'strict': True}
short-io	other	{'type': 'function', 'name': 'top-column-statistics', 'description': 'Get top clicks values for specified column, ordered by clicks desc', 'parameters': {'type': 'object', 'properties': {'column': {'type': 'string', 'enum': ['path', 'path_404', 'method', 'st', 'proto', 'human', 'browser', 'browser_version', 'country', 'city', 'social', 'refhost', 'os', 'utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'goal_completed', 'ab_path']}, 'domainId': {'type': 'number'}, 'endDate': {'type': 'string'}, 'exclude': {'type': 'object', 'additionalProperties': False}, 'include': {'type': 'object', 'additionalProperties': False}, 'limit': {'type': 'number'}, 'period': {'type': 'string', 'enum': ['custom', 'today', 'yesterday', 'total', 'week', 'month', 'lastmonth', 'last7', 'last30']}, 'startDate': {'type': 'string'}, 'tz': {'type': 'string'}}, 'required': ['domainId', 'column'], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'create_job_from_notebook', 'description': 'Create a scheduled job to run a notebook (uploaded to shared space).\n\n Args:\n ctx: Context object\n name: Name of the job\n notebook_path: Remote path to the shared notebook file\n mode: Job mode (options: "Once", "Recurring")\n execution_interval_in_minutes: Optional interval in minutes for recurring jobs\n\n Returns:\n Dict with job creation result', 'parameters': {'type': 'object', 'properties': {'execution_interval_in_minutes': {'title': 'Execution Interval In Minutes', 'default': None, 'anyOf': [{'type': 'integer'}, {'type': 'null'}]}, 'mode': {'type': 'string', 'title': 'Mode', 'default': 'Once'}, 'name': {'type': 'string', 'title': 'Name'}, 'notebook_path': {'type': 'string', 'title': 'Notebook Path'}}, 'required': ['name', 'notebook_path'], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'create_notebook_file', 'description': 'Create a Jupyter notebook file in the correct singlestore format and saves it to a temporary location.\n\n This tool validates the provided content against the Jupyter notebook schema and creates a properly\n formatted .ipynb file in a temporary location. The content is converted from the simplified format\n to the full Jupyter notebook format.\n\n Args:\n content: Notebook content in the format: {\n "cells": [\n {"type": "markdown", "content": "Markdown content here"},\n {"type": "code", "content": "Python code here"}\n ]\n }\n\n Returns:\n Dictionary with the temporary file path and validation status\n\n Example:\n content = {\n "cells": [\n {"type": "markdown", "content": "# My Notebook\nThis is a sample notebook"},\n {"type": "code", "content": "import pandas as pd\nprint(\'Hello World\')"}\n ]\n }', 'parameters': {'type': 'object', 'properties': {'content': {'type': 'object', 'title': 'Content', 'additionalProperties': True}}, 'required': ['content'], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'create_starter_workspace', 'description': 'Create a new starter workspace using the SingleStore SDK.\n\n This tool provides a modern SDK-based approach to creating starter workspaces,\n offering improved reliability and better error handling compared to direct API calls.\n\n Args:\n name: Unique name for the new starter workspace\n database_name: Name of the database to create in the starter workspace\n provider: Cloud provider for the workspace (e.g., "AWS", "GCP", "Azure")\n region_name: Region where the workspace should be deployed (e.g., "us-west-2", "europe-west1")\n\n Returns:\n Dictionary with starter workspace creation details including:\n - workspace_id: Unique identifier for the created workspace\n - name: Display name of the workspace\n - endpoint: Connection endpoint URL\n - database_name: Name of the primary database\n\n Example Usage:\n ```python\n result = create_starter_workspace(\n ctx=ctx,\n name="my-test-workspace",\n database_name="analytics_db"\n )\n workspace_id = result["workspace_id"]\n endpoint = result["endpoint"]\n ```', 'parameters': {'type': 'object', 'properties': {'database_name': {'type': 'string', 'title': 'Database Name'}, 'name': {'type': 'string', 'title': 'Name'}, 'provider': {'title': 'Provider', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}, 'region_name': {'title': 'Region Name', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['name', 'database_name'], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'delete_job', 'description': 'Delete a scheduled job by its ID.\n\n Args:\n ctx: Context object\n job_id: ID of the job to delete\n\n Returns:\n Dict with deletion result', 'parameters': {'type': 'object', 'properties': {'job_id': {'type': 'string', 'title': 'Job Id'}}, 'required': ['job_id'], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'get_job', 'description': 'Retrieve details of a scheduled job by its ID.\n\n Args:\n ctx: Context object\n job_id: ID of the job to retrieve\n\n Returns:\n Dict with job details or error info', 'parameters': {'type': 'object', 'properties': {'job_id': {'type': 'string', 'title': 'Job Id'}}, 'required': ['job_id'], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'get_user_info', 'description': 'Retrieve all information about the current user.\n\n Returns:\n dict: User information including userID, email, firstName, lastName.\n\n Performance Tip:\n Cache the returned info when making multiple API calls.', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'list_regions', 'description': 'List all available deployment regions where SingleStore workspaces can be deployed by the user.\n\n Returns region information including:\n - regionID: Unique identifier for the region\n - provider: Cloud provider (AWS, GCP, or Azure)\n - name: Human-readable region name (e.g., Europe West 2 (London), US West 2 (Oregon))\n\n Use this tool to:\n 1. Select optimal deployment regions based on:\n - Geographic proximity to users\n - Compliance requirements\n - Cost considerations\n - Available cloud providers\n 2. Plan multi-region deployments', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'list_sharedtier_regions', 'description': 'List all regions where shared tier workspaces can be created.\n\n This tool provides information about available regions for creating starter workspaces,\n including region names and cloud providers.\n\n Args:\n ctx: Context for user interaction and logging\n\n Returns:\n Dictionary with region information including:\n - regionName: Name of the region (e.g., "us-west-2", "europe-west1")\n - provider: Cloud provider (AWS, GCP, or Azure)\n - name: Human-readable region name (e.g., Europe West 2 (London), US West 2 (Oregon))\n\n Example Usage:\n ```python\n result = await list_shared_tier_regions(ctx)\n regions = result["data"]["result"]\n ```', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'list_starter_workspaces', 'description': 'List all starter (virtual) workspaces available to the user in SingleStore.\n\n Returns detailed information about each starter workspace:\n - virtualWorkspaceID: Unique identifier for the workspace\n - name: Display name of the workspace\n - endpoint: Connection endpoint URL\n - databaseName: Name of the primary database\n - mysqlDmlPort: Port for MySQL protocol connections\n - webSocketPort: Port for WebSocket connections\n - state: Current status of the workspace\n\n Use this tool to:\n 1. Get starter workspace IDs for other operations\n 2. Check starter workspace availability and status\n 3. Obtain connection details for database access', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'organization_info', 'description': "Retrieve information about the current user's organization in SingleStore.\n\n Returns organization details including:\n - orgID: Unique identifier for the organization\n - name: Organization display name", 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'resume_workspace', 'description': 'Resume a workspace within a specified workspace group in SingleStore.\n\n Args:\n workspace_group_id: Unique identifier of the workspace group\n workspace_id: Unique identifier of the workspace to resume\n\n Returns:\n Dictionary with status, message, and metadata about the resume operation', 'parameters': {'type': 'object', 'properties': {'workspace_id': {'type': 'string', 'title': 'Workspace Id'}}, 'required': ['workspace_id'], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'run_sql', 'description': 'Use this tool to execute a single SQL statement against a SingleStore database.\n\n Returns:\n - Query results with column names and typed values\n - Row count and metadata\n - Execution status\n - Workspace type ("shared" for starter workspaces, "dedicated" for regular workspaces)\n - Workspace name\n\n Args:\n id: Workspace or starter workspace ID\n sql_query: The SQL query to execute\n database: (optional) Database name to use\n\n Returns:\n Standardized response with query results and metadata', 'parameters': {'type': 'object', 'properties': {'database': {'title': 'Database', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}, 'id': {'type': 'string', 'title': 'Id'}, 'sql_query': {'type': 'string', 'title': 'Sql Query'}}, 'required': ['sql_query', 'id'], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'terminate_starter_workspace', 'description': 'Permanently delete a starter workspace in SingleStore with safety confirmations.\n\n ⚠️ WARNING: This action CANNOT be undone. All workspace data will be permanently lost.\n Make sure to backup important data before proceeding.\n\n Safety Features:\n - Requires explicit user confirmation (if elicitation is supported)\n - Validates workspace existence\n - Provides warning messages\n - Includes error handling\n\n Args:\n ctx: Context for user interaction and logging\n workspace_id: Workspace identifier (format: "ws-" followed by alphanumeric chars)\n\n Returns:\n {\n "status": "success" \| "error" \| "cancelled",\n "message": str, # Human-readable result\n "workspace_id": str,\n "workspace_name": str, # If available\n "termination_time": str, # ISO 8601 (if successful)\n "error": str # If status="error"\n }\n\n Example:\n ```python\n result = await terminate_starter_workspace(ctx, "ws-abc123")\n if result["status"] == "success":\n print(f"Workspace {result[\'workspace_name\']} terminated")\n ```\n\n Related:\n - list_starter_workspaces()\n - create_starter_workspace()', 'parameters': {'type': 'object', 'properties': {'workspace_id': {'type': 'string', 'title': 'Workspace Id'}}, 'required': ['workspace_id'], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'upload_notebook_file', 'description': 'Upload a notebook file from a local local_path to SingleStore shared or personal space.\n\n This tool validates the notebook schema before uploading. If upload_name or upload_location\n are not provided, the user will be prompted through elicitation.\n\n Args:\n local_path: Local file system path to the notebook file (.ipynb)\n upload_name: Optional. Name of the file after upload (with or without .ipynb extension).\n If not provided, user will be prompted.\n upload_location: Optional. Either "shared" or "personal". If not provided, user will be prompted.\n\n Returns:\n Dictionary with upload status and file information\n\n Example:\n local_path = "/path/to/my_notebook.ipynb"\n upload_name = "analysis_notebook" # Optional\n upload_location = "shared" # Optional', 'parameters': {'type': 'object', 'properties': {'local_path': {'type': 'string', 'title': 'Local Path'}, 'upload_location': {'title': 'Upload Location', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}, 'upload_name': {'title': 'Upload Name', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['local_path'], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'workspace_groups_info', 'description': 'List all workspace groups accessible to the user in SingleStore.\n\n Returns detailed information for each group:\n - workspaceGroupID: Unique identifier for the group\n - name: Display name of the workspace group\n - region: Region information (name, provider)\n - firewallRanges: List of allowed IP ranges for the group\n - allowAllTraffic: Whether all traffic is allowed to the group\n - createdAt: Timestamp of group creation\n - terminatedAt: Timestamp when the group was terminated (if applicable)\n\n\n Use this tool to:\n 1. Get workspace group IDs for other operations\n 2. Plan maintenance windows\n\n Related operations:\n - Use workspaces_info to list workspaces within a group\n - Use execute_sql to run queries on workspaces in a group', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
singlestore	other	{'type': 'function', 'name': 'workspaces_info', 'description': "List all workspaces within a specified workspace group in SingleStore.\n\n Returns detailed information for each workspace:\n - createdAt: Timestamp of workspace creation\n - deploymentType: Type of deployment (e.g., 'PRODUCTION')\n - endpoint: Connection URL for database access\n - name: Display name of the workspace\n - size: Compute and storage configuration\n - state: Current status (e.g., 'ACTIVE', 'PAUSED')\n - terminatedAt: End timestamp if applicable\n - workspaceGroupID: Workspacegroup identifier\n - workspaceID: Unique workspace identifier\n\n Args:\n workspace_group_id: Unique identifier of the workspace group\n\n Returns:\n List of workspace information dictionaries", 'parameters': {'type': 'object', 'properties': {'workspace_group_id': {'type': 'string', 'title': 'Workspace Group Id'}}, 'required': ['workspace_group_id'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'api_hub_create_portal', 'description': "Create a new portal within API Hub.\n\nParameters:\n- name (string): The portal name.\n- subdomain (string) required: The portal subdomain.\n- offline (boolean): If set to true the portal will not be visible to customers.\n- routing (string): Determines the routing strategy ('browser' or 'proxy').\n- credentialsEnabled (string): Indicates if credentials are enabled for the portal.\n- swaggerHubOrganizationId (string) required: The corresponding API Hub (formerly SwaggerHub) organization UUID.\n- openapiRenderer (string): Portal level setting for the OpenAPI renderer. SWAGGER_UI - Use the Swagger UI renderer. ELEMENTS - Use the Elements renderer. TOGGLE - Switch between the two renderers with elements set as the default.\n- pageContentFormat (string): The format of the page content.", 'parameters': {'type': 'object', 'properties': {'credentialsEnabled': {'type': 'string', 'description': 'Indicates if credentials are enabled for the portal.'}, 'name': {'type': 'string', 'description': 'The portal name.'}, 'offline': {'type': 'boolean', 'description': 'If set to true the portal will not be visible to customers.'}, 'openapiRenderer': {'type': 'string', 'description': 'Portal level setting for the OpenAPI renderer. SWAGGER_UI - Use the Swagger UI renderer. ELEMENTS - Use the Elements renderer. TOGGLE - Switch between the two renderers with elements set as the default.'}, 'pageContentFormat': {'type': 'string', 'description': 'The format of the page content.'}, 'routing': {'type': 'string', 'description': "Determines the routing strategy ('browser' or 'proxy')."}, 'subdomain': {'type': 'string', 'description': 'The portal subdomain.'}, 'swaggerHubOrganizationId': {'type': 'string', 'description': 'The corresponding API Hub (formerly SwaggerHub) organization UUID.'}}, 'required': ['subdomain', 'swaggerHubOrganizationId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'api_hub_create_portal_product', 'description': "Create a new product for a specific portal.\n\nParameters:\n- portalId (string) required: Portal UUID or subdomain.\n- type (string) required: Product type (Allowed values: 'new', 'copy').\n- name (string) required: Product name.\n- slug (string) required: URL component for this product. Must be unique within the portal.\n- description (string): Product description.\n- public (boolean): Indicates if the product is public.\n- hidden (string): Indicates if the product is hidden.\n- role (boolean): Indicates if the product has a role.", 'parameters': {'type': 'object', 'properties': {'description': {'type': 'string', 'description': 'Product description.'}, 'hidden': {'type': 'string', 'description': 'Indicates if the product is hidden.'}, 'name': {'type': 'string', 'description': 'Product name.'}, 'portalId': {'type': 'string', 'description': 'Portal UUID or subdomain.'}, 'public': {'type': 'boolean', 'description': 'Indicates if the product is public.'}, 'role': {'type': 'boolean', 'description': 'Indicates if the product has a role.'}, 'slug': {'type': 'string', 'description': 'URL component for this product. Must be unique within the portal.'}, 'type': {'type': 'string', 'description': "Product type (Allowed values: 'new', 'copy')."}}, 'required': ['portalId', 'type', 'name', 'slug'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'api_hub_delete_portal', 'description': 'Delete a specific portal.\n\nParameters:\n- portalId (string) required: Portal UUID or subdomain.', 'parameters': {'type': 'object', 'properties': {'portalId': {'type': 'string', 'description': 'Portal UUID or subdomain.'}}, 'required': ['portalId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'api_hub_delete_portal_product', 'description': 'Delete a product from a specific portal\n\nParameters:\n- productId (string) required: Product UUID, or identifier in the format.', 'parameters': {'type': 'object', 'properties': {'productId': {'type': 'string', 'description': 'Product UUID, or identifier in the format.'}}, 'required': ['productId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'api_hub_get_portal', 'description': 'Retrieve information about a specific portal.\n\nParameters:\n- portalId (string) required: Portal UUID or subdomain.', 'parameters': {'type': 'object', 'properties': {'portalId': {'type': 'string', 'description': 'Portal UUID or subdomain.'}}, 'required': ['portalId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'api_hub_get_portal_product', 'description': 'Retrieve information about a specific product resource.\n\nParameters:\n- productId (string) required: Product UUID, or identifier in the format.', 'parameters': {'type': 'object', 'properties': {'productId': {'type': 'string', 'description': 'Product UUID, or identifier in the format.'}}, 'required': ['productId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'api_hub_list_portal_products', 'description': 'Get products for a specific portal that match your criteria.\n\nParameters:\n- portalId (string) required: Portal UUID or subdomain.', 'parameters': {'type': 'object', 'properties': {'portalId': {'type': 'string', 'description': 'Portal UUID or subdomain.'}}, 'required': ['portalId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'api_hub_list_portals', 'description': 'Search for available portals within API Hub. Only portals where you have at least a designer role, either at the product level or organization level, are returned.', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'api_hub_update_portal', 'description': "Update a specific portal's configuration.\n\nParameters:\n- portalId (string) required: Portal UUID or subdomain.\n- name (string): The portal name.\n- subdomain (string): The portal subdomain.\n- customDomain (boolean): Indicates if the portal has a custom domain.\n- gtmKey (string): Google Tag Manager key for the portal.\n- offline (boolean): If set to true the portal will not be visible to customers.\n- routing (string): Determines the routing strategy ('browser' or 'proxy').\n- credentialsEnabled (boolean): Indicates if credentials are enabled for the portal.\n- openapiRenderer (string): Portal level setting for the OpenAPI renderer. SWAGGER_UI - Use the Swagger UI renderer. ELEMENTS - Use the Elements renderer. TOGGLE - Switch between the two renderers with elements set as the default.\n- pageContentFormat (string): The format of the page content.", 'parameters': {'type': 'object', 'properties': {'credentialsEnabled': {'type': 'boolean', 'description': 'Indicates if credentials are enabled for the portal.'}, 'customDomain': {'type': 'boolean', 'description': 'Indicates if the portal has a custom domain.'}, 'gtmKey': {'type': 'string', 'description': 'Google Tag Manager key for the portal.'}, 'name': {'type': 'string', 'description': 'The portal name.'}, 'offline': {'type': 'boolean', 'description': 'If set to true the portal will not be visible to customers.'}, 'openapiRenderer': {'type': 'string', 'description': 'Portal level setting for the OpenAPI renderer. SWAGGER_UI - Use the Swagger UI renderer. ELEMENTS - Use the Elements renderer. TOGGLE - Switch between the two renderers with elements set as the default.'}, 'pageContentFormat': {'type': 'string', 'description': 'The format of the page content.'}, 'portalId': {'type': 'string', 'description': 'Portal UUID or subdomain.'}, 'routing': {'type': 'string', 'description': "Determines the routing strategy ('browser' or 'proxy')."}, 'subdomain': {'type': 'string', 'description': 'The portal subdomain.'}}, 'required': ['portalId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'api_hub_update_portal_product', 'description': "Update a product's settings within a specific portal.\n\nParameters:\n- productId (string) required: Product UUID, or identifier in the format.\n- name (string): Product name.\n- slug (string): URL component for this product. Must be unique within the portal.\n- description (string): Product description.\n- public (boolean): Indicates if the product is public.\n- hidden (string): Indicates if the product is hidden.", 'parameters': {'type': 'object', 'properties': {'description': {'type': 'string', 'description': 'Product description.'}, 'hidden': {'type': 'string', 'description': 'Indicates if the product is hidden.'}, 'name': {'type': 'string', 'description': 'Product name.'}, 'productId': {'type': 'string', 'description': 'Product UUID, or identifier in the format.'}, 'public': {'type': 'boolean', 'description': 'Indicates if the product is public.'}, 'slug': {'type': 'string', 'description': 'URL component for this product. Must be unique within the portal.'}}, 'required': ['productId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'reflect_cancel_suite_execution', 'description': 'Cancel a reflect suite execution\n\nParameters:\n- suiteId (string) required: ID of the reflect suite to cancel execution for\n- executionId (string) required: ID of the reflect suite execution to cancel', 'parameters': {'type': 'object', 'properties': {'executionId': {'type': 'string', 'description': 'ID of the reflect suite execution to cancel'}, 'suiteId': {'type': 'string', 'description': 'ID of the reflect suite to cancel execution for'}}, 'required': ['suiteId', 'executionId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'reflect_execute_suite', 'description': 'Execute a reflect suite\n\nParameters:\n- suiteId (string) required: ID of the reflect suite to list executions for', 'parameters': {'type': 'object', 'properties': {'suiteId': {'type': 'string', 'description': 'ID of the reflect suite to list executions for'}}, 'required': ['suiteId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'reflect_get_suite_execution_status', 'description': 'Get the status of a reflect suite execution\n\nParameters:\n- suiteId (string) required: ID of the reflect suite to get execution status for\n- executionId (string) required: ID of the reflect suite execution to get status for', 'parameters': {'type': 'object', 'properties': {'executionId': {'type': 'string', 'description': 'ID of the reflect suite execution to get status for'}, 'suiteId': {'type': 'string', 'description': 'ID of the reflect suite to get execution status for'}}, 'required': ['suiteId', 'executionId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'reflect_get_test_status', 'description': 'Get the status of a reflect test execution\n\nParameters:\n- testId (string) required: ID of the reflect test to run\n- executionId (string) required: ID of the reflect test execution to get status for', 'parameters': {'type': 'object', 'properties': {'executionId': {'type': 'string', 'description': 'ID of the reflect test execution to get status for'}, 'testId': {'type': 'string', 'description': 'ID of the reflect test to run'}}, 'required': ['testId', 'executionId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'reflect_list_suite_executions', 'description': 'List all executions for a given suite\n\nParameters:\n- suiteId (string) required: ID of the reflect suite to list executions for', 'parameters': {'type': 'object', 'properties': {'suiteId': {'type': 'string', 'description': 'ID of the reflect suite to list executions for'}}, 'required': ['suiteId'], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'reflect_list_suites', 'description': 'Retrieve a list of all reflect suites available', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'reflect_list_tests', 'description': 'List all reflect tests', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
smartbear	other	{'type': 'function', 'name': 'reflect_run_test', 'description': 'Run a reflect test\n\nParameters:\n- testId (string) required: ID of the reflect test to run', 'parameters': {'type': 'object', 'properties': {'testId': {'type': 'string', 'description': 'ID of the reflect test to run'}}, 'required': ['testId'], 'additionalProperties': False}, 'strict': True}
SQLite	other	{'type': 'function', 'name': 'append_insight', 'description': 'Add a business insight to the memo', 'parameters': {'type': 'object', 'properties': {'insight': {'type': 'string', 'description': 'Business insight discovered from data analysis'}}, 'required': ['insight'], 'additionalProperties': False}, 'strict': True}
SQLite	other	{'type': 'function', 'name': 'create_table', 'description': 'Create a new table in the SQLite database', 'parameters': {'type': 'object', 'properties': {'query': {'type': 'string', 'description': 'CREATE TABLE SQL statement'}}, 'required': ['query'], 'additionalProperties': False}, 'strict': True}
SQLite	other	{'type': 'function', 'name': 'describe_table', 'description': 'Get the schema information for a specific table', 'parameters': {'type': 'object', 'properties': {'table_name': {'type': 'string', 'description': 'Name of the table to describe'}}, 'required': ['table_name'], 'additionalProperties': False}, 'strict': True}
SQLite	other	{'type': 'function', 'name': 'list_tables', 'description': 'List all tables in the SQLite database', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}
SQLite	other	{'type': 'function', 'name': 'read_query', 'description': 'Execute a SELECT query on the SQLite database', 'parameters': {'type': 'object', 'properties': {'query': {'type': 'string', 'description': 'SELECT SQL query to execute'}}, 'required': ['query'], 'additionalProperties': False}, 'strict': True}
SQLite	other	{'type': 'function', 'name': 'write_query', 'description': 'Execute an INSERT, UPDATE, or DELETE query on the SQLite database', 'parameters': {'type': 'object', 'properties': {'query': {'type': 'string', 'description': 'SQL query to execute'}}, 'required': ['query'], 'additionalProperties': False}, 'strict': True}
supadata	other	{'type': 'function', 'name': 'supadata_check_crawl_status', 'description': 'Check the status and retrieve results of a crawl job created with supadata_crawl.\n\nPurpose: Monitor crawl job progress and retrieve completed results.\nWorkflow: Use the job ID returned from supadata_crawl to check status and get results.\n\nUsage Example:\n```json\n{\n "name": "supadata_check_crawl_status",\n "arguments": {\n "id": "550e8400-e29b-41d4-a716-446655440000"\n }\n}\n```\n\nReturns: \n- Job status: \'scraping\', \'completed\', \'failed\', or \'cancelled\'\n- For completed jobs: URL, Markdown content, page title, and description for each crawled page\n- Progress information and any error details if applicable\n\nTip: Poll this endpoint periodically until status is \'completed\' or \'failed\'.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'Crawl job ID returned from supadata_crawl'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
supadata	other	{'type': 'function', 'name': 'supadata_check_transcript_status', 'description': 'Check the status and retrieve results of a transcript job created with supadata_transcript.\n\nPurpose: Monitor transcript job progress and retrieve completed results.\nWorkflow: Use the job ID returned from supadata_transcript to check status and get results.\n\nUsage Example:\n```json\n{\n "name": "supadata_check_transcript_status",\n "arguments": {\n "id": "550e8400-e29b-41d4-a716-446655440000"\n }\n}\n```\n\nReturns: \n- Job status: \'queued\', \'active\', \'completed\', \'failed\'\n- For completed jobs: Full transcript content\n- Error details if job failed\n\nTip: Poll this endpoint periodically until status is \'completed\' or \'failed\'.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'Transcript job ID returned from supadata_transcript'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
supadata	other	{'type': 'function', 'name': 'supadata_crawl', 'description': 'Create a crawl job to extract content from all pages on a website using Supadata\'s crawling API.\n\nPurpose: Crawl a whole website and get content of all pages on it.\nBest for: Extracting content from multiple related pages when you need comprehensive coverage.\nWorkflow: 1) Create crawl job → 2) Receive job ID → 3) Check job status and retrieve results\n\nCrawling Behavior:\n- Follows only child links within the specified domain\n- Example: For https://supadata.ai/blog, crawls https://supadata.ai/blog/article-1 but not https://supadata.ai/about\n- To crawl entire website, use top-level URL like https://supadata.ai\n\nUsage Example:\n```json\n{\n "name": "supadata_crawl",\n "arguments": {\n "url": "https://example.com",\n "limit": 100\n }\n}\n```\n\nReturns: Job ID for status checking. Use supadata_check_crawl_status to check progress.\nJob Status: Possible statuses are \'scraping\', \'completed\', \'failed\', or \'cancelled\'\n\nImportant: Respect robots.txt and website terms of service when crawling web content.', 'parameters': {'type': 'object', 'properties': {'limit': {'type': 'number', 'description': 'Maximum number of pages to crawl (1-5000, default: 100)', 'default': 100, 'minimum': 1, 'maximum': 5000}, 'url': {'type': 'string', 'description': 'URL of the webpage to crawl'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}
supadata	other	{'type': 'function', 'name': 'supadata_map', 'description': 'Crawl a whole website and get all URLs on it using Supadata\'s mapping API.\n\nPurpose: Extract all links found on a website for content discovery and sitemap creation.\nBest for: Website content discovery, SEO analysis, content aggregation, automated web scraping and indexing.\nUse cases: Creating a sitemap, running a crawler to fetch content from all pages of a website.\n\nUsage Example:\n```json\n{\n "name": "supadata_map",\n "arguments": {\n "url": "https://example.com"\n }\n}\n```\n\nReturns: Array of URLs found on the website.', 'parameters': {'type': 'object', 'properties': {'url': {'type': 'string', 'description': 'URL of the website to map'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}
supadata	other	{'type': 'function', 'name': 'supadata_scrape', 'description': 'Extract content from any web page to Markdown format using Supadata\'s powerful scraping API.\n\nPurpose: Single page content extraction with automatic formatting to Markdown.\nBest for: When you know exactly which page contains the information you need.\n\nUsage Example:\n```json\n{\n "name": "supadata_scrape",\n "arguments": {\n "url": "https://example.com",\n "noLinks": false,\n "lang": "en"\n }\n}\n```\n\nReturns: \n- URL of the scraped page\n- Extracted content in Markdown format\n- Page name and description\n- Character count\n- List of URLs found on the page', 'parameters': {'type': 'object', 'properties': {'lang': {'type': 'string', 'description': 'Preferred language for the scraped content (ISO 639-1 code)', 'default': 'en'}, 'noLinks': {'type': 'boolean', 'description': 'When true, removes markdown links from the content', 'default': False}, 'url': {'type': 'string', 'description': 'Web page URL to scrape'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}
supadata	other	{'type': 'function', 'name': 'supadata_transcript', 'description': 'Extract transcript from supported video platforms (YouTube, TikTok, Instagram, Twitter) or file URLs using Supadata\'s transcript API.\n\nPurpose: Get transcripts from video content across multiple platforms.\nBest for: Video content analysis, subtitle extraction, content indexing.\n\nUsage Example:\n```json\n{\n "name": "supadata_transcript",\n "arguments": {\n "url": "https://youtube.com/watch?v=example",\n "lang": "en",\n "text": false,\n "mode": "auto"\n }\n}\n```\n\nReturns: \n- Either immediate transcript content\n- Or job ID for asynchronous processing (use supadata_check_transcript_status)\n\nSupported Platforms: YouTube, TikTok, Instagram, Twitter, and file URLs', 'parameters': {'type': 'object', 'properties': {'chunkSize': {'type': 'number', 'description': 'Maximum characters per transcript chunk'}, 'lang': {'type': 'string', 'description': 'Preferred language code (ISO 639-1)'}, 'mode': {'type': 'string', 'description': 'Transcript generation mode', 'enum': ['native', 'auto', 'generate']}, 'text': {'type': 'boolean', 'description': 'Return plain text instead of formatted output', 'default': False}, 'url': {'type': 'string', 'description': 'Video or file URL to get transcript from (YouTube, TikTok, Instagram, Twitter, file)'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}
suzieq	other	{'type': 'function', 'name': 'run_suzieq_show', 'description': 'Runs a SuzieQ \'show\' query via its REST API.\n\n Args:\n table: The name of the SuzieQ table to query (e.g., \'device\', \'bgp\', \'interface\', \'route\').\n filters: An optional dictionary of filter parameters for the SuzieQ query\n (e.g., {"hostname": "leaf01", "vrf": "default", "state": "Established"}).\n Keys should match SuzieQ filter names. Values can be strings or lists of strings.\n If no filters are needed, this can be None, null, or an empty dictionary.\n\n Returns:\n A JSON string representing the result from the SuzieQ API, or a JSON string with an error message.', 'parameters': {'type': 'object', 'properties': {'filters': {'title': 'Filters', 'default': None, 'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}]}, 'table': {'type': 'string', 'title': 'Table'}}, 'required': ['table'], 'additionalProperties': False}, 'strict': True}
suzieq	other	{'type': 'function', 'name': 'run_suzieq_summarize', 'description': 'Runs a SuzieQ \'summarize\' query via its REST API.\n\n Args:\n table: The name of the SuzieQ table to summarize (e.g., \'device\', \'bgp\', \'interface\', \'route\').\n filters: An optional dictionary of filter parameters for the SuzieQ query\n (e.g., {"hostname": "leaf01", "vrf": "default"}).\n Keys should match SuzieQ filter names. Values can be strings or lists of strings.\n If no filters are needed, this can be None, null, or an empty dictionary.\n\n Returns:\n A JSON string representing the summarized result from the SuzieQ API,\n or a JSON string with an error message.', 'parameters': {'type': 'object', 'properties': {'filters': {'title': 'Filters', 'default': None, 'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}]}, 'table': {'type': 'string', 'title': 'Table'}}, 'required': ['table'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'add_section', 'description': 'Adds a section to a task, feature, or project.\n \n ## Purpose\n \n Sections store detailed content for tasks, features, and projects in a structured way.\n Instead of storing all content directly in the entities, sections allow for\n organized content blocks with specific formats and purposes. This approach\n optimizes context efficiency by keeping core entities lightweight.\n \n ## Usage Guidelines\n \n EFFICIENCY RECOMMENDATION: For adding multiple sections at once, prefer using \n `bulk_create_sections` instead of multiple `add_section` calls. This is especially \n important for:\n - Creating initial section sets for new tasks/features\n - Adding sections with shorter content (reduces network overhead)\n - Template-like section creation scenarios\n \n WHEN TO USE add_section:\n - Adding a single section with substantial content\n - Adding sections incrementally during task development\n - Creating sections that require careful individual validation\n \n ## Content Organization Strategy\n \n Common Section Types (use these title patterns for consistency):\n - Requirements: What needs to be accomplished, acceptance criteria\n - Implementation Notes: Technical approach, architecture decisions\n - Testing Strategy: Testing approach, coverage requirements\n - Reference Information: External links, documentation, resources\n - Dependencies: Prerequisites, related tasks, blocking issues\n - Architecture: Design patterns, system integration points\n \n Ordinal Sequencing Best Practices:\n - Start with ordinal 0 for the first section\n - Use increments of 1 for logical ordering\n - Leave gaps (0, 10, 20) when you anticipate inserting sections later\n - Requirements typically come first (ordinal 0)\n - Implementation details in the middle (ordinal 1-5)\n - Testing and validation toward the end (ordinal 6+)\n \n Content Format Selection:\n - MARKDOWN: Default for documentation, requirements, notes (rich formatting)\n - PLAIN_TEXT: Simple text without formatting needs\n - JSON: Structured data, configuration, API specifications\n - CODE: Source code examples, implementation snippets\n \n ## Integration with Workflow\n \n Template Integration: When using templates, they create standard sections automatically.\n Use add_section to supplement template-created sections with project-specific content.\n \n Progressive Detail: Start with high-level sections (Requirements, Architecture) \n and add implementation details as the task progresses.\n \n ## Parameters\n \n \| Parameter \| Type \| Required \| Default \| Description \|\n \|-----------\|------\|----------\|---------\|-------------\|\n \| entityType \| string \| Yes \| - \| Type of entity to attach this section to: \'PROJECT\', \'TASK\', or \'FEATURE\' \|\n \| entityId \| UUID string \| Yes \| - \| ID of the project, task, or feature to add the section to (e.g., \'550e8400-e29b-41d4-a716-446655440000\') \|\n \| title \| string \| Yes \| - \| Section title (e.g., \'Requirements\', \'Implementation Notes\', \'Testing Plan\') \|\n \| usageDescription \| string \| Yes \| - \| Description of how this section should be used by AI models or users \|\n \| content \| string \| Yes \| - \| The actual content of the section in the specified format \|\n \| contentFormat \| string \| No \| "MARKDOWN" \| Format of the content: \'MARKDOWN\', \'PLAIN_TEXT\', \'JSON\', or \'CODE\' \|\n \| ordinal \| integer \| Yes \| - \| Order position (0-based). Lower numbers appear first when ordered. \|\n \| tags \| string \| No \| - \| Comma-separated list of tags for categorization (e.g., \'documentation,frontend,api\') \|\n \n ## Response Format\n \n ### Success Response\n \n ```json\n {\n "success": true,\n "message": "Section added successfully",\n "data": {\n "section": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "entityType": "TASK",\n "entityId": "661f9511-f30c-52e5-b827-557766551111",\n "title": "Implementation Steps",\n "contentFormat": "MARKDOWN",\n "ordinal": 1,\n "createdAt": "2025-05-10T14:30:00Z"\n }\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 provided parameters fail validation\n ```json\n {\n "success": false,\n "message": "Title is required",\n "error": {\n "code": "VALIDATION_ERROR"\n }\n }\n ```\n \n - DATABASE_ERROR (500): When there\'s an issue storing the section in the database\n \n - INTERNAL_ERROR (500): For unexpected system errors during execution\n \n ## Usage Examples\n \n 1. Add a requirements section to a task:\n ```json\n {\n "entityType": "TASK",\n "entityId": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Requirements",\n "usageDescription": "Key requirements that the implementation must satisfy",\n "content": "1. Must support OAuth2 authentication\\\\n2. Should handle token refresh\\\\n3. Needs rate limiting",\n "contentFormat": "MARKDOWN",\n "ordinal": 0,\n "tags": "requirements,security,api"\n }\n ```\n \n 2. Add implementation notes to a feature:\n ```json\n {\n "entityType": "FEATURE",\n "entityId": "661e8511-f30c-41d4-a716-557788990000",\n "title": "Implementation Notes",\n "usageDescription": "Technical details on implementation approach",\n "content": "Use the AuthLib 2.0 library for OAuth implementation...",\n "contentFormat": "MARKDOWN",\n "ordinal": 1,\n "tags": "implementation,technical"\n }\n ```\n \n 3. Add overview documentation to a project:\n ```json\n {\n "entityType": "PROJECT",\n "entityId": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Project Overview",\n "usageDescription": "High-level overview of the project",\n "content": "This project aims to create a scalable infrastructure...",\n "contentFormat": "MARKDOWN",\n "ordinal": 0,\n "tags": "overview,documentation"\n }\n ```\n \n 3. Add structured data as JSON:\n ```json\n {\n "entityType": "FEATURE",\n "entityId": "661e8511-f30c-41d4-a716-557788990000",\n "title": "API Endpoints",\n "usageDescription": "Definition of REST API endpoints",\n "content": "{\\\\"endpoints\\\\": [{\\\\"path\\\\": \\\\"/api/auth\\\\", \\\\"method\\\\": \\\\"POST\\\\"}]}",\n "contentFormat": "JSON",\n "ordinal": 0\n }\n ```\n \n 4. Add code sample:\n ```json\n {\n "entityType": "TASK",\n "entityId": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Authentication Handler",\n "usageDescription": "Code for handling OAuth authentication",\n "content": "fun authenticateUser(credentials: Credentials): Result<User> {\\n // Implementation\\n}",\n "contentFormat": "CODE",\n "ordinal": 2\n }\n ```\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\n \n ## Related Tools\n \n - `get_sections`: Retrieve sections for a task or feature\n - `update_section`: Modify an existing section\n - `delete_section`: Remove a section\n - `bulk_create_sections`: Create multiple sections at once (recommended when adding multiple sections)\n \n ## Efficiency Note\n \n For efficiency and better performance, when you need to add multiple sections to the \n same entity, use the `bulk_create_sections` tool instead. This reduces the number of\n database operations and network calls, resulting in faster execution, especially when\n dealing with multiple sections with shorter content.', 'parameters': {'type': 'object', 'properties': {'content': {'type': 'string', 'description': 'The actual content of the section in the specified format'}, 'contentFormat': {'type': 'string', 'description': "Format of the content: 'MARKDOWN' for formatted text, 'PLAIN_TEXT' for unformatted text, 'JSON' for data, 'CODE' for source code", 'default': 'MARKDOWN', 'enum': ['PLAIN_TEXT', 'MARKDOWN', 'JSON', 'CODE']}, 'entityId': {'type': 'string', 'description': "ID (UUID) of the project, task, or feature to add the section to (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'entityType': {'type': 'string', 'description': "Type of entity to attach this section to: 'PROJECT', 'TASK', or 'FEATURE'", 'enum': ['PROJECT', 'FEATURE', 'TASK', 'TEMPLATE', 'SECTION']}, 'ordinal': {'type': 'integer', 'description': 'Order position (0-based). Lower numbers appear first when ordered.', 'minimum': 0}, 'tags': {'type': 'string', 'description': "Comma-separated list of tags for categorization (e.g., 'documentation,frontend,api')"}, 'title': {'type': 'string', 'description': "Section title (e.g., 'Requirements', 'Implementation Notes', 'Testing Plan')"}, 'usageDescription': {'type': 'string', 'description': 'Description of how this section should be used by AI models or users'}}, 'required': ['entityType', 'entityId', 'title', 'usageDescription', 'content', 'ordinal'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'add_template_section', 'description': 'Add a section to a template.\n \n Templates define a structured documentation pattern with multiple sections.\n This tool adds a section definition to a template, which will be created\n when the template is applied to tasks or features.\n \n Example successful response:\n {\n "success": true,\n "message": "Template section added successfully",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "templateId": "661e8511-f30c-41d4-a716-557788990000",\n "title": "Implementation Steps",\n "usageDescription": "Detailed steps to implement this task",\n "contentSample": "1. First step\\\\n2. Second step\\\\n3. Third step",\n "contentFormat": "markdown",\n "ordinal": 1,\n "isRequired": true,\n "tags": ["implementation", "steps"]\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation\n - RESOURCE_NOT_FOUND: When the template doesn\'t exist\n - DATABASE_ERROR: When there\'s an issue storing the section\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'contentFormat': {'type': 'string', 'description': 'Format of the content', 'default': 'MARKDOWN', 'enum': ['PLAIN_TEXT', 'MARKDOWN', 'JSON', 'CODE']}, 'contentSample': {'type': 'string', 'description': 'Sample content that will be used when creating from the template'}, 'isRequired': {'type': 'boolean', 'description': 'Whether this section is required when applying the template', 'default': False}, 'ordinal': {'type': 'integer', 'description': 'Order position (0-based). Lower numbers appear first when ordered.', 'minimum': 0}, 'tags': {'type': 'string', 'description': 'Comma-separated list of tags for categorization'}, 'templateId': {'type': 'string', 'description': 'The unique ID of the template to add the section to', 'format': 'uuid'}, 'title': {'type': 'string', 'description': "Section title (e.g., 'Requirements', 'Implementation Notes', 'Testing Plan')"}, 'usageDescription': {'type': 'string', 'description': 'Description of how this section should be used by AI models or users'}}, 'required': ['templateId', 'title', 'usageDescription', 'contentSample', 'ordinal'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'apply_template', 'description': 'Apply one or more templates to create sections for a task or feature.\n \n ## Purpose\n Templates provide standardized structure for task and feature documentation.\n This tool applies templates to an entity, creating sections based on template section definitions.\n \n ## Template Application Strategies\n \n Multiple Template Support:\n - Apply multiple templates in single operation using templateIds array\n - Templates applied in array order (later templates\' sections appear after earlier ones)\n - Use single-item array for one template: ["template-uuid"]\n - Use multiple templates for comprehensive coverage: ["uuid1", "uuid2", "uuid3"]\n \n Template Combination Patterns:\n The template system is organized into composable categories:\n \n AI Workflow Instructions (process guidance):\n - Local Git Branching Workflow, GitHub PR Workflow\n - Task Implementation Workflow, Bug Investigation Workflow\n \n Documentation Properties (information capture):\n - Technical Approach, Requirements Specification, Context & Background\n \n Process & Quality (standards and completion):\n - Testing Strategy, Definition of Done\n \n Recommended Combinations:\n - Development Task: Technical Approach + Task Implementation Workflow + Testing Strategy\n - Bug Fix: Bug Investigation Workflow + Technical Approach + Definition of Done\n - Feature Planning: Requirements Specification + Context & Background + Testing Strategy\n - Complex Implementation: Technical Approach + Local Git Branching + GitHub PR + Definition of Done\n \n ## Context Efficiency Techniques\n \n ALWAYS PREFER direct creation with templates over separate operations:\n ```\n // EFFICIENT\n create_task(title: "X", templateIds: ["Y"])\n \n // LESS EFFICIENT \n id = create_task(title: "X")\n apply_template(entityId: id, templateIds: ["Y"])\n ```\n \n Multiple Templates in One Call:\n ```\n // EFFICIENT\n apply_template(entityId: id, templateIds: ["A", "B", "C"])\n \n // LESS EFFICIENT\n apply_template(entityId: id, templateIds: ["A"])\n apply_template(entityId: id, templateIds: ["B"]) \n apply_template(entityId: id, templateIds: ["C"])\n ```\n \n Template Sequence Optimization:\n 1. Start with Context: Context & Background, Requirements Specification\n 2. Add Technical Detail: Technical Approach for implementation guidance \n 3. Include Process Guidance: Task Implementation, Bug Investigation workflows\n 4. Add Git Workflow: Local Git Branching, GitHub PR workflows\n 5. Ensure Quality: Testing Strategy, Definition of Done\n \n You can apply one or more templates by providing a templateIds array parameter.\n Use a single-item array for applying just one template.\n \n Example successful response for a single template:\n {\n "success": true,\n "message": "Template applied successfully, created 3 sections",\n "data": {\n "templateId": "550e8400-e29b-41d4-a716-446655440000",\n "entityType": "TASK",\n "entityId": "661e8511-f30c-41d4-a716-557788990000",\n "sectionsCreated": 3,\n "sections": [\n {\n "id": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Requirements",\n "ordinal": 0\n },\n {\n "id": "882f9733-h52e-63f6-c938-779900212222",\n "title": "Implementation Notes",\n "ordinal": 1\n },\n {\n "id": "993f0844-i63f-74g7-d049-8800a1323333",\n "title": "Testing Strategy",\n "ordinal": 2\n }\n ]\n }\n }\n \n Example successful response for multiple templates:\n {\n "success": true,\n "message": "Applied 2 templates successfully, created 5 sections",\n "data": {\n "entityType": "TASK",\n "entityId": "661e8511-f30c-41d4-a716-557788990000",\n "totalSectionsCreated": 5,\n "appliedTemplates": [\n {\n "templateId": "550e8400-e29b-41d4-a716-446655440000",\n "sectionsCreated": 3,\n "sections": [\n {\n "id": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Requirements",\n "ordinal": 0\n },\n {\n "id": "882f9733-h52e-63f6-c938-779900212222",\n "title": "Implementation Notes",\n "ordinal": 1\n },\n {\n "id": "993f0844-i63f-74g7-d049-8800a1323333",\n "title": "Testing Strategy",\n "ordinal": 2\n }\n ]\n },\n {\n "templateId": "661e8511-f30c-41d4-a716-557788990000",\n "sectionsCreated": 2,\n "sections": [\n {\n "id": "772f9622-g41d-52e5-b827-668899101112",\n "title": "Design Documentation",\n "ordinal": 3\n },\n {\n "id": "882f9733-h52e-63f6-c938-779900212223",\n "title": "Related Tasks",\n "ordinal": 4\n }\n ]\n }\n ]\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation\n - RESOURCE_NOT_FOUND: When the template or entity doesn\'t exist\n - DATABASE_ERROR: When there\'s an issue applying the template\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'entityId': {'type': 'string', 'description': 'ID of the entity to apply the template to', 'format': 'uuid'}, 'entityType': {'type': 'string', 'description': 'Type of entity (TASK or FEATURE)', 'enum': ['TASK', 'FEATURE']}, 'templateIds': {'type': 'array', 'description': 'List of template IDs to apply. Use a single-item array for applying just one template.', 'items': {'type': 'string', 'format': 'uuid'}}}, 'required': ['entityType', 'entityId', 'templateIds'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'bulk_create_sections', 'description': 'Creates multiple sections in a single operation.\n \n ## Purpose\n \n This tool efficiently creates multiple sections for tasks, features, or projects in a single operation.\n PREFERRED over multiple `add_section` calls for efficiency and performance.\n \n ## When to Use bulk_create_sections\n \n ALWAYS PREFER for:\n - Creating initial section sets for new tasks/features (3+ sections)\n - Adding template-like section structures\n - Sections with shorter content (< 500 characters each)\n - Any scenario requiring multiple sections for the same entity\n \n Performance Benefits:\n - Single database transaction (atomic operation)\n - Reduced network overhead (one API call vs multiple)\n - Faster execution for multiple sections\n - Better error handling (all succeed or fail together)\n \n ## Common Section Creation Patterns\n \n Standard Task Documentation Set:\n ```json\n {\n "sections": [\n {\n "entityType": "TASK",\n "entityId": "task-uuid",\n "title": "Requirements",\n "usageDescription": "Key requirements and acceptance criteria",\n "content": "[List specific requirements and success criteria]",\n "ordinal": 0,\n "tags": "requirements,core"\n },\n {\n "entityType": "TASK",\n "entityId": "task-uuid",\n "title": "Technical Approach",\n "usageDescription": "Implementation strategy and architecture",\n "content": "[Describe technical approach and key decisions]",\n "ordinal": 1,\n "tags": "technical,architecture"\n },\n {\n "entityType": "TASK",\n "entityId": "task-uuid",\n "title": "Testing Strategy",\n "usageDescription": "Testing approach and coverage requirements",\n "content": "[Define testing strategy and success criteria]",\n "ordinal": 2,\n "tags": "testing,quality"\n }\n ]\n }\n ```\n \n Feature Planning Documentation:\n ```json\n {\n "sections": [\n {\n "entityType": "FEATURE",\n "entityId": "feature-uuid",\n "title": "Business Context",\n "usageDescription": "Business value and user impact",\n "content": "[Explain business need and user benefits]",\n "ordinal": 0,\n "tags": "business,context"\n },\n {\n "entityType": "FEATURE",\n "entityId": "feature-uuid",\n "title": "Feature Specification",\n "usageDescription": "Detailed feature requirements and behavior",\n "content": "[Define feature scope and detailed requirements]",\n "ordinal": 1,\n "tags": "requirements,specification"\n }\n ]\n }\n ```\n \n ## Section Organization Best Practices\n \n Ordinal Sequencing:\n - Start with ordinal 0 for the first section\n - Use increments of 1 for tightly related sequences\n - Leave gaps (0, 10, 20) when you might insert sections later\n - Order logically: Context → Requirements → Implementation → Testing\n \n Content Format Selection:\n - MARKDOWN: Default for rich text, documentation, requirements\n - PLAIN_TEXT: Simple text without formatting needs\n - JSON: Structured data, API specs, configuration\n - CODE: Implementation examples, code snippets\n \n Tagging Strategy:\n - Use consistent tags across similar section types\n - Include functional area: "requirements", "testing", "architecture"\n - Add technical context: "api", "database", "frontend", "security"\n - Mark importance: "core", "optional", "critical"\n \n ## Integration with Templates\n \n Templates vs Manual Sections:\n - Templates provide standardized section structures automatically\n - Use bulk_create_sections to supplement template sections with project-specific content\n - Templates handle common patterns; bulk_create_sections handles custom needs\n \n Post-Template Enhancement:\n After applying templates, use bulk_create_sections to add:\n - Project-specific context sections\n - Additional technical details\n - Custom workflow or process sections\n - Domain-specific requirements or constraints\n \n ## Parameters\n \n \| Parameter \| Type \| Required \| Default \| Description \|\n \|-----------\|------\|----------\|---------\|-------------\|\n \| sections \| array \| Yes \| - \| Array of section objects to create \|\n \n Each section object in the array must include:\n \n \| Field \| Type \| Required \| Default \| Description \|\n \|-------\|------\|----------\|---------\|-------------\|\n \| entityType \| string \| Yes \| - \| Type of entity: \'PROJECT\', \'TASK\', or \'FEATURE\' \|\n \| entityId \| UUID string \| Yes \| - \| ID of the project, task, or feature to add the section to \|\n \| title \| string \| Yes \| - \| Section title (e.g., \'Requirements\', \'Implementation Notes\') \|\n \| usageDescription \| string \| Yes \| - \| Description of how this section should be used \|\n \| content \| string \| Yes \| - \| The actual content of the section \|\n \| contentFormat \| string \| No \| "MARKDOWN" \| Format of the content: \'MARKDOWN\', \'PLAIN_TEXT\', \'JSON\', or \'CODE\' \|\n \| ordinal \| integer \| Yes \| - \| Order position (0-based). Lower numbers appear first. \|\n \| tags \| string \| No \| - \| Comma-separated list of tags for categorization \|\n \n ## Response Format\n \n ### Success Response (All Sections Created)\n \n ```json\n {\n "success": true,\n "message": "3 sections created successfully",\n "data": {\n "items": [\n {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "entityType": "task",\n "entityId": "661f9511-f30c-52e5-b827-557766551111",\n "title": "Requirements",\n "contentFormat": "markdown",\n "ordinal": 0,\n "createdAt": "2025-05-10T14:30:00Z"\n }\n ],\n "count": 3,\n "failed": 0\n }\n }\n ```\n \n ## Error Responses\n \n - VALIDATION_ERROR (400): When the input doesn\'t match the expected format or values are invalid\n - OPERATION_FAILED (500): When all sections fail to create\n - RESOURCE_NOT_FOUND (404): When an entity doesn\'t exist\n \n ## Usage Examples\n \n 1. Create multiple sections for a task:\n ```json\n {\n "sections": [\n {\n "entityType": "TASK",\n "entityId": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Requirements",\n "usageDescription": "Key requirements for implementation",\n "content": "1. Must support user authentication\\n2. Should integrate with existing systems",\n "contentFormat": "MARKDOWN",\n "ordinal": 0,\n "tags": "requirements,core"\n },\n {\n "entityType": "TASK",\n "entityId": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Technical Approach",\n "usageDescription": "Implementation strategy and technical details",\n "content": "We\'ll use Spring Security for authentication and implement REST endpoints...",\n "contentFormat": "MARKDOWN",\n "ordinal": 1,\n "tags": "technical,implementation"\n },\n {\n "entityType": "TASK",\n "entityId": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Testing Strategy",\n "usageDescription": "Test approach and coverage requirements",\n "content": "Ensure 80% unit test coverage and implement integration tests for key flows",\n "contentFormat": "MARKDOWN",\n "ordinal": 2,\n "tags": "testing,quality"\n }\n ]\n }\n ```\n \n 2. Create multiple sections for a project:\n ```json\n {\n "sections": [\n {\n "entityType": "PROJECT",\n "entityId": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Project Overview",\n "usageDescription": "High-level description of the project",\n "content": "This project aims to create a scalable infrastructure...",\n "contentFormat": "MARKDOWN",\n "ordinal": 0,\n "tags": "overview,documentation"\n },\n {\n "entityType": "PROJECT",\n "entityId": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Project Architecture",\n "usageDescription": "Technical architecture details",\n "content": "The project uses a modular architecture with the following components...",\n "contentFormat": "MARKDOWN",\n "ordinal": 1,\n "tags": "architecture,technical"\n }\n ]\n }\n ```\n \n ## Performance Benefits\n \n Using `bulk_create_sections` instead of multiple calls to `add_section` offers significant \n advantages:\n \n 1. Reduced network overhead: Only one API call instead of multiple calls\n 2. Improved transaction efficiency: Database operations are batched\n 3. Faster execution: Creating multiple sections in parallel\n 4. Atomic operations: All sections succeed or useful error information is provided\n \n ## Common Section Combinations\n \n Typical section combinations for tasks include:\n \n 1. Requirements + Implementation Approach + Testing Strategy\n 2. Problem Statement + Solution Design + Acceptance Criteria\n 3. Context + Technical Details + References', 'parameters': {'type': 'object', 'properties': {'sections': {'type': 'array', 'description': 'Array of sections to create', 'items': {'type': 'object', 'required': ['entityType', 'entityId', 'title', 'usageDescription', 'content', 'ordinal'], 'properties': {'content': {'type': 'string', 'description': 'Section content'}, 'contentFormat': {'type': 'string', 'description': 'Format of the content', 'default': 'MARKDOWN', 'enum': ['PLAIN_TEXT', 'MARKDOWN', 'JSON', 'CODE']}, 'entityId': {'type': 'string', 'description': 'ID of the project, task, or feature', 'format': 'uuid'}, 'entityType': {'type': 'string', 'description': 'Type of entity (PROJECT, TASK, or FEATURE)', 'enum': ['PROJECT', 'FEATURE', 'TASK', 'TEMPLATE', 'SECTION']}, 'ordinal': {'type': 'integer', 'description': 'Order position (0-based)', 'minimum': 0}, 'tags': {'type': 'string', 'description': 'Comma-separated list of tags'}, 'title': {'type': 'string', 'description': 'Section title'}, 'usageDescription': {'type': 'string', 'description': 'Guidance for LLMs on how to use this content'}}}}}, 'required': ['sections'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'bulk_delete_sections', 'description': 'Deletes multiple sections in a single operation', 'parameters': {'type': 'object', 'properties': {'hardDelete': {'type': 'boolean', 'description': 'Whether to permanently delete the sections (true) or soft delete them (false)', 'default': False}, 'ids': {'type': 'array', 'description': 'Array of section IDs to delete', 'items': {'type': 'string', 'description': 'Section ID', 'format': 'uuid'}}}, 'required': ['ids'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'bulk_update_sections', 'description': 'Updates multiple sections in a single operation', 'parameters': {'type': 'object', 'properties': {'sections': {'type': 'array', 'description': 'Array of sections to update', 'items': {'type': 'object', 'required': ['id'], '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': ['sections'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'create_dependency', 'description': 'Creates a new task dependency with validation for task existence, cycle detection, and duplicate prevention.\n \n Dependencies represent relationships between tasks that can affect execution planning and workflow management.\n This tool ensures data integrity by validating all aspects before creation.\n \n Example successful response:\n {\n "success": true,\n "message": "Dependency created successfully",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "fromTaskId": "661e8511-f30c-41d4-a716-557788990000",\n "toTaskId": "772f9622-g41d-52e5-b827-668899101111",\n "type": "BLOCKS",\n "createdAt": "2025-05-10T14:30:00Z"\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation\n - RESOURCE_NOT_FOUND: When one or both tasks don\'t exist\n - CONFLICT_ERROR: When the dependency would create a cycle or already exists\n - DATABASE_ERROR: When there\'s an issue storing the dependency\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'fromTaskId': {'type': 'string', 'description': 'ID of the source task (the task that creates the dependency)', 'format': 'uuid'}, 'toTaskId': {'type': 'string', 'description': 'ID of the target task (the task that is affected by the dependency)', 'format': 'uuid'}, 'type': {'type': 'string', 'description': "Type of dependency: 'BLOCKS' (source blocks target), 'IS_BLOCKED_BY' (source is blocked by target), or 'RELATES_TO' (general relationship)", 'default': 'BLOCKS', 'enum': ['BLOCKS', 'IS_BLOCKED_BY', 'RELATES_TO']}}, 'required': ['fromTaskId', 'toTaskId'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'create_feature', 'description': 'Create a new feature with required and optional fields.\n \n ## Purpose\n Features provide higher-level organization for related tasks, representing coherent\n functionality or project components. They bridge the gap between individual tasks\n and overall project goals.\n \n ## Feature vs Task Decision Guide\n \n Create a Feature when:\n - Work involves multiple related tasks (3+ tasks)\n - Functionality represents a user-facing feature or system component\n - Work has distinct phases (planning, development, testing, deployment)\n - Multiple developers or skill sets are involved\n - Work has independent business value or can be delivered as a unit\n \n Use Direct Tasks when:\n - Work is a single, focused implementation\n - Maintenance, bug fixes, or small enhancements\n - Infrastructure or tooling improvements\n - Work doesn\'t logically group with other tasks\n \n ## Template Integration Strategy\n \n RECOMMENDED: Apply templates at creation for consistent documentation structure.\n \n Feature-Level Templates (use `list_templates` with targetEntityType="FEATURE"):\n - Context & Background: Project context and business requirements\n - Requirements Specification: Detailed functional and non-functional requirements\n - Technical Approach: High-level architecture and technical strategy\n \n Template Combinations for Features:\n - Planning Phase: Context & Background + Requirements Specification\n - Technical Phase: Requirements Specification + Technical Approach\n - Comprehensive: All three templates for complex features\n \n ## Feature Lifecycle Management\n \n Status Progression:\n 1. `planning` - Requirements gathering, design, scope definition\n 2. `in-development` - Active implementation across multiple tasks\n 3. `completed` - All associated tasks completed, feature delivered\n 4. `archived` - Feature complete and no longer under active development\n \n Priority Guidelines:\n - `high`: Core functionality, user-facing features, business critical\n - `medium`: Important enhancements, internal tools, performance improvements\n - `low`: Nice-to-have features, experimental functionality\n \n ## Organizing Tasks Under Features\n \n After creating a feature, use the featureId in `create_task` to associate tasks:\n ```json\n {\n "title": "Implement OAuth Login",\n "summary": "Create OAuth authentication endpoints",\n "featureId": "feature-uuid-here",\n "templateIds": ["task-template-uuid"]\n }\n ```\n \n Task Organization Patterns:\n - Frontend + Backend: Separate tasks for UI and API implementation\n - By Component: Database, API, UI, Tests as separate tasks\n - By Phase: Research, Implementation, Testing, Documentation\n - By Complexity: Break large features into manageable task chunks\n \n ## Integration with Project Hierarchy\n \n Project → Features → Tasks hierarchy:\n - Use projectId to associate feature with a project\n - Features group related functionality within a project\n - Tasks represent specific implementation work within features\n \n ## Best Practices\n \n Naming Conventions:\n - Use noun phrases describing functionality: "User Authentication", "Payment Processing"\n - Avoid implementation details in names: "OAuth Integration" not "Implement OAuth"\n - Be specific enough to distinguish from other features\n \n Summary Guidelines:\n - Include business value and user impact\n - Mention key technical components or integrations\n - Define success criteria or completion indicators\n - Keep scope clear and bounded\n \n Tagging Strategy:\n - Include functional area: "authentication", "payments", "reporting"\n - Add technical stack: "frontend", "backend", "database", "api"\n - Mark business importance: "core", "enhancement", "experimental"\n - Include user-facing impact: "user-experience", "admin-tools", "internal"\n \n Example successful response:\n {\n "success": true,\n "message": "Feature created successfully with 2 template(s) applied, creating 5 section(s)",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "name": "User Authentication System",\n "summary": "Complete user authentication system with OAuth 2.0, JWT tokens, and social login integration. Provides secure user registration, login, password reset, and session management.",\n "status": "planning",\n "priority": "high",\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T14:30:00Z",\n "tags": ["core", "authentication", "security", "user-experience", "oauth"],\n "appliedTemplates": [\n {\n "templateId": "context-background-uuid",\n "sectionsCreated": 2\n },\n {\n "templateId": "requirements-spec-uuid",\n "sectionsCreated": 3\n }\n ]\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation (empty name/summary)\n - RESOURCE_NOT_FOUND: When specified projectId or templateIds don\'t exist\n - DATABASE_ERROR: When there\'s an issue storing the feature or applying templates\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'name': {'type': 'string', 'description': "Required feature name (e.g., 'User Authentication', 'Data Export')"}, 'priority': {'type': 'string', 'description': "Priority level. Valid values: 'high', 'medium', 'low'", 'default': 'medium', 'enum': ['high', 'medium', 'low']}, 'projectId': {'type': 'string', 'description': "Optional UUID of the project this feature belongs to (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'status': {'type': 'string', 'description': "Feature status. Valid values: 'planning', 'in-development', 'completed', 'archived'", 'default': 'planning', 'enum': ['planning', 'in-development', 'completed', 'archived']}, 'summary': {'type': 'string', 'description': 'Required feature summary describing its purpose and scope'}, 'tags': {'type': 'string', 'description': "Comma-separated list of tags for categorization (e.g., 'frontend,ui,critical')"}, 'templateIds': {'type': 'array', 'description': 'List of template IDs to apply. Use a single-item array for applying just one template.', 'items': {'type': 'string', 'format': 'uuid'}}}, 'required': ['name', 'summary'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'create_project', 'description': 'Implement the CreateProjectTool MCP tool for creating new projects. Define parameter schema and validation for all required and optional fields (name, summary, status, tags). Implement tool execution logic to create and persist project entities.\n \n This tool creates a new Project entity in the MCP Task Orchestrator system. Projects are top-level organizational containers that can group related features and tasks together. Each project requires a name and summary, and can optionally include status information and tags for categorization.\n \n Projects provide a higher level of organization above features, allowing you to manage work across multiple features and their related tasks.\n \n Example successful response:\n {\n "success": true,\n "message": "Project created successfully",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "name": "Mobile App Redesign",\n "summary": "Complete redesign of the mobile application with improved UI/UX",\n "status": "planning",\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T14:30:00Z",\n "tags": ["mobile", "ui", "2025-roadmap"]\n },\n "error": null,\n "metadata": {\n "timestamp": "2025-05-10T14:30:00Z"\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation\n - DATABASE_ERROR: When there\'s an issue storing the project\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'name': {'type': 'string', 'description': "Project name (e.g., 'Mobile App Redesign', 'Backend API')"}, 'status': {'type': 'string', 'description': "Project status. Valid values: 'planning', 'in-development', 'completed', 'archived'", 'default': 'planning', 'enum': ['planning', 'in-development', 'completed', 'archived']}, 'summary': {'type': 'string', 'description': 'Project description explaining its purpose and scope'}, 'tags': {'type': 'string', 'description': "Comma-separated list of tags for categorization (e.g., 'frontend,mobile,2025-roadmap')"}}, 'required': ['name', 'summary'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'create_task', 'description': 'Creates a new task with the specified properties.\n \n ## Purpose\n Tasks are the primary work items in the system and can be organized into Features.\n Each task has basic metadata (title, status, etc.) and can have Sections for detailed content.\n \n ## Template Integration\n RECOMMENDED: Apply templates at creation time using templateIds parameter for consistent\n documentation structure. Use `list_templates` first to find appropriate templates.\n \n Template application creates standardized sections automatically:\n - Use single-item array for one template: ["template-uuid"]\n - Use multiple templates for comprehensive coverage: ["uuid1", "uuid2"]\n - Templates are applied in order, with later templates\' sections appearing after earlier ones\n \n ## Best Practices\n - Use descriptive titles that clearly indicate the work to be done\n - Write comprehensive summaries with acceptance criteria when helpful\n - Set appropriate complexity ratings (1=trivial, 10=highly complex)\n - Use consistent tagging conventions (e.g., "task-type-feature", "task-type-bug")\n - Associate with features when the task is part of larger functionality\n - Apply templates that match the work type (implementation, testing, documentation)\n \n ## Entity Relationships\n - Tasks can belong to Features (use featureId to establish relationship)\n - Tasks can belong to Projects (use projectId for top-level organization)\n - Use dependencies to link related tasks (see create_dependency tool)\n \n ## Workflow Integration\n Tasks integrate with the complete project management workflow:\n 1. Start with get_overview to understand current work\n 2. Create task with appropriate templates and metadata\n 3. Use add_section or bulk_create_sections for additional content\n 4. Update status as work progresses (pending → in_progress → completed)\n 5. Create dependencies between related tasks\n \n Example successful response:\n {\n "success": true,\n "message": "Task created successfully with 2 template(s) applied, creating 6 section(s)",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Implement OAuth Authentication API",\n "summary": "Create secure API endpoints for OAuth 2.0 authentication with JWT tokens",\n "status": "pending",\n "priority": "high",\n "complexity": 8,\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T14:30:00Z",\n "featureId": "661e8511-f30c-41d4-a716-557788990000",\n "tags": ["task-type-feature", "oauth", "authentication", "api", "security"],\n "appliedTemplates": [\n {\n "templateId": "technical-approach-uuid",\n "sectionsCreated": 3\n },\n {\n "templateId": "implementation-workflow-uuid",\n "sectionsCreated": 3\n }\n ]\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation (empty title/summary, invalid UUIDs)\n - RESOURCE_NOT_FOUND: When specified featureId, projectId, or templateIds don\'t exist\n - DATABASE_ERROR: When there\'s an issue storing the task or applying templates\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'complexity': {'type': 'integer', 'description': 'Task complexity on a scale from 1-10 (1=simplest, 10=most complex)', 'default': 5, 'minimum': 1, 'maximum': 10}, 'featureId': {'type': 'string', 'description': "Optional UUID of the feature this task belongs to (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'priority': {'type': 'string', 'description': "Task priority. Valid values: 'high', 'medium', 'low'", 'default': 'medium', 'enum': ['high', 'medium', 'low']}, 'projectId': {'type': 'string', 'description': "Optional UUID of the project this task belongs to (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'status': {'type': 'string', 'description': "Task status. Valid values: 'pending', 'in-progress', 'completed', 'cancelled', 'deferred'", 'default': 'pending', 'enum': ['pending', 'in_progress', 'completed', 'cancelled', 'deferred']}, 'summary': {'type': 'string', 'description': 'Brief summary of the task content (required for task creation)'}, 'tags': {'type': 'string', 'description': "Comma-separated list of tags for categorization (e.g., 'api,backend,urgent')"}, 'templateIds': {'type': 'array', 'description': 'List of template IDs to apply. Use a single-item array for applying just one template.', 'items': {'type': 'string', 'format': 'uuid'}}, 'title': {'type': 'string', 'description': 'The title of the task (required)'}}, 'required': ['title', 'summary'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'create_template', 'description': 'Creates a new template with required and optional fields.\n \n Templates provide reusable patterns for structuring task and feature documentation.\n Each template has metadata and can contain multiple section definitions.\n \n Example successful response:\n {\n "success": true,\n "message": "Template created successfully",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "name": "User Authentication",\n "description": "Implement secure user authentication system",\n "targetEntityType": "TASK",\n "isBuiltIn": false,\n "isProtected": false,\n "isEnabled": true,\n "createdBy": "Claude",\n "tags": ["security", "login", "user-management"],\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T14:30:00Z"\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation\n - CONFLICT_ERROR: When a template with the same name already exists\n - DATABASE_ERROR: When there\'s an issue storing the template\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'createdBy': {'type': 'string', 'description': 'Optional creator identifier (default: null)'}, 'description': {'type': 'string', 'description': 'Required template description explaining its purpose and scope'}, 'isBuiltIn': {'type': 'boolean', 'description': 'Whether this is a built-in template (default: false)', 'default': False}, 'isEnabled': {'type': 'boolean', 'description': 'Whether this template is enabled for use (default: true)', 'default': True}, 'isProtected': {'type': 'boolean', 'description': 'Whether this template is protected from modification (default: false)', 'default': False}, 'name': {'type': 'string', 'description': "Required template name (e.g., 'User Authentication', 'Data Export')"}, 'tags': {'type': 'string', 'description': "Comma-separated list of tags for categorization (e.g., 'frontend,ui,critical')"}, 'targetEntityType': {'type': 'string', 'description': "Type of entity this template is for: 'TASK' or 'FEATURE'", 'enum': ['TASK', 'FEATURE']}}, 'required': ['name', 'description', 'targetEntityType'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'delete_dependency', 'description': 'Deletes task dependencies by dependency ID or by task relationship criteria.\n \n This tool provides flexible dependency deletion capabilities. You can delete dependencies:\n - By specific dependency ID (most precise)\n - By task relationship (fromTaskId and toTaskId with optional type filter)\n - All dependencies for a specific task (using deleteAll parameter)\n \n Example successful response:\n {\n "success": true,\n "message": "Dependency deleted successfully",\n "data": {\n "deletedCount": 1,\n "deletedDependencies": [\n {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "fromTaskId": "661e8511-f30c-41d4-a716-557788990000",\n "toTaskId": "772f9622-g41d-52e5-b827-668899101111",\n "type": "BLOCKS"\n }\n ]\n }\n }\n \n Common error responses:\n - RESOURCE_NOT_FOUND: When the specified dependency doesn\'t exist\n - VALIDATION_ERROR: When provided parameters fail validation\n - DATABASE_ERROR: When there\'s an issue deleting the dependency\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'deleteAll': {'type': 'boolean', 'description': 'When used with fromTaskId OR toTaskId (not both), deletes all dependencies for that task', 'default': False}, 'fromTaskId': {'type': 'string', 'description': 'ID of the source task (used with toTaskId for relationship-based deletion)', 'format': 'uuid'}, 'id': {'type': 'string', 'description': 'ID of the specific dependency to delete (mutually exclusive with task relationship parameters)', 'format': 'uuid'}, 'toTaskId': {'type': 'string', 'description': 'ID of the target task (used with fromTaskId for relationship-based deletion)', 'format': 'uuid'}, 'type': {'type': 'string', 'description': 'Filter by dependency type when using task relationship deletion (optional)', 'enum': ['BLOCKS', 'IS_BLOCKED_BY', 'RELATES_TO']}}, 'required': [], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'delete_feature', 'description': 'Remove a feature and its associated tasks', 'parameters': {'type': 'object', 'properties': {'cascade': {'type': 'boolean', 'description': 'Whether to delete tasks associated with this feature', 'default': False}, 'force': {'type': 'boolean', 'description': 'Whether to force deletion even with active tasks', 'default': False}, 'hardDelete': {'type': 'boolean', 'description': 'Whether to completely remove the feature from the database', 'default': False}, 'id': {'type': 'string', 'description': 'The unique ID of the feature to delete'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'delete_project', 'description': 'Remove a project and its associated features/tasks', 'parameters': {'type': 'object', 'properties': {'cascade': {'type': 'boolean', 'description': 'Whether to delete all features and tasks associated with this project', 'default': False}, 'force': {'type': 'boolean', 'description': 'Whether to force deletion even with active features or tasks', 'default': False}, 'hardDelete': {'type': 'boolean', 'description': 'Whether to permanently remove the project from the database', 'default': False}, 'id': {'type': 'string', 'description': 'The unique ID of the project to delete'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'delete_section', 'description': 'Deletes a section by its ID', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID of the section to delete', 'format': 'uuid'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'delete_task', 'description': 'Deletes a task by its ID', 'parameters': {'type': 'object', 'properties': {'cascade': {'type': 'boolean', 'description': 'Whether to also delete subtasks', 'default': False}, 'deleteSections': {'type': 'boolean', 'description': 'Whether to also delete associated sections', 'default': True}, 'force': {'type': 'boolean', 'description': 'Whether to delete even if other tasks depend on this one. When true, breaks dependency chains and deletes all associated dependencies.', 'default': False}, 'hardDelete': {'type': 'boolean', 'description': 'Whether to permanently delete the task (true) or soft delete it (false)', 'default': False}, 'id': {'type': 'string', 'description': 'The unique ID of the task to delete', 'format': 'uuid'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'delete_template', 'description': 'Deletes a user-created template. Built-in templates cannot be deleted.\n \n Parameters:\n - id (required): UUID of the template to delete\n - force (optional): Boolean flag to override protection, defaults to false\n \n Validation Rules:\n - Template must exist\n - Built-in templates cannot be deleted\n - If a user attempts to delete a built-in template, they will get back an error message\n instructing them to use \'disable_template\' instead\n \n Example:\n ```json\n {\n "id": "550e8400-e29b-41d4-a716-446655440000"\n }\n ```', 'parameters': {'type': 'object', 'properties': {'force': {'type': 'boolean', 'description': 'Whether to override protection (use with caution)', 'default': False}, 'id': {'type': 'string', 'description': 'The unique ID of the template to delete', 'format': 'uuid'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'disable_template', 'description': 'Disables a template including system templates. Disabled templates are not available for use.\n \n Parameters:\n - id (required): UUID of the template to disable\n \n Validation Rules:\n - Template must exist\n \n Example:\n ```json\n {\n "id": "550e8400-e29b-41d4-a716-446655440000"\n }\n ```', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID of the template to disable', 'format': 'uuid'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}
task-orchestrator	other	{'type': 'function', 'name': 'enable_template', 'description': 'Enables a previously disabled template, making it available for use again.\n \n Parameters:\n - id (required): UUID of the template to enable\n \n Validation Rules:\n - Template must exist\n \n Example:\n ```json\n {\n "id": "550e8400-e29b-41d4-a716-446655440000"\n }\n ```', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID of the template to enable', 'format': 'uuid'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}

schogini-mcp-image-border

other

{'type': 'function', 'name': 'add-two-numbers', 'description': 'A simple tool to add two numbers.', 'parameters': {'type': 'object', 'properties': {'num1': {'type': 'string', 'description': 'First number to add'}, 'num2': {'type': 'string', 'description': 'Second number to add'}}, 'required': ['num1', 'num2'], 'additionalProperties': False}, 'strict': True}

schogini-mcp-image-border

other

{'type': 'function', 'name': 'image-border', 'description': 'Add a colored border to an image from a URL', 'parameters': {'type': 'object', 'properties': {'border_color': {'type': 'string', 'description': 'e.g., black, red, #FF0000'}, 'border_thickness': {'type': 'integer', 'minimum': 0}, 'image_url': {'type': 'string', 'description': 'Public image URL'}}, 'required': ['image_url', 'border_thickness', 'border_color'], 'additionalProperties': False}, 'strict': True}

schogini-mcp-image-border

other

{'type': 'function', 'name': 'image-meta', 'description': 'Get image metadata from a public image URL. Returns width, height, file size in bytes, image mode (e.g., RGB), and image format (e.g., PNG, JPEG).', 'parameters': {'type': 'object', 'properties': {'image_url': {'type': 'string', 'description': 'The public URL of the image.'}}, 'required': ['image_url'], 'additionalProperties': False}, 'strict': True}

scrapegraph

other

{'type': 'function', 'name': 'markdownify', 'description': 'Convert a webpage into clean, formatted markdown.\n\n Args:\n website_url: URL of the webpage to convert\n\n Returns:\n Dictionary containing the markdown result', 'parameters': {'type': 'object', 'properties': {'website_url': {'type': 'string', 'title': 'Website Url'}}, 'required': ['website_url'], 'additionalProperties': False}, 'strict': True}

scrapegraph

other

{'type': 'function', 'name': 'searchscraper', 'description': 'Perform AI-powered web searches with structured results.\n\n Args:\n user_prompt: Search query or instructions\n num_results: Number of websites to search (optional, default: 3 websites = 30 credits)\n number_of_scrolls: Number of infinite scrolls to perform on each website (optional)\n\n Returns:\n Dictionary containing search results and reference URLs', 'parameters': {'type': 'object', 'properties': {'num_results': {'type': 'integer', 'title': 'Num Results', 'default': None}, 'number_of_scrolls': {'type': 'integer', 'title': 'Number Of Scrolls', 'default': None}, 'user_prompt': {'type': 'string', 'title': 'User Prompt'}}, 'required': ['user_prompt'], 'additionalProperties': False}, 'strict': True}

scrapegraph

other

{'type': 'function', 'name': 'smartcrawler_fetch_results', 'description': 'Fetch the results of a SmartCrawler operation.\n\n Args:\n request_id: The request ID returned by smartcrawler_initiate\n\n Returns:\n Dictionary containing the crawled data (structured extraction or markdown)\n and metadata about processed pages', 'parameters': {'type': 'object', 'properties': {'request_id': {'type': 'string', 'title': 'Request Id'}}, 'required': ['request_id'], 'additionalProperties': False}, 'strict': True}

scrapegraph

other

{'type': 'function', 'name': 'smartcrawler_initiate', 'description': 'Initiate a SmartCrawler request for intelligent multi-page web crawling.\n \n SmartCrawler supports two modes:\n - AI Extraction Mode (10 credits per page): Extracts structured data based on your prompt\n - Markdown Conversion Mode (2 credits per page): Converts pages to clean markdown\n\n Args:\n url: Starting URL to crawl\n prompt: AI prompt for data extraction (required for AI mode)\n extraction_mode: "ai" for AI extraction or "markdown" for markdown conversion (default: "ai")\n depth: Maximum link traversal depth (optional)\n max_pages: Maximum number of pages to crawl (optional)\n same_domain_only: Whether to crawl only within the same domain (optional)\n\n Returns:\n Dictionary containing the request ID for async processing', 'parameters': {'type': 'object', 'properties': {'depth': {'type': 'integer', 'title': 'Depth', 'default': None}, 'extraction_mode': {'type': 'string', 'title': 'Extraction Mode', 'default': 'ai'}, 'max_pages': {'type': 'integer', 'title': 'Max Pages', 'default': None}, 'prompt': {'type': 'string', 'title': 'Prompt', 'default': None}, 'same_domain_only': {'type': 'boolean', 'title': 'Same Domain Only', 'default': None}, 'url': {'type': 'string', 'title': 'Url'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}

scrapegraph

other

{'type': 'function', 'name': 'smartscraper', 'description': 'Extract structured data from a webpage using AI.\n\n Args:\n user_prompt: Instructions for what data to extract\n website_url: URL of the webpage to scrape\n number_of_scrolls: Number of infinite scrolls to perform (optional)\n markdown_only: Whether to return only markdown content without AI processing (optional)\n\n Returns:\n Dictionary containing the extracted data or markdown content', 'parameters': {'type': 'object', 'properties': {'markdown_only': {'type': 'boolean', 'title': 'Markdown Only', 'default': None}, 'number_of_scrolls': {'type': 'integer', 'title': 'Number Of Scrolls', 'default': None}, 'user_prompt': {'type': 'string', 'title': 'User Prompt'}, 'website_url': {'type': 'string', 'title': 'Website Url'}}, 'required': ['user_prompt', 'website_url'], 'additionalProperties': False}, 'strict': True}

scrapezy

other

{'type': 'function', 'name': 'extract-structured-data', 'description': 'Extract structured data from a website.', 'parameters': {'type': 'object', 'properties': {'prompt': {'type': 'string', 'description': 'Prompt to extract data from the website'}, 'url': {'type': 'string', 'description': 'URL of the website to extract data from', 'format': 'uri'}}, 'required': ['url', 'prompt'], 'additionalProperties': False}, 'strict': True}

securenote-link-mcp-server

other

{'type': 'function', 'name': 'check_api_health', 'description': 'Check if the secure notes API is running and healthy.', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

securenote-link-mcp-server

other

{'type': 'function', 'name': 'get_instructions', 'description': 'Provides a comprehensive guide on how to use this secure note sharing service, intended for both humans and AI agents.\n\nThis guide explains the encryption process, the different methods for sharing secrets, and the tools available.', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

securenote-link-mcp-server

other

{'type': 'function', 'name': 'retrieve_and_decrypt_secret', 'description': 'Retrieve and decrypt a secret from the API.\n\nArgs:\n secret_id: The ID of the secret to retrieve\n decryption_key: The decryption key (base64 encoded)\n password: Optional password if the secret is password protected', 'parameters': {'type': 'object', 'properties': {'decryption_key': {'type': 'string', 'title': 'Decryption Key'}, 'password': {'title': 'Password', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}, 'secret_id': {'type': 'string', 'title': 'Secret Id'}}, 'required': ['secret_id', 'decryption_key'], 'additionalProperties': False}, 'strict': True}

securenote-link-mcp-server

other

{'type': 'function', 'name': 'send_secure_note', 'description': "Encrypt a message, send it to the secure notes API, and generate a single, shareable URL (default app behavior).\n\nThis function creates a user-friendly link that embeds both the secret ID and the decryption key.\nThe recipient can simply click the link to view the message—no need to copy/paste keys separately.\n\nThis is the default and recommended way to share secure notes in this app.\n\nArgs:\n message: The secret message to encrypt and send\n password: Optional password for additional protection\n expires_in: Expiration time in hours (1, 24, 72, or 168)\n\nReturns:\n A formatted message containing the shareable URL and security notes.\n\nSecurity Note:\n The decryption key is included in the URL fragment (after '#'), which is not sent to the server,\n but may be visible in browser history or if the link is shared insecurely.\n For maximum security, consider sharing the key separately.", 'parameters': {'type': 'object', 'properties': {'expires_in': {'type': 'integer', 'title': 'Expires In', 'default': 24}, 'message': {'type': 'string', 'title': 'Message'}, 'password': {'title': 'Password', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['message'], 'additionalProperties': False}, 'strict': True}

securenote-link-mcp-server

other

{'type': 'function', 'name': 'send_secure_note_return_api_url_and_key', 'description': "Encrypt a message, store it via the API, and return the retrieval URL and decryption key separately.\n\nThis function is for advanced workflows where you want to handle retrieval and decryption yourself.\nIt returns:\n - The API URL to retrieve the encrypted message (returns JSON, not a user-facing page)\n - The decryption key (base64-encoded, to be used separately)\n\nAfter calling this function, you (or your code) must:\n - Use your own code to fetch the encrypted message from the API and decrypt it using the key,\n OR\n - Use the provided 'retrieve_and_decrypt_secret' method to fetch and decrypt the message via the API.\n\nArgs:\n message: The secret message to encrypt and send.\n password: Optional password for additional protection.\n expires_in: Expiration time in hours (1, 24, 72, or 168).\n\nReturns:\n A formatted message containing:\n - The retrieval URL (API endpoint)\n - The decryption key (base64-encoded)\n - Security notes and usage instructions\n\nSecurity Note:\n For maximum security, share the URL and decryption key through different channels.\n If you want a single, user-friendly link, use 'send_secure_note' instead.\n\n---\nDecryption process specifics:\n- The encryption algorithm used is AES-256-GCM.\n- The encrypted data is base64-encoded, with a separate IV (also base64-encoded).\n- The API's response structure is JSON with fields like 'encryptedData' and 'iv'.\n- The key is base64-encoded.\n\nAnyone writing their own decryption code must:\n- Correctly parse the API response (get 'encryptedData' and 'iv').\n- Base64-decode the key, iv, and encryptedData.\n- Use AES-256-GCM to decrypt, using the key and iv.", 'parameters': {'type': 'object', 'properties': {'expires_in': {'type': 'integer', 'title': 'Expires In', 'default': 24}, 'message': {'type': 'string', 'title': 'Message'}, 'password': {'title': 'Password', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['message'], 'additionalProperties': False}, 'strict': True}

semgrep

other

{'type': 'function', 'name': 'get_abstract_syntax_tree', 'description': 'Returns the Abstract Syntax Tree (AST) for the provided code file in JSON format\n\n Use this tool when you need to:\n - get the Abstract Syntax Tree (AST) for the provided code file - get the AST of a file\n - understand the structure of the code in a more granular way\n - see what a parser sees in the code', 'parameters': {'type': 'object', 'properties': {'code': {'type': 'string', 'title': 'Code', 'description': 'The code to get the AST for'}, 'language': {'type': 'string', 'title': 'Language', 'description': 'The programming language of the code'}}, 'required': ['code', 'language'], 'additionalProperties': False}, 'strict': True}

semgrep

other

{'type': 'function', 'name': 'get_supported_languages', 'description': 'Returns a list of supported languages by Semgrep\n\n Only use this tool if you are not sure what languages Semgrep supports.', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

semgrep

other

{'type': 'function', 'name': 'security_check', 'description': "Runs a fast security check on code and returns any issues found.\n\n Use this tool when you need to:\n - scan code for security vulnerabilities\n - verify that code is secure\n - double check that code is secure before committing\n - get a second opinion on code security\n\n If there are any issues found, you **MUST** fix them or offer to fix them and\n explain to the user why it's important to fix.\n If there are no issues, you can be reasonably confident that the code is secure.", 'parameters': {'type': 'object', 'properties': {'code_files': {'type': 'array', 'title': 'Code Files', 'description': "List of dictionaries with 'filename' and 'content' keys", 'items': {'type': 'object', 'additionalProperties': {'type': 'string'}}}}, 'required': ['code_files'], 'additionalProperties': False}, 'strict': True}

semgrep

other

{'type': 'function', 'name': 'semgrep_findings', 'description': 'Fetches findings from the Semgrep AppSec Platform Findings API.\n\n This function retrieves security, code quality, and supply chain findings that have already been\n identified by previous Semgrep scans and uploaded to the Semgrep AppSec platform. It does NOT\n perform a new scan or analyze code directly. Instead, it queries the Semgrep API to access\n historical scan results for a given repository or set of repositories.\n\n DEFAULT BEHAVIOR: By default, this tool should filter by the current repository. The model\n should determine the current repository name and pass it in the \'repos\' parameter to ensure\n findings are scoped to the relevant codebase. However, users may explicitly request findings\n from other repositories, in which case the model should respect that request.\n\n Use this function when a prompt requests a summary, list, or analysis of existing findings,\n such as:\n - "Please list the top 10 security findings and propose solutions for them."\n - "Show all open critical vulnerabilities in this repository."\n - "Summarize the most recent Semgrep scan results."\n - "Get findings from repository X" (explicitly requesting different repo)\n\n This function is ideal for:\n - Reviewing, listing, or summarizing findings from past scans.\n - Providing actionable insights or remediation advice based on existing scan data.\n\n Do NOT use this function to perform a new scan or check code that has not yet been analyzed by\n Semgrep. For new scans, use the appropriate scanning function.\n\n Args:\n issue_type (Optional[List[str]]): Filter findings by type. Use \'sast\' for code analysis\n findings and \'sca\' for supply chain analysis findings (e.g., [\'sast\'], [\'sca\']).\n status (Optional[str]): Filter findings by status (default: \'open\').\n repos (Optional[List[str]]): List of repository names to filter results. By default, should\n include the current repository name to scope findings appropriately. Can be overridden\n when users explicitly request findings from other repositories.\n severities (Optional[List[str]]): Filter findings by severity (e.g., [\'critical\', \'high\']).\n confidence (Optional[List[str]]): Filter findings by confidence level (e.g., [\'high\']).\n autotriage_verdict (Optional[str]): Filter findings by auto-triage verdict\n (default: \'true_positive\').\n page (Optional[int]): Page number for paginated results. (default: 0)\n page_size (int): Number of findings per page (default: 100, min: 100, max: 3000).\n\n Returns:\n List[Finding]: A list of findings matching the specified filters, where each finding\n contains details such as rule ID, description, severity, file location, and remediation\n guidance if available.', 'parameters': {'type': 'object', 'properties': {'autotriage_verdict': {'type': 'string', 'title': 'Autotriage Verdict', 'default': 'true_positive'}, 'confidence': {'type': 'array', 'title': 'Confidence', 'default': None, 'items': {'type': 'string'}}, 'issue_type': {'type': 'array', 'title': 'Issue Type', 'default': ['sast', 'sca'], 'items': {'type': 'string'}}, 'page': {'type': 'integer', 'title': 'Page', 'default': 0}, 'page_size': {'type': 'integer', 'title': 'Page Size', 'default': 100}, 'repos': {'type': 'array', 'title': 'Repos', 'default': None, 'items': {'type': 'string'}}, 'severities': {'type': 'array', 'title': 'Severities', 'default': None, 'items': {'type': 'string'}}, 'status': {'type': 'string', 'title': 'Status', 'default': 'open'}}, 'required': [], 'additionalProperties': False}, 'strict': True}

semgrep

other

{'type': 'function', 'name': 'semgrep_rule_schema', 'description': 'Get the schema for a Semgrep rule\n\n Use this tool when you need to:\n - get the schema required to write a Semgrep rule\n - need to see what fields are available for a Semgrep rule\n - verify what fields are available for a Semgrep rule\n - verify the syntax for a Semgrep rule is correct', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

semgrep

other

{'type': 'function', 'name': 'semgrep_scan', 'description': 'Runs a Semgrep scan on provided code content and returns the findings in JSON format\n\n Use this tool when you need to:\n - scan code files for security vulnerabilities\n - scan code files for other issues', 'parameters': {'type': 'object', 'properties': {'code_files': {'type': 'array', 'title': 'Code Files', 'description': "List of dictionaries with 'filename' and 'content' keys", 'items': {'type': 'object', 'additionalProperties': {'type': 'string'}}}, 'config': {'title': 'Config', 'description': "Optional Semgrep configuration string (e.g. 'p/docker', 'p/xss', 'auto')", 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['code_files'], 'additionalProperties': False}, 'strict': True}

semgrep

other

{'type': 'function', 'name': 'semgrep_scan_local', 'description': 'Runs a Semgrep scan locally on provided code files returns the findings in JSON format.\n\n Files are expected to be in the current paths are absolute paths to the code files.\n\n Use this tool when you need to:\n - scan code files for security vulnerabilities\n - scan code files for other issues', 'parameters': {'type': 'object', 'properties': {'code_files': {'type': 'array', 'title': 'Code Files', 'description': "List of dictionaries with 'path' pointing to the absolute path of the code file", 'items': {'type': 'object', 'additionalProperties': {'type': 'string'}}}, 'config': {'title': 'Config', 'description': "Optional Semgrep configuration string (e.g. 'p/docker', 'p/xss', 'auto')", 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['code_files'], 'additionalProperties': False}, 'strict': True}

semgrep

other

{'type': 'function', 'name': 'semgrep_scan_with_custom_rule', 'description': 'Runs a Semgrep scan with a custom rule on provided code content\n and returns the findings in JSON format\n\n Use this tool when you need to:\n - scan code files for specific security vulnerability not covered by the default Semgrep rules\n - scan code files for specific issue not covered by the default Semgrep rules', 'parameters': {'type': 'object', 'properties': {'code_files': {'type': 'array', 'title': 'Code Files', 'description': "List of dictionaries with 'filename' and 'content' keys", 'items': {'type': 'object', 'additionalProperties': {'type': 'string'}}}, 'rule': {'type': 'string', 'title': 'Rule', 'description': 'Semgrep YAML rule string'}}, 'required': ['code_files', 'rule'], 'additionalProperties': False}, 'strict': True}

sentry

other

{'type': 'function', 'name': 'get_sentry_issue', 'description': 'Retrieve and analyze a Sentry issue by ID or URL. Use this tool when you need to:\n - Investigate production errors and crashes\n - Access detailed stacktraces from Sentry\n - Analyze error patterns and frequencies\n - Get information about when issues first/last occurred\n - Review error counts and status', 'parameters': {'type': 'object', 'properties': {'issue_id_or_url': {'type': 'string', 'description': 'Sentry issue ID or URL to analyze'}}, 'required': ['issue_id_or_url'], 'additionalProperties': False}, 'strict': True}

sequentialthinking

other

{'type': 'function', 'name': 'sequentialthinking', 'description': 'A detailed tool for dynamic and reflective problem-solving through thoughts.\nThis tool helps analyze problems through a flexible thinking process that can adapt and evolve.\nEach thought can build on, question, or revise previous insights as understanding deepens.\n\nWhen to use this tool:\n- Breaking down complex problems into steps\n- Planning and design with room for revision\n- Analysis that might need course correction\n- Problems where the full scope might not be clear initially\n- Problems that require a multi-step solution\n- Tasks that need to maintain context over multiple steps\n- Situations where irrelevant information needs to be filtered out\n\nKey features:\n- You can adjust total_thoughts up or down as you progress\n- You can question or revise previous thoughts\n- You can add more thoughts even after reaching what seemed like the end\n- You can express uncertainty and explore alternative approaches\n- Not every thought needs to build linearly - you can branch or backtrack\n- Generates a solution hypothesis\n- Verifies the hypothesis based on the Chain of Thought steps\n- Repeats the process until satisfied\n- Provides a correct answer\n\nParameters explained:\n- thought: Your current thinking step, which can include:\n* Regular analytical steps\n* Revisions of previous thoughts\n* Questions about previous decisions\n* Realizations about needing more analysis\n* Changes in approach\n* Hypothesis generation\n* Hypothesis verification\n- next_thought_needed: True if you need more thinking, even if at what seemed like the end\n- thought_number: Current number in sequence (can go beyond initial total if needed)\n- total_thoughts: Current estimate of thoughts needed (can be adjusted up/down)\n- is_revision: A boolean indicating if this thought revises previous thinking\n- revises_thought: If is_revision is true, which thought number is being reconsidered\n- branch_from_thought: If branching, which thought number is the branching point\n- branch_id: Identifier for the current branch (if any)\n- needs_more_thoughts: If reaching end but realizing more thoughts needed\n\nYou should:\n1. Start with an initial estimate of needed thoughts, but be ready to adjust\n2. Feel free to question or revise previous thoughts\n3. Don\'t hesitate to add more thoughts if needed, even at the "end"\n4. Express uncertainty when present\n5. Mark thoughts that revise previous thinking or branch into new paths\n6. Ignore information that is irrelevant to the current step\n7. Generate a solution hypothesis when appropriate\n8. Verify the hypothesis based on the Chain of Thought steps\n9. Repeat the process until satisfied with the solution\n10. Provide a single, ideally correct answer as the final output\n11. Only set next_thought_needed to false when truly done and a satisfactory answer is reached', 'parameters': {'type': 'object', 'properties': {'branchFromThought': {'type': 'integer', 'description': 'Branching point thought number', 'minimum': 1}, 'branchId': {'type': 'string', 'description': 'Branch identifier'}, 'isRevision': {'type': 'boolean', 'description': 'Whether this revises previous thinking'}, 'needsMoreThoughts': {'type': 'boolean', 'description': 'If more thoughts are needed'}, 'nextThoughtNeeded': {'type': 'boolean', 'description': 'Whether another thought step is needed'}, 'revisesThought': {'type': 'integer', 'description': 'Which thought is being reconsidered', 'minimum': 1}, 'thought': {'type': 'string', 'description': 'Your current thinking step'}, 'thoughtNumber': {'type': 'integer', 'description': 'Current thought number', 'minimum': 1}, 'totalThoughts': {'type': 'integer', 'description': 'Estimated total thoughts needed', 'minimum': 1}}, 'required': ['thought', 'nextThoughtNeeded', 'thoughtNumber', 'totalThoughts'], 'additionalProperties': False}, 'strict': True}

short-io

other

{'type': 'function', 'name': 'create-short-link', 'description': 'Create short link from the original URL', 'parameters': {'type': 'object', 'properties': {'allowDuplicates': {'type': 'boolean'}, 'androidURL': {'type': 'string'}, 'archived': {'type': 'boolean'}, 'clicksLimit': {'type': 'number'}, 'cloaking': {'type': 'boolean'}, 'createdAt': {'type': ['string', 'number']}, 'domain': {'type': 'string'}, 'expiredURL': {'type': 'string'}, 'expiresAt': {'type': ['string', 'number']}, 'folderId': {'type': 'string'}, 'integrationAdroll': {'type': 'string'}, 'integrationFB': {'type': 'string'}, 'integrationGA': {'type': 'string'}, 'integrationGTM': {'type': 'string'}, 'iphoneURL': {'type': 'string'}, 'originalURL': {'type': 'string'}, 'password': {'type': 'string'}, 'passwordContact': {'type': 'boolean'}, 'path': {'type': 'string'}, 'redirectType': {'type': 'number', 'enum': [301, 302, 307, 308]}, 'skipQS': {'type': 'boolean'}, 'splitPercent': {'type': 'number'}, 'splitURL': {'type': 'string'}, 'tags': {'type': 'array', 'items': {'type': 'string'}}, 'title': {'type': 'string'}, 'ttl': {'type': ['string', 'number']}, 'utmCampaign': {'type': 'string'}, 'utmContent': {'type': 'string'}, 'utmMedium': {'type': 'string'}, 'utmSource': {'type': 'string'}, 'utmTerm': {'type': 'string'}}, 'required': ['domain', 'originalURL'], 'additionalProperties': False}, 'strict': True}

short-io

other

{'type': 'function', 'name': 'domain-statistics', 'description': 'Get detailed statistics for domain in given period', 'parameters': {'type': 'object', 'properties': {'clicksChartInterval': {'type': 'string', 'enum': ['hour', 'day', 'week', 'month']}, 'domainId': {'type': 'number'}, 'endDate': {'type': 'string'}, 'exclude': {'type': 'object', 'additionalProperties': False}, 'include': {'type': 'object', 'additionalProperties': False}, 'period': {'type': 'string', 'enum': ['custom', 'today', 'yesterday', 'total', 'week', 'month', 'lastmonth', 'last7', 'last30']}, 'skipTops': {'type': 'boolean'}, 'startDate': {'type': 'string'}, 'tz': {'type': 'string'}}, 'required': ['domainId', 'period'], 'additionalProperties': False}, 'strict': True}

short-io

other

{'type': 'function', 'name': 'get-domains', 'description': 'Get list of domains in the account', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

short-io

other

{'type': 'function', 'name': 'get-link-list', 'description': 'Get list of links for a domain', 'parameters': {'type': 'object', 'properties': {'afterDate': {'type': 'string'}, 'beforeDate': {'type': 'string'}, 'createAt': {'type': 'string'}, 'dateSortOrder': {'type': 'string', 'enum': ['asc', 'desc']}, 'domainId': {'type': 'number'}, 'folderId': {'type': 'string'}, 'limit': {'type': 'number'}}, 'required': ['domainId'], 'additionalProperties': False}, 'strict': True}

short-io

other

{'type': 'function', 'name': 'link-statistics', 'description': 'Get detailed statistics for link in given period', 'parameters': {'type': 'object', 'properties': {'clicksChartInterval': {'type': 'string', 'enum': ['hour', 'day', 'week', 'month']}, 'endDate': {'type': 'string'}, 'exclude': {'type': 'object', 'additionalProperties': False}, 'include': {'type': 'object', 'additionalProperties': False}, 'linkId': {'type': 'string'}, 'period': {'type': 'string', 'enum': ['custom', 'today', 'yesterday', 'total', 'week', 'month', 'lastmonth', 'last7', 'last30']}, 'skipTops': {'type': 'boolean'}, 'startDate': {'type': 'string'}, 'tz': {'type': 'string'}}, 'required': ['linkId'], 'additionalProperties': False}, 'strict': True}

short-io

other

{'type': 'function', 'name': 'search-links', 'description': 'Search for links in a domain', 'parameters': {'type': 'object', 'properties': {'afterDate': {'type': 'string'}, 'beforeDate': {'type': 'string'}, 'dateSortOrder': {'type': 'string', 'enum': ['asc', 'desc']}, 'domainId': {'type': 'number'}, 'folderId': {'type': 'string'}, 'limit': {'type': 'number'}, 'q': {'type': 'string', 'description': 'Search query'}, 'tz': {'type': 'string'}}, 'required': ['domainId'], 'additionalProperties': False}, 'strict': True}

short-io

other

{'type': 'function', 'name': 'top-by-interval-column', 'description': 'Get top clicks values by interval and counts for specified column', 'parameters': {'type': 'object', 'properties': {'column': {'type': 'string', 'enum': ['path', 'path_404', 'method', 'st', 'proto', 'human', 'browser', 'browser_version', 'country', 'city', 'social', 'refhost', 'os', 'utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'goal_completed', 'ab_path']}, 'domainId': {'type': 'number'}, 'endDate': {'type': 'string'}, 'exclude': {'type': 'object', 'additionalProperties': False}, 'include': {'type': 'object', 'additionalProperties': False}, 'interval': {'type': 'string', 'enum': ['hour', 'day', 'week', 'month']}, 'limit': {'type': 'number'}, 'period': {'type': 'string', 'enum': ['custom', 'today', 'yesterday', 'total', 'week', 'month', 'lastmonth', 'last7', 'last30']}, 'startDate': {'type': 'string'}, 'tz': {'type': 'string'}}, 'required': ['domainId', 'column', 'interval'], 'additionalProperties': False}, 'strict': True}

short-io

other

{'type': 'function', 'name': 'top-column-by-link-statistics', 'description': 'Get top column values for link in given period', 'parameters': {'type': 'object', 'properties': {'column': {'type': 'string', 'enum': ['path', 'path_404', 'method', 'st', 'proto', 'human', 'browser', 'browser_version', 'country', 'city', 'social', 'refhost', 'os', 'utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'goal_completed', 'ab_path']}, 'endDate': {'type': 'string'}, 'exclude': {'type': 'object', 'additionalProperties': False}, 'include': {'type': 'object', 'additionalProperties': False}, 'limit': {'type': 'number'}, 'linkId': {'type': 'string'}, 'period': {'type': 'string', 'enum': ['custom', 'today', 'yesterday', 'total', 'week', 'month', 'lastmonth', 'last7', 'last30']}, 'prefix': {'type': 'string'}, 'startDate': {'type': 'string'}, 'tz': {'type': 'string'}}, 'required': ['linkId', 'column'], 'additionalProperties': False}, 'strict': True}

short-io

other

{'type': 'function', 'name': 'top-column-statistics', 'description': 'Get top clicks values for specified column, ordered by clicks desc', 'parameters': {'type': 'object', 'properties': {'column': {'type': 'string', 'enum': ['path', 'path_404', 'method', 'st', 'proto', 'human', 'browser', 'browser_version', 'country', 'city', 'social', 'refhost', 'os', 'utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'goal_completed', 'ab_path']}, 'domainId': {'type': 'number'}, 'endDate': {'type': 'string'}, 'exclude': {'type': 'object', 'additionalProperties': False}, 'include': {'type': 'object', 'additionalProperties': False}, 'limit': {'type': 'number'}, 'period': {'type': 'string', 'enum': ['custom', 'today', 'yesterday', 'total', 'week', 'month', 'lastmonth', 'last7', 'last30']}, 'startDate': {'type': 'string'}, 'tz': {'type': 'string'}}, 'required': ['domainId', 'column'], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'create_job_from_notebook', 'description': 'Create a scheduled job to run a notebook (uploaded to shared space).\n\n Args:\n ctx: Context object\n name: Name of the job\n notebook_path: Remote path to the shared notebook file\n mode: Job mode (options: "Once", "Recurring")\n execution_interval_in_minutes: Optional interval in minutes for recurring jobs\n\n Returns:\n Dict with job creation result', 'parameters': {'type': 'object', 'properties': {'execution_interval_in_minutes': {'title': 'Execution Interval In Minutes', 'default': None, 'anyOf': [{'type': 'integer'}, {'type': 'null'}]}, 'mode': {'type': 'string', 'title': 'Mode', 'default': 'Once'}, 'name': {'type': 'string', 'title': 'Name'}, 'notebook_path': {'type': 'string', 'title': 'Notebook Path'}}, 'required': ['name', 'notebook_path'], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'create_notebook_file', 'description': 'Create a Jupyter notebook file in the correct singlestore format and saves it to a temporary location.\n\n This tool validates the provided content against the Jupyter notebook schema and creates a properly\n formatted .ipynb file in a temporary location. The content is converted from the simplified format\n to the full Jupyter notebook format.\n\n Args:\n content: Notebook content in the format: {\n "cells": [\n {"type": "markdown", "content": "Markdown content here"},\n {"type": "code", "content": "Python code here"}\n ]\n }\n\n Returns:\n Dictionary with the temporary file path and validation status\n\n Example:\n content = {\n "cells": [\n {"type": "markdown", "content": "# My Notebook\nThis is a sample notebook"},\n {"type": "code", "content": "import pandas as pd\nprint(\'Hello World\')"}\n ]\n }', 'parameters': {'type': 'object', 'properties': {'content': {'type': 'object', 'title': 'Content', 'additionalProperties': True}}, 'required': ['content'], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'create_starter_workspace', 'description': 'Create a new starter workspace using the SingleStore SDK.\n\n This tool provides a modern SDK-based approach to creating starter workspaces,\n offering improved reliability and better error handling compared to direct API calls.\n\n Args:\n name: Unique name for the new starter workspace\n database_name: Name of the database to create in the starter workspace\n provider: Cloud provider for the workspace (e.g., "AWS", "GCP", "Azure")\n region_name: Region where the workspace should be deployed (e.g., "us-west-2", "europe-west1")\n\n Returns:\n Dictionary with starter workspace creation details including:\n - workspace_id: Unique identifier for the created workspace\n - name: Display name of the workspace\n - endpoint: Connection endpoint URL\n - database_name: Name of the primary database\n\n Example Usage:\n ```python\n result = create_starter_workspace(\n ctx=ctx,\n name="my-test-workspace",\n database_name="analytics_db"\n )\n workspace_id = result["workspace_id"]\n endpoint = result["endpoint"]\n ```', 'parameters': {'type': 'object', 'properties': {'database_name': {'type': 'string', 'title': 'Database Name'}, 'name': {'type': 'string', 'title': 'Name'}, 'provider': {'title': 'Provider', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}, 'region_name': {'title': 'Region Name', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['name', 'database_name'], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'delete_job', 'description': 'Delete a scheduled job by its ID.\n\n Args:\n ctx: Context object\n job_id: ID of the job to delete\n\n Returns:\n Dict with deletion result', 'parameters': {'type': 'object', 'properties': {'job_id': {'type': 'string', 'title': 'Job Id'}}, 'required': ['job_id'], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'get_job', 'description': 'Retrieve details of a scheduled job by its ID.\n\n Args:\n ctx: Context object\n job_id: ID of the job to retrieve\n\n Returns:\n Dict with job details or error info', 'parameters': {'type': 'object', 'properties': {'job_id': {'type': 'string', 'title': 'Job Id'}}, 'required': ['job_id'], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'get_user_info', 'description': 'Retrieve all information about the current user.\n\n Returns:\n dict: User information including userID, email, firstName, lastName.\n\n Performance Tip:\n Cache the returned info when making multiple API calls.', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'list_regions', 'description': 'List all available deployment regions where SingleStore workspaces can be deployed by the user.\n\n Returns region information including:\n - regionID: Unique identifier for the region\n - provider: Cloud provider (AWS, GCP, or Azure)\n - name: Human-readable region name (e.g., Europe West 2 (London), US West 2 (Oregon))\n\n Use this tool to:\n 1. Select optimal deployment regions based on:\n - Geographic proximity to users\n - Compliance requirements\n - Cost considerations\n - Available cloud providers\n 2. Plan multi-region deployments', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'list_sharedtier_regions', 'description': 'List all regions where shared tier workspaces can be created.\n\n This tool provides information about available regions for creating starter workspaces,\n including region names and cloud providers.\n\n Args:\n ctx: Context for user interaction and logging\n\n Returns:\n Dictionary with region information including:\n - regionName: Name of the region (e.g., "us-west-2", "europe-west1")\n - provider: Cloud provider (AWS, GCP, or Azure)\n - name: Human-readable region name (e.g., Europe West 2 (London), US West 2 (Oregon))\n\n Example Usage:\n ```python\n result = await list_shared_tier_regions(ctx)\n regions = result["data"]["result"]\n ```', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'list_starter_workspaces', 'description': 'List all starter (virtual) workspaces available to the user in SingleStore.\n\n Returns detailed information about each starter workspace:\n - virtualWorkspaceID: Unique identifier for the workspace\n - name: Display name of the workspace\n - endpoint: Connection endpoint URL\n - databaseName: Name of the primary database\n - mysqlDmlPort: Port for MySQL protocol connections\n - webSocketPort: Port for WebSocket connections\n - state: Current status of the workspace\n\n Use this tool to:\n 1. Get starter workspace IDs for other operations\n 2. Check starter workspace availability and status\n 3. Obtain connection details for database access', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'organization_info', 'description': "Retrieve information about the current user's organization in SingleStore.\n\n Returns organization details including:\n - orgID: Unique identifier for the organization\n - name: Organization display name", 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'resume_workspace', 'description': 'Resume a workspace within a specified workspace group in SingleStore.\n\n Args:\n workspace_group_id: Unique identifier of the workspace group\n workspace_id: Unique identifier of the workspace to resume\n\n Returns:\n Dictionary with status, message, and metadata about the resume operation', 'parameters': {'type': 'object', 'properties': {'workspace_id': {'type': 'string', 'title': 'Workspace Id'}}, 'required': ['workspace_id'], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'run_sql', 'description': 'Use this tool to execute a single SQL statement against a SingleStore database.\n\n Returns:\n - Query results with column names and typed values\n - Row count and metadata\n - Execution status\n - Workspace type ("shared" for starter workspaces, "dedicated" for regular workspaces)\n - Workspace name\n\n Args:\n id: Workspace or starter workspace ID\n sql_query: The SQL query to execute\n database: (optional) Database name to use\n\n Returns:\n Standardized response with query results and metadata', 'parameters': {'type': 'object', 'properties': {'database': {'title': 'Database', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}, 'id': {'type': 'string', 'title': 'Id'}, 'sql_query': {'type': 'string', 'title': 'Sql Query'}}, 'required': ['sql_query', 'id'], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'terminate_starter_workspace', 'description': 'Permanently delete a starter workspace in SingleStore with safety confirmations.\n\n ⚠️ WARNING: This action CANNOT be undone. All workspace data will be permanently lost.\n Make sure to backup important data before proceeding.\n\n Safety Features:\n - Requires explicit user confirmation (if elicitation is supported)\n - Validates workspace existence\n - Provides warning messages\n - Includes error handling\n\n Args:\n ctx: Context for user interaction and logging\n workspace_id: Workspace identifier (format: "ws-" followed by alphanumeric chars)\n\n Returns:\n {\n "status": "success" | "error" | "cancelled",\n "message": str, # Human-readable result\n "workspace_id": str,\n "workspace_name": str, # If available\n "termination_time": str, # ISO 8601 (if successful)\n "error": str # If status="error"\n }\n\n Example:\n ```python\n result = await terminate_starter_workspace(ctx, "ws-abc123")\n if result["status"] == "success":\n print(f"Workspace {result[\'workspace_name\']} terminated")\n ```\n\n Related:\n - list_starter_workspaces()\n - create_starter_workspace()', 'parameters': {'type': 'object', 'properties': {'workspace_id': {'type': 'string', 'title': 'Workspace Id'}}, 'required': ['workspace_id'], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'upload_notebook_file', 'description': 'Upload a notebook file from a local local_path to SingleStore shared or personal space.\n\n This tool validates the notebook schema before uploading. If upload_name or upload_location\n are not provided, the user will be prompted through elicitation.\n\n Args:\n local_path: Local file system path to the notebook file (.ipynb)\n upload_name: Optional. Name of the file after upload (with or without .ipynb extension).\n If not provided, user will be prompted.\n upload_location: Optional. Either "shared" or "personal". If not provided, user will be prompted.\n\n Returns:\n Dictionary with upload status and file information\n\n Example:\n local_path = "/path/to/my_notebook.ipynb"\n upload_name = "analysis_notebook" # Optional\n upload_location = "shared" # Optional', 'parameters': {'type': 'object', 'properties': {'local_path': {'type': 'string', 'title': 'Local Path'}, 'upload_location': {'title': 'Upload Location', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}, 'upload_name': {'title': 'Upload Name', 'default': None, 'anyOf': [{'type': 'string'}, {'type': 'null'}]}}, 'required': ['local_path'], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'workspace_groups_info', 'description': 'List all workspace groups accessible to the user in SingleStore.\n\n Returns detailed information for each group:\n - workspaceGroupID: Unique identifier for the group\n - name: Display name of the workspace group\n - region: Region information (name, provider)\n - firewallRanges: List of allowed IP ranges for the group\n - allowAllTraffic: Whether all traffic is allowed to the group\n - createdAt: Timestamp of group creation\n - terminatedAt: Timestamp when the group was terminated (if applicable)\n\n\n Use this tool to:\n 1. Get workspace group IDs for other operations\n 2. Plan maintenance windows\n\n Related operations:\n - Use workspaces_info to list workspaces within a group\n - Use execute_sql to run queries on workspaces in a group', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

singlestore

other

{'type': 'function', 'name': 'workspaces_info', 'description': "List all workspaces within a specified workspace group in SingleStore.\n\n Returns detailed information for each workspace:\n - createdAt: Timestamp of workspace creation\n - deploymentType: Type of deployment (e.g., 'PRODUCTION')\n - endpoint: Connection URL for database access\n - name: Display name of the workspace\n - size: Compute and storage configuration\n - state: Current status (e.g., 'ACTIVE', 'PAUSED')\n - terminatedAt: End timestamp if applicable\n - workspaceGroupID: Workspacegroup identifier\n - workspaceID: Unique workspace identifier\n\n Args:\n workspace_group_id: Unique identifier of the workspace group\n\n Returns:\n List of workspace information dictionaries", 'parameters': {'type': 'object', 'properties': {'workspace_group_id': {'type': 'string', 'title': 'Workspace Group Id'}}, 'required': ['workspace_group_id'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'api_hub_create_portal', 'description': "Create a new portal within API Hub.\n\n**Parameters:**\n- name (string): The portal name.\n- subdomain (string) *required*: The portal subdomain.\n- offline (boolean): If set to true the portal will not be visible to customers.\n- routing (string): Determines the routing strategy ('browser' or 'proxy').\n- credentialsEnabled (string): Indicates if credentials are enabled for the portal.\n- swaggerHubOrganizationId (string) *required*: The corresponding API Hub (formerly SwaggerHub) organization UUID.\n- openapiRenderer (string): Portal level setting for the OpenAPI renderer. SWAGGER_UI - Use the Swagger UI renderer. ELEMENTS - Use the Elements renderer. TOGGLE - Switch between the two renderers with elements set as the default.\n- pageContentFormat (string): The format of the page content.", 'parameters': {'type': 'object', 'properties': {'credentialsEnabled': {'type': 'string', 'description': 'Indicates if credentials are enabled for the portal.'}, 'name': {'type': 'string', 'description': 'The portal name.'}, 'offline': {'type': 'boolean', 'description': 'If set to true the portal will not be visible to customers.'}, 'openapiRenderer': {'type': 'string', 'description': 'Portal level setting for the OpenAPI renderer. SWAGGER_UI - Use the Swagger UI renderer. ELEMENTS - Use the Elements renderer. TOGGLE - Switch between the two renderers with elements set as the default.'}, 'pageContentFormat': {'type': 'string', 'description': 'The format of the page content.'}, 'routing': {'type': 'string', 'description': "Determines the routing strategy ('browser' or 'proxy')."}, 'subdomain': {'type': 'string', 'description': 'The portal subdomain.'}, 'swaggerHubOrganizationId': {'type': 'string', 'description': 'The corresponding API Hub (formerly SwaggerHub) organization UUID.'}}, 'required': ['subdomain', 'swaggerHubOrganizationId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'api_hub_create_portal_product', 'description': "Create a new product for a specific portal.\n\n**Parameters:**\n- portalId (string) *required*: Portal UUID or subdomain.\n- type (string) *required*: Product type (Allowed values: 'new', 'copy').\n- name (string) *required*: Product name.\n- slug (string) *required*: URL component for this product. Must be unique within the portal.\n- description (string): Product description.\n- public (boolean): Indicates if the product is public.\n- hidden (string): Indicates if the product is hidden.\n- role (boolean): Indicates if the product has a role.", 'parameters': {'type': 'object', 'properties': {'description': {'type': 'string', 'description': 'Product description.'}, 'hidden': {'type': 'string', 'description': 'Indicates if the product is hidden.'}, 'name': {'type': 'string', 'description': 'Product name.'}, 'portalId': {'type': 'string', 'description': 'Portal UUID or subdomain.'}, 'public': {'type': 'boolean', 'description': 'Indicates if the product is public.'}, 'role': {'type': 'boolean', 'description': 'Indicates if the product has a role.'}, 'slug': {'type': 'string', 'description': 'URL component for this product. Must be unique within the portal.'}, 'type': {'type': 'string', 'description': "Product type (Allowed values: 'new', 'copy')."}}, 'required': ['portalId', 'type', 'name', 'slug'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'api_hub_delete_portal', 'description': 'Delete a specific portal.\n\n**Parameters:**\n- portalId (string) *required*: Portal UUID or subdomain.', 'parameters': {'type': 'object', 'properties': {'portalId': {'type': 'string', 'description': 'Portal UUID or subdomain.'}}, 'required': ['portalId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'api_hub_delete_portal_product', 'description': 'Delete a product from a specific portal\n\n**Parameters:**\n- productId (string) *required*: Product UUID, or identifier in the format.', 'parameters': {'type': 'object', 'properties': {'productId': {'type': 'string', 'description': 'Product UUID, or identifier in the format.'}}, 'required': ['productId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'api_hub_get_portal', 'description': 'Retrieve information about a specific portal.\n\n**Parameters:**\n- portalId (string) *required*: Portal UUID or subdomain.', 'parameters': {'type': 'object', 'properties': {'portalId': {'type': 'string', 'description': 'Portal UUID or subdomain.'}}, 'required': ['portalId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'api_hub_get_portal_product', 'description': 'Retrieve information about a specific product resource.\n\n**Parameters:**\n- productId (string) *required*: Product UUID, or identifier in the format.', 'parameters': {'type': 'object', 'properties': {'productId': {'type': 'string', 'description': 'Product UUID, or identifier in the format.'}}, 'required': ['productId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'api_hub_list_portal_products', 'description': 'Get products for a specific portal that match your criteria.\n\n**Parameters:**\n- portalId (string) *required*: Portal UUID or subdomain.', 'parameters': {'type': 'object', 'properties': {'portalId': {'type': 'string', 'description': 'Portal UUID or subdomain.'}}, 'required': ['portalId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'api_hub_list_portals', 'description': 'Search for available portals within API Hub. Only portals where you have at least a designer role, either at the product level or organization level, are returned.', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'api_hub_update_portal', 'description': "Update a specific portal's configuration.\n\n**Parameters:**\n- portalId (string) *required*: Portal UUID or subdomain.\n- name (string): The portal name.\n- subdomain (string): The portal subdomain.\n- customDomain (boolean): Indicates if the portal has a custom domain.\n- gtmKey (string): Google Tag Manager key for the portal.\n- offline (boolean): If set to true the portal will not be visible to customers.\n- routing (string): Determines the routing strategy ('browser' or 'proxy').\n- credentialsEnabled (boolean): Indicates if credentials are enabled for the portal.\n- openapiRenderer (string): Portal level setting for the OpenAPI renderer. SWAGGER_UI - Use the Swagger UI renderer. ELEMENTS - Use the Elements renderer. TOGGLE - Switch between the two renderers with elements set as the default.\n- pageContentFormat (string): The format of the page content.", 'parameters': {'type': 'object', 'properties': {'credentialsEnabled': {'type': 'boolean', 'description': 'Indicates if credentials are enabled for the portal.'}, 'customDomain': {'type': 'boolean', 'description': 'Indicates if the portal has a custom domain.'}, 'gtmKey': {'type': 'string', 'description': 'Google Tag Manager key for the portal.'}, 'name': {'type': 'string', 'description': 'The portal name.'}, 'offline': {'type': 'boolean', 'description': 'If set to true the portal will not be visible to customers.'}, 'openapiRenderer': {'type': 'string', 'description': 'Portal level setting for the OpenAPI renderer. SWAGGER_UI - Use the Swagger UI renderer. ELEMENTS - Use the Elements renderer. TOGGLE - Switch between the two renderers with elements set as the default.'}, 'pageContentFormat': {'type': 'string', 'description': 'The format of the page content.'}, 'portalId': {'type': 'string', 'description': 'Portal UUID or subdomain.'}, 'routing': {'type': 'string', 'description': "Determines the routing strategy ('browser' or 'proxy')."}, 'subdomain': {'type': 'string', 'description': 'The portal subdomain.'}}, 'required': ['portalId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'api_hub_update_portal_product', 'description': "Update a product's settings within a specific portal.\n\n**Parameters:**\n- productId (string) *required*: Product UUID, or identifier in the format.\n- name (string): Product name.\n- slug (string): URL component for this product. Must be unique within the portal.\n- description (string): Product description.\n- public (boolean): Indicates if the product is public.\n- hidden (string): Indicates if the product is hidden.", 'parameters': {'type': 'object', 'properties': {'description': {'type': 'string', 'description': 'Product description.'}, 'hidden': {'type': 'string', 'description': 'Indicates if the product is hidden.'}, 'name': {'type': 'string', 'description': 'Product name.'}, 'productId': {'type': 'string', 'description': 'Product UUID, or identifier in the format.'}, 'public': {'type': 'boolean', 'description': 'Indicates if the product is public.'}, 'slug': {'type': 'string', 'description': 'URL component for this product. Must be unique within the portal.'}}, 'required': ['productId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'reflect_cancel_suite_execution', 'description': 'Cancel a reflect suite execution\n\n**Parameters:**\n- suiteId (string) *required*: ID of the reflect suite to cancel execution for\n- executionId (string) *required*: ID of the reflect suite execution to cancel', 'parameters': {'type': 'object', 'properties': {'executionId': {'type': 'string', 'description': 'ID of the reflect suite execution to cancel'}, 'suiteId': {'type': 'string', 'description': 'ID of the reflect suite to cancel execution for'}}, 'required': ['suiteId', 'executionId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'reflect_execute_suite', 'description': 'Execute a reflect suite\n\n**Parameters:**\n- suiteId (string) *required*: ID of the reflect suite to list executions for', 'parameters': {'type': 'object', 'properties': {'suiteId': {'type': 'string', 'description': 'ID of the reflect suite to list executions for'}}, 'required': ['suiteId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'reflect_get_suite_execution_status', 'description': 'Get the status of a reflect suite execution\n\n**Parameters:**\n- suiteId (string) *required*: ID of the reflect suite to get execution status for\n- executionId (string) *required*: ID of the reflect suite execution to get status for', 'parameters': {'type': 'object', 'properties': {'executionId': {'type': 'string', 'description': 'ID of the reflect suite execution to get status for'}, 'suiteId': {'type': 'string', 'description': 'ID of the reflect suite to get execution status for'}}, 'required': ['suiteId', 'executionId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'reflect_get_test_status', 'description': 'Get the status of a reflect test execution\n\n**Parameters:**\n- testId (string) *required*: ID of the reflect test to run\n- executionId (string) *required*: ID of the reflect test execution to get status for', 'parameters': {'type': 'object', 'properties': {'executionId': {'type': 'string', 'description': 'ID of the reflect test execution to get status for'}, 'testId': {'type': 'string', 'description': 'ID of the reflect test to run'}}, 'required': ['testId', 'executionId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'reflect_list_suite_executions', 'description': 'List all executions for a given suite\n\n**Parameters:**\n- suiteId (string) *required*: ID of the reflect suite to list executions for', 'parameters': {'type': 'object', 'properties': {'suiteId': {'type': 'string', 'description': 'ID of the reflect suite to list executions for'}}, 'required': ['suiteId'], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'reflect_list_suites', 'description': 'Retrieve a list of all reflect suites available', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'reflect_list_tests', 'description': 'List all reflect tests', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

smartbear

other

{'type': 'function', 'name': 'reflect_run_test', 'description': 'Run a reflect test\n\n**Parameters:**\n- testId (string) *required*: ID of the reflect test to run', 'parameters': {'type': 'object', 'properties': {'testId': {'type': 'string', 'description': 'ID of the reflect test to run'}}, 'required': ['testId'], 'additionalProperties': False}, 'strict': True}

SQLite

other

{'type': 'function', 'name': 'append_insight', 'description': 'Add a business insight to the memo', 'parameters': {'type': 'object', 'properties': {'insight': {'type': 'string', 'description': 'Business insight discovered from data analysis'}}, 'required': ['insight'], 'additionalProperties': False}, 'strict': True}

SQLite

other

{'type': 'function', 'name': 'create_table', 'description': 'Create a new table in the SQLite database', 'parameters': {'type': 'object', 'properties': {'query': {'type': 'string', 'description': 'CREATE TABLE SQL statement'}}, 'required': ['query'], 'additionalProperties': False}, 'strict': True}

SQLite

other

{'type': 'function', 'name': 'describe_table', 'description': 'Get the schema information for a specific table', 'parameters': {'type': 'object', 'properties': {'table_name': {'type': 'string', 'description': 'Name of the table to describe'}}, 'required': ['table_name'], 'additionalProperties': False}, 'strict': True}

SQLite

other

{'type': 'function', 'name': 'list_tables', 'description': 'List all tables in the SQLite database', 'parameters': {'type': 'object', 'properties': {}, 'required': [], 'additionalProperties': False}, 'strict': True}

SQLite

other

{'type': 'function', 'name': 'read_query', 'description': 'Execute a SELECT query on the SQLite database', 'parameters': {'type': 'object', 'properties': {'query': {'type': 'string', 'description': 'SELECT SQL query to execute'}}, 'required': ['query'], 'additionalProperties': False}, 'strict': True}

SQLite

other

{'type': 'function', 'name': 'write_query', 'description': 'Execute an INSERT, UPDATE, or DELETE query on the SQLite database', 'parameters': {'type': 'object', 'properties': {'query': {'type': 'string', 'description': 'SQL query to execute'}}, 'required': ['query'], 'additionalProperties': False}, 'strict': True}

supadata

other

{'type': 'function', 'name': 'supadata_check_crawl_status', 'description': 'Check the status and retrieve results of a crawl job created with supadata_crawl.\n\n**Purpose:** Monitor crawl job progress and retrieve completed results.\n**Workflow:** Use the job ID returned from supadata_crawl to check status and get results.\n\n**Usage Example:**\n```json\n{\n "name": "supadata_check_crawl_status",\n "arguments": {\n "id": "550e8400-e29b-41d4-a716-446655440000"\n }\n}\n```\n\n**Returns:** \n- Job status: \'scraping\', \'completed\', \'failed\', or \'cancelled\'\n- For completed jobs: URL, Markdown content, page title, and description for each crawled page\n- Progress information and any error details if applicable\n\n**Tip:** Poll this endpoint periodically until status is \'completed\' or \'failed\'.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'Crawl job ID returned from supadata_crawl'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}

supadata

other

{'type': 'function', 'name': 'supadata_check_transcript_status', 'description': 'Check the status and retrieve results of a transcript job created with supadata_transcript.\n\n**Purpose:** Monitor transcript job progress and retrieve completed results.\n**Workflow:** Use the job ID returned from supadata_transcript to check status and get results.\n\n**Usage Example:**\n```json\n{\n "name": "supadata_check_transcript_status",\n "arguments": {\n "id": "550e8400-e29b-41d4-a716-446655440000"\n }\n}\n```\n\n**Returns:** \n- Job status: \'queued\', \'active\', \'completed\', \'failed\'\n- For completed jobs: Full transcript content\n- Error details if job failed\n\n**Tip:** Poll this endpoint periodically until status is \'completed\' or \'failed\'.', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'Transcript job ID returned from supadata_transcript'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}

supadata

other

{'type': 'function', 'name': 'supadata_crawl', 'description': 'Create a crawl job to extract content from all pages on a website using Supadata\'s crawling API.\n\n**Purpose:** Crawl a whole website and get content of all pages on it.\n**Best for:** Extracting content from multiple related pages when you need comprehensive coverage.\n**Workflow:** 1) Create crawl job → 2) Receive job ID → 3) Check job status and retrieve results\n\n**Crawling Behavior:**\n- Follows only child links within the specified domain\n- Example: For https://supadata.ai/blog, crawls https://supadata.ai/blog/article-1 but not https://supadata.ai/about\n- To crawl entire website, use top-level URL like https://supadata.ai\n\n**Usage Example:**\n```json\n{\n "name": "supadata_crawl",\n "arguments": {\n "url": "https://example.com",\n "limit": 100\n }\n}\n```\n\n**Returns:** Job ID for status checking. Use supadata_check_crawl_status to check progress.\n**Job Status:** Possible statuses are \'scraping\', \'completed\', \'failed\', or \'cancelled\'\n\n**Important:** Respect robots.txt and website terms of service when crawling web content.', 'parameters': {'type': 'object', 'properties': {'limit': {'type': 'number', 'description': 'Maximum number of pages to crawl (1-5000, default: 100)', 'default': 100, 'minimum': 1, 'maximum': 5000}, 'url': {'type': 'string', 'description': 'URL of the webpage to crawl'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}

supadata

other

{'type': 'function', 'name': 'supadata_map', 'description': 'Crawl a whole website and get all URLs on it using Supadata\'s mapping API.\n\n**Purpose:** Extract all links found on a website for content discovery and sitemap creation.\n**Best for:** Website content discovery, SEO analysis, content aggregation, automated web scraping and indexing.\n**Use cases:** Creating a sitemap, running a crawler to fetch content from all pages of a website.\n\n**Usage Example:**\n```json\n{\n "name": "supadata_map",\n "arguments": {\n "url": "https://example.com"\n }\n}\n```\n\n**Returns:** Array of URLs found on the website.', 'parameters': {'type': 'object', 'properties': {'url': {'type': 'string', 'description': 'URL of the website to map'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}

supadata

other

{'type': 'function', 'name': 'supadata_scrape', 'description': 'Extract content from any web page to Markdown format using Supadata\'s powerful scraping API.\n\n**Purpose:** Single page content extraction with automatic formatting to Markdown.\n**Best for:** When you know exactly which page contains the information you need.\n\n**Usage Example:**\n```json\n{\n "name": "supadata_scrape",\n "arguments": {\n "url": "https://example.com",\n "noLinks": false,\n "lang": "en"\n }\n}\n```\n\n**Returns:** \n- URL of the scraped page\n- Extracted content in Markdown format\n- Page name and description\n- Character count\n- List of URLs found on the page', 'parameters': {'type': 'object', 'properties': {'lang': {'type': 'string', 'description': 'Preferred language for the scraped content (ISO 639-1 code)', 'default': 'en'}, 'noLinks': {'type': 'boolean', 'description': 'When true, removes markdown links from the content', 'default': False}, 'url': {'type': 'string', 'description': 'Web page URL to scrape'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}

supadata

other

{'type': 'function', 'name': 'supadata_transcript', 'description': 'Extract transcript from supported video platforms (YouTube, TikTok, Instagram, Twitter) or file URLs using Supadata\'s transcript API.\n\n**Purpose:** Get transcripts from video content across multiple platforms.\n**Best for:** Video content analysis, subtitle extraction, content indexing.\n\n**Usage Example:**\n```json\n{\n "name": "supadata_transcript",\n "arguments": {\n "url": "https://youtube.com/watch?v=example",\n "lang": "en",\n "text": false,\n "mode": "auto"\n }\n}\n```\n\n**Returns:** \n- Either immediate transcript content\n- Or job ID for asynchronous processing (use supadata_check_transcript_status)\n\n**Supported Platforms:** YouTube, TikTok, Instagram, Twitter, and file URLs', 'parameters': {'type': 'object', 'properties': {'chunkSize': {'type': 'number', 'description': 'Maximum characters per transcript chunk'}, 'lang': {'type': 'string', 'description': 'Preferred language code (ISO 639-1)'}, 'mode': {'type': 'string', 'description': 'Transcript generation mode', 'enum': ['native', 'auto', 'generate']}, 'text': {'type': 'boolean', 'description': 'Return plain text instead of formatted output', 'default': False}, 'url': {'type': 'string', 'description': 'Video or file URL to get transcript from (YouTube, TikTok, Instagram, Twitter, file)'}}, 'required': ['url'], 'additionalProperties': False}, 'strict': True}

suzieq

other

{'type': 'function', 'name': 'run_suzieq_show', 'description': 'Runs a SuzieQ \'show\' query via its REST API.\n\n Args:\n table: The name of the SuzieQ table to query (e.g., \'device\', \'bgp\', \'interface\', \'route\').\n filters: An optional dictionary of filter parameters for the SuzieQ query\n (e.g., {"hostname": "leaf01", "vrf": "default", "state": "Established"}).\n Keys should match SuzieQ filter names. Values can be strings or lists of strings.\n If no filters are needed, this can be None, null, or an empty dictionary.\n\n Returns:\n A JSON string representing the result from the SuzieQ API, or a JSON string with an error message.', 'parameters': {'type': 'object', 'properties': {'filters': {'title': 'Filters', 'default': None, 'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}]}, 'table': {'type': 'string', 'title': 'Table'}}, 'required': ['table'], 'additionalProperties': False}, 'strict': True}

suzieq

other

{'type': 'function', 'name': 'run_suzieq_summarize', 'description': 'Runs a SuzieQ \'summarize\' query via its REST API.\n\n Args:\n table: The name of the SuzieQ table to summarize (e.g., \'device\', \'bgp\', \'interface\', \'route\').\n filters: An optional dictionary of filter parameters for the SuzieQ query\n (e.g., {"hostname": "leaf01", "vrf": "default"}).\n Keys should match SuzieQ filter names. Values can be strings or lists of strings.\n If no filters are needed, this can be None, null, or an empty dictionary.\n\n Returns:\n A JSON string representing the summarized result from the SuzieQ API,\n or a JSON string with an error message.', 'parameters': {'type': 'object', 'properties': {'filters': {'title': 'Filters', 'default': None, 'anyOf': [{'type': 'object', 'additionalProperties': True}, {'type': 'null'}]}, 'table': {'type': 'string', 'title': 'Table'}}, 'required': ['table'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'add_section', 'description': 'Adds a section to a task, feature, or project.\n \n ## Purpose\n \n Sections store detailed content for tasks, features, and projects in a structured way.\n Instead of storing all content directly in the entities, sections allow for\n organized content blocks with specific formats and purposes. This approach\n optimizes context efficiency by keeping core entities lightweight.\n \n ## Usage Guidelines\n \n **EFFICIENCY RECOMMENDATION**: For adding multiple sections at once, prefer using \n `bulk_create_sections` instead of multiple `add_section` calls. This is especially \n important for:\n - Creating initial section sets for new tasks/features\n - Adding sections with shorter content (reduces network overhead)\n - Template-like section creation scenarios\n \n **WHEN TO USE add_section**:\n - Adding a single section with substantial content\n - Adding sections incrementally during task development\n - Creating sections that require careful individual validation\n \n ## Content Organization Strategy\n \n **Common Section Types** (use these title patterns for consistency):\n - **Requirements**: What needs to be accomplished, acceptance criteria\n - **Implementation Notes**: Technical approach, architecture decisions\n - **Testing Strategy**: Testing approach, coverage requirements\n - **Reference Information**: External links, documentation, resources\n - **Dependencies**: Prerequisites, related tasks, blocking issues\n - **Architecture**: Design patterns, system integration points\n \n **Ordinal Sequencing Best Practices**:\n - Start with ordinal 0 for the first section\n - Use increments of 1 for logical ordering\n - Leave gaps (0, 10, 20) when you anticipate inserting sections later\n - Requirements typically come first (ordinal 0)\n - Implementation details in the middle (ordinal 1-5)\n - Testing and validation toward the end (ordinal 6+)\n \n **Content Format Selection**:\n - **MARKDOWN**: Default for documentation, requirements, notes (rich formatting)\n - **PLAIN_TEXT**: Simple text without formatting needs\n - **JSON**: Structured data, configuration, API specifications\n - **CODE**: Source code examples, implementation snippets\n \n ## Integration with Workflow\n \n **Template Integration**: When using templates, they create standard sections automatically.\n Use add_section to supplement template-created sections with project-specific content.\n \n **Progressive Detail**: Start with high-level sections (Requirements, Architecture) \n and add implementation details as the task progresses.\n \n ## Parameters\n \n | Parameter | Type | Required | Default | Description |\n |-----------|------|----------|---------|-------------|\n | entityType | string | Yes | - | Type of entity to attach this section to: \'PROJECT\', \'TASK\', or \'FEATURE\' |\n | entityId | UUID string | Yes | - | ID of the project, task, or feature to add the section to (e.g., \'550e8400-e29b-41d4-a716-446655440000\') |\n | title | string | Yes | - | Section title (e.g., \'Requirements\', \'Implementation Notes\', \'Testing Plan\') |\n | usageDescription | string | Yes | - | Description of how this section should be used by AI models or users |\n | content | string | Yes | - | The actual content of the section in the specified format |\n | contentFormat | string | No | "MARKDOWN" | Format of the content: \'MARKDOWN\', \'PLAIN_TEXT\', \'JSON\', or \'CODE\' |\n | ordinal | integer | Yes | - | Order position (0-based). Lower numbers appear first when ordered. |\n | tags | string | No | - | Comma-separated list of tags for categorization (e.g., \'documentation,frontend,api\') |\n \n ## Response Format\n \n ### Success Response\n \n ```json\n {\n "success": true,\n "message": "Section added successfully",\n "data": {\n "section": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "entityType": "TASK",\n "entityId": "661f9511-f30c-52e5-b827-557766551111",\n "title": "Implementation Steps",\n "contentFormat": "MARKDOWN",\n "ordinal": 1,\n "createdAt": "2025-05-10T14:30:00Z"\n }\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 provided parameters fail validation\n ```json\n {\n "success": false,\n "message": "Title is required",\n "error": {\n "code": "VALIDATION_ERROR"\n }\n }\n ```\n \n - DATABASE_ERROR (500): When there\'s an issue storing the section in the database\n \n - INTERNAL_ERROR (500): For unexpected system errors during execution\n \n ## Usage Examples\n \n 1. Add a requirements section to a task:\n ```json\n {\n "entityType": "TASK",\n "entityId": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Requirements",\n "usageDescription": "Key requirements that the implementation must satisfy",\n "content": "1. Must support OAuth2 authentication\\\\n2. Should handle token refresh\\\\n3. Needs rate limiting",\n "contentFormat": "MARKDOWN",\n "ordinal": 0,\n "tags": "requirements,security,api"\n }\n ```\n \n 2. Add implementation notes to a feature:\n ```json\n {\n "entityType": "FEATURE",\n "entityId": "661e8511-f30c-41d4-a716-557788990000",\n "title": "Implementation Notes",\n "usageDescription": "Technical details on implementation approach",\n "content": "Use the AuthLib 2.0 library for OAuth implementation...",\n "contentFormat": "MARKDOWN",\n "ordinal": 1,\n "tags": "implementation,technical"\n }\n ```\n \n 3. Add overview documentation to a project:\n ```json\n {\n "entityType": "PROJECT",\n "entityId": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Project Overview",\n "usageDescription": "High-level overview of the project",\n "content": "This project aims to create a scalable infrastructure...",\n "contentFormat": "MARKDOWN",\n "ordinal": 0,\n "tags": "overview,documentation"\n }\n ```\n \n 3. Add structured data as JSON:\n ```json\n {\n "entityType": "FEATURE",\n "entityId": "661e8511-f30c-41d4-a716-557788990000",\n "title": "API Endpoints",\n "usageDescription": "Definition of REST API endpoints",\n "content": "{\\\\"endpoints\\\\": [{\\\\"path\\\\": \\\\"/api/auth\\\\", \\\\"method\\\\": \\\\"POST\\\\"}]}",\n "contentFormat": "JSON",\n "ordinal": 0\n }\n ```\n \n 4. Add code sample:\n ```json\n {\n "entityType": "TASK",\n "entityId": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Authentication Handler",\n "usageDescription": "Code for handling OAuth authentication",\n "content": "fun authenticateUser(credentials: Credentials): Result<User> {\\n // Implementation\\n}",\n "contentFormat": "CODE",\n "ordinal": 2\n }\n ```\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\n \n ## Related Tools\n \n - `get_sections`: Retrieve sections for a task or feature\n - `update_section`: Modify an existing section\n - `delete_section`: Remove a section\n - `bulk_create_sections`: Create multiple sections at once (recommended when adding multiple sections)\n \n ## Efficiency Note\n \n For efficiency and better performance, when you need to add multiple sections to the \n same entity, use the `bulk_create_sections` tool instead. This reduces the number of\n database operations and network calls, resulting in faster execution, especially when\n dealing with multiple sections with shorter content.', 'parameters': {'type': 'object', 'properties': {'content': {'type': 'string', 'description': 'The actual content of the section in the specified format'}, 'contentFormat': {'type': 'string', 'description': "Format of the content: 'MARKDOWN' for formatted text, 'PLAIN_TEXT' for unformatted text, 'JSON' for data, 'CODE' for source code", 'default': 'MARKDOWN', 'enum': ['PLAIN_TEXT', 'MARKDOWN', 'JSON', 'CODE']}, 'entityId': {'type': 'string', 'description': "ID (UUID) of the project, task, or feature to add the section to (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'entityType': {'type': 'string', 'description': "Type of entity to attach this section to: 'PROJECT', 'TASK', or 'FEATURE'", 'enum': ['PROJECT', 'FEATURE', 'TASK', 'TEMPLATE', 'SECTION']}, 'ordinal': {'type': 'integer', 'description': 'Order position (0-based). Lower numbers appear first when ordered.', 'minimum': 0}, 'tags': {'type': 'string', 'description': "Comma-separated list of tags for categorization (e.g., 'documentation,frontend,api')"}, 'title': {'type': 'string', 'description': "Section title (e.g., 'Requirements', 'Implementation Notes', 'Testing Plan')"}, 'usageDescription': {'type': 'string', 'description': 'Description of how this section should be used by AI models or users'}}, 'required': ['entityType', 'entityId', 'title', 'usageDescription', 'content', 'ordinal'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'add_template_section', 'description': 'Add a section to a template.\n \n Templates define a structured documentation pattern with multiple sections.\n This tool adds a section definition to a template, which will be created\n when the template is applied to tasks or features.\n \n Example successful response:\n {\n "success": true,\n "message": "Template section added successfully",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "templateId": "661e8511-f30c-41d4-a716-557788990000",\n "title": "Implementation Steps",\n "usageDescription": "Detailed steps to implement this task",\n "contentSample": "1. First step\\\\n2. Second step\\\\n3. Third step",\n "contentFormat": "markdown",\n "ordinal": 1,\n "isRequired": true,\n "tags": ["implementation", "steps"]\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation\n - RESOURCE_NOT_FOUND: When the template doesn\'t exist\n - DATABASE_ERROR: When there\'s an issue storing the section\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'contentFormat': {'type': 'string', 'description': 'Format of the content', 'default': 'MARKDOWN', 'enum': ['PLAIN_TEXT', 'MARKDOWN', 'JSON', 'CODE']}, 'contentSample': {'type': 'string', 'description': 'Sample content that will be used when creating from the template'}, 'isRequired': {'type': 'boolean', 'description': 'Whether this section is required when applying the template', 'default': False}, 'ordinal': {'type': 'integer', 'description': 'Order position (0-based). Lower numbers appear first when ordered.', 'minimum': 0}, 'tags': {'type': 'string', 'description': 'Comma-separated list of tags for categorization'}, 'templateId': {'type': 'string', 'description': 'The unique ID of the template to add the section to', 'format': 'uuid'}, 'title': {'type': 'string', 'description': "Section title (e.g., 'Requirements', 'Implementation Notes', 'Testing Plan')"}, 'usageDescription': {'type': 'string', 'description': 'Description of how this section should be used by AI models or users'}}, 'required': ['templateId', 'title', 'usageDescription', 'contentSample', 'ordinal'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'apply_template', 'description': 'Apply one or more templates to create sections for a task or feature.\n \n ## Purpose\n Templates provide standardized structure for task and feature documentation.\n This tool applies templates to an entity, creating sections based on template section definitions.\n \n ## Template Application Strategies\n \n **Multiple Template Support**:\n - Apply multiple templates in single operation using templateIds array\n - Templates applied in array order (later templates\' sections appear after earlier ones)\n - Use single-item array for one template: ["template-uuid"]\n - Use multiple templates for comprehensive coverage: ["uuid1", "uuid2", "uuid3"]\n \n **Template Combination Patterns**:\n The template system is organized into composable categories:\n \n **AI Workflow Instructions** (process guidance):\n - Local Git Branching Workflow, GitHub PR Workflow\n - Task Implementation Workflow, Bug Investigation Workflow\n \n **Documentation Properties** (information capture):\n - Technical Approach, Requirements Specification, Context & Background\n \n **Process & Quality** (standards and completion):\n - Testing Strategy, Definition of Done\n \n **Recommended Combinations**:\n - **Development Task**: Technical Approach + Task Implementation Workflow + Testing Strategy\n - **Bug Fix**: Bug Investigation Workflow + Technical Approach + Definition of Done\n - **Feature Planning**: Requirements Specification + Context & Background + Testing Strategy\n - **Complex Implementation**: Technical Approach + Local Git Branching + GitHub PR + Definition of Done\n \n ## Context Efficiency Techniques\n \n **ALWAYS PREFER** direct creation with templates over separate operations:\n ```\n // EFFICIENT\n create_task(title: "X", templateIds: ["Y"])\n \n // LESS EFFICIENT \n id = create_task(title: "X")\n apply_template(entityId: id, templateIds: ["Y"])\n ```\n \n **Multiple Templates in One Call**:\n ```\n // EFFICIENT\n apply_template(entityId: id, templateIds: ["A", "B", "C"])\n \n // LESS EFFICIENT\n apply_template(entityId: id, templateIds: ["A"])\n apply_template(entityId: id, templateIds: ["B"]) \n apply_template(entityId: id, templateIds: ["C"])\n ```\n \n **Template Sequence Optimization**:\n 1. Start with Context: Context & Background, Requirements Specification\n 2. Add Technical Detail: Technical Approach for implementation guidance \n 3. Include Process Guidance: Task Implementation, Bug Investigation workflows\n 4. Add Git Workflow: Local Git Branching, GitHub PR workflows\n 5. Ensure Quality: Testing Strategy, Definition of Done\n \n You can apply one or more templates by providing a templateIds array parameter.\n Use a single-item array for applying just one template.\n \n Example successful response for a single template:\n {\n "success": true,\n "message": "Template applied successfully, created 3 sections",\n "data": {\n "templateId": "550e8400-e29b-41d4-a716-446655440000",\n "entityType": "TASK",\n "entityId": "661e8511-f30c-41d4-a716-557788990000",\n "sectionsCreated": 3,\n "sections": [\n {\n "id": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Requirements",\n "ordinal": 0\n },\n {\n "id": "882f9733-h52e-63f6-c938-779900212222",\n "title": "Implementation Notes",\n "ordinal": 1\n },\n {\n "id": "993f0844-i63f-74g7-d049-8800a1323333",\n "title": "Testing Strategy",\n "ordinal": 2\n }\n ]\n }\n }\n \n Example successful response for multiple templates:\n {\n "success": true,\n "message": "Applied 2 templates successfully, created 5 sections",\n "data": {\n "entityType": "TASK",\n "entityId": "661e8511-f30c-41d4-a716-557788990000",\n "totalSectionsCreated": 5,\n "appliedTemplates": [\n {\n "templateId": "550e8400-e29b-41d4-a716-446655440000",\n "sectionsCreated": 3,\n "sections": [\n {\n "id": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Requirements",\n "ordinal": 0\n },\n {\n "id": "882f9733-h52e-63f6-c938-779900212222",\n "title": "Implementation Notes",\n "ordinal": 1\n },\n {\n "id": "993f0844-i63f-74g7-d049-8800a1323333",\n "title": "Testing Strategy",\n "ordinal": 2\n }\n ]\n },\n {\n "templateId": "661e8511-f30c-41d4-a716-557788990000",\n "sectionsCreated": 2,\n "sections": [\n {\n "id": "772f9622-g41d-52e5-b827-668899101112",\n "title": "Design Documentation",\n "ordinal": 3\n },\n {\n "id": "882f9733-h52e-63f6-c938-779900212223",\n "title": "Related Tasks",\n "ordinal": 4\n }\n ]\n }\n ]\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation\n - RESOURCE_NOT_FOUND: When the template or entity doesn\'t exist\n - DATABASE_ERROR: When there\'s an issue applying the template\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'entityId': {'type': 'string', 'description': 'ID of the entity to apply the template to', 'format': 'uuid'}, 'entityType': {'type': 'string', 'description': 'Type of entity (TASK or FEATURE)', 'enum': ['TASK', 'FEATURE']}, 'templateIds': {'type': 'array', 'description': 'List of template IDs to apply. Use a single-item array for applying just one template.', 'items': {'type': 'string', 'format': 'uuid'}}}, 'required': ['entityType', 'entityId', 'templateIds'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'bulk_create_sections', 'description': 'Creates multiple sections in a single operation.\n \n ## Purpose\n \n This tool efficiently creates multiple sections for tasks, features, or projects in a single operation.\n PREFERRED over multiple `add_section` calls for efficiency and performance.\n \n ## When to Use bulk_create_sections\n \n **ALWAYS PREFER** for:\n - Creating initial section sets for new tasks/features (3+ sections)\n - Adding template-like section structures\n - Sections with shorter content (< 500 characters each)\n - Any scenario requiring multiple sections for the same entity\n \n **Performance Benefits**:\n - Single database transaction (atomic operation)\n - Reduced network overhead (one API call vs multiple)\n - Faster execution for multiple sections\n - Better error handling (all succeed or fail together)\n \n ## Common Section Creation Patterns\n \n **Standard Task Documentation Set**:\n ```json\n {\n "sections": [\n {\n "entityType": "TASK",\n "entityId": "task-uuid",\n "title": "Requirements",\n "usageDescription": "Key requirements and acceptance criteria",\n "content": "[List specific requirements and success criteria]",\n "ordinal": 0,\n "tags": "requirements,core"\n },\n {\n "entityType": "TASK",\n "entityId": "task-uuid",\n "title": "Technical Approach",\n "usageDescription": "Implementation strategy and architecture",\n "content": "[Describe technical approach and key decisions]",\n "ordinal": 1,\n "tags": "technical,architecture"\n },\n {\n "entityType": "TASK",\n "entityId": "task-uuid",\n "title": "Testing Strategy",\n "usageDescription": "Testing approach and coverage requirements",\n "content": "[Define testing strategy and success criteria]",\n "ordinal": 2,\n "tags": "testing,quality"\n }\n ]\n }\n ```\n \n **Feature Planning Documentation**:\n ```json\n {\n "sections": [\n {\n "entityType": "FEATURE",\n "entityId": "feature-uuid",\n "title": "Business Context",\n "usageDescription": "Business value and user impact",\n "content": "[Explain business need and user benefits]",\n "ordinal": 0,\n "tags": "business,context"\n },\n {\n "entityType": "FEATURE",\n "entityId": "feature-uuid",\n "title": "Feature Specification",\n "usageDescription": "Detailed feature requirements and behavior",\n "content": "[Define feature scope and detailed requirements]",\n "ordinal": 1,\n "tags": "requirements,specification"\n }\n ]\n }\n ```\n \n ## Section Organization Best Practices\n \n **Ordinal Sequencing**:\n - Start with ordinal 0 for the first section\n - Use increments of 1 for tightly related sequences\n - Leave gaps (0, 10, 20) when you might insert sections later\n - Order logically: Context → Requirements → Implementation → Testing\n \n **Content Format Selection**:\n - **MARKDOWN**: Default for rich text, documentation, requirements\n - **PLAIN_TEXT**: Simple text without formatting needs\n - **JSON**: Structured data, API specs, configuration\n - **CODE**: Implementation examples, code snippets\n \n **Tagging Strategy**:\n - Use consistent tags across similar section types\n - Include functional area: "requirements", "testing", "architecture"\n - Add technical context: "api", "database", "frontend", "security"\n - Mark importance: "core", "optional", "critical"\n \n ## Integration with Templates\n \n **Templates vs Manual Sections**:\n - Templates provide standardized section structures automatically\n - Use bulk_create_sections to supplement template sections with project-specific content\n - Templates handle common patterns; bulk_create_sections handles custom needs\n \n **Post-Template Enhancement**:\n After applying templates, use bulk_create_sections to add:\n - Project-specific context sections\n - Additional technical details\n - Custom workflow or process sections\n - Domain-specific requirements or constraints\n \n ## Parameters\n \n | Parameter | Type | Required | Default | Description |\n |-----------|------|----------|---------|-------------|\n | sections | array | Yes | - | Array of section objects to create |\n \n Each section object in the array must include:\n \n | Field | Type | Required | Default | Description |\n |-------|------|----------|---------|-------------|\n | entityType | string | Yes | - | Type of entity: \'PROJECT\', \'TASK\', or \'FEATURE\' |\n | entityId | UUID string | Yes | - | ID of the project, task, or feature to add the section to |\n | title | string | Yes | - | Section title (e.g., \'Requirements\', \'Implementation Notes\') |\n | usageDescription | string | Yes | - | Description of how this section should be used |\n | content | string | Yes | - | The actual content of the section |\n | contentFormat | string | No | "MARKDOWN" | Format of the content: \'MARKDOWN\', \'PLAIN_TEXT\', \'JSON\', or \'CODE\' |\n | ordinal | integer | Yes | - | Order position (0-based). Lower numbers appear first. |\n | tags | string | No | - | Comma-separated list of tags for categorization |\n \n ## Response Format\n \n ### Success Response (All Sections Created)\n \n ```json\n {\n "success": true,\n "message": "3 sections created successfully",\n "data": {\n "items": [\n {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "entityType": "task",\n "entityId": "661f9511-f30c-52e5-b827-557766551111",\n "title": "Requirements",\n "contentFormat": "markdown",\n "ordinal": 0,\n "createdAt": "2025-05-10T14:30:00Z"\n }\n ],\n "count": 3,\n "failed": 0\n }\n }\n ```\n \n ## Error Responses\n \n - VALIDATION_ERROR (400): When the input doesn\'t match the expected format or values are invalid\n - OPERATION_FAILED (500): When all sections fail to create\n - RESOURCE_NOT_FOUND (404): When an entity doesn\'t exist\n \n ## Usage Examples\n \n 1. Create multiple sections for a task:\n ```json\n {\n "sections": [\n {\n "entityType": "TASK",\n "entityId": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Requirements",\n "usageDescription": "Key requirements for implementation",\n "content": "1. Must support user authentication\\n2. Should integrate with existing systems",\n "contentFormat": "MARKDOWN",\n "ordinal": 0,\n "tags": "requirements,core"\n },\n {\n "entityType": "TASK",\n "entityId": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Technical Approach",\n "usageDescription": "Implementation strategy and technical details",\n "content": "We\'ll use Spring Security for authentication and implement REST endpoints...",\n "contentFormat": "MARKDOWN",\n "ordinal": 1,\n "tags": "technical,implementation"\n },\n {\n "entityType": "TASK",\n "entityId": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Testing Strategy",\n "usageDescription": "Test approach and coverage requirements",\n "content": "Ensure 80% unit test coverage and implement integration tests for key flows",\n "contentFormat": "MARKDOWN",\n "ordinal": 2,\n "tags": "testing,quality"\n }\n ]\n }\n ```\n \n 2. Create multiple sections for a project:\n ```json\n {\n "sections": [\n {\n "entityType": "PROJECT",\n "entityId": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Project Overview",\n "usageDescription": "High-level description of the project",\n "content": "This project aims to create a scalable infrastructure...",\n "contentFormat": "MARKDOWN",\n "ordinal": 0,\n "tags": "overview,documentation"\n },\n {\n "entityType": "PROJECT",\n "entityId": "772f9622-g41d-52e5-b827-668899101111",\n "title": "Project Architecture",\n "usageDescription": "Technical architecture details",\n "content": "The project uses a modular architecture with the following components...",\n "contentFormat": "MARKDOWN",\n "ordinal": 1,\n "tags": "architecture,technical"\n }\n ]\n }\n ```\n \n ## Performance Benefits\n \n Using `bulk_create_sections` instead of multiple calls to `add_section` offers significant \n advantages:\n \n 1. Reduced network overhead: Only one API call instead of multiple calls\n 2. Improved transaction efficiency: Database operations are batched\n 3. Faster execution: Creating multiple sections in parallel\n 4. Atomic operations: All sections succeed or useful error information is provided\n \n ## Common Section Combinations\n \n Typical section combinations for tasks include:\n \n 1. Requirements + Implementation Approach + Testing Strategy\n 2. Problem Statement + Solution Design + Acceptance Criteria\n 3. Context + Technical Details + References', 'parameters': {'type': 'object', 'properties': {'sections': {'type': 'array', 'description': 'Array of sections to create', 'items': {'type': 'object', 'required': ['entityType', 'entityId', 'title', 'usageDescription', 'content', 'ordinal'], 'properties': {'content': {'type': 'string', 'description': 'Section content'}, 'contentFormat': {'type': 'string', 'description': 'Format of the content', 'default': 'MARKDOWN', 'enum': ['PLAIN_TEXT', 'MARKDOWN', 'JSON', 'CODE']}, 'entityId': {'type': 'string', 'description': 'ID of the project, task, or feature', 'format': 'uuid'}, 'entityType': {'type': 'string', 'description': 'Type of entity (PROJECT, TASK, or FEATURE)', 'enum': ['PROJECT', 'FEATURE', 'TASK', 'TEMPLATE', 'SECTION']}, 'ordinal': {'type': 'integer', 'description': 'Order position (0-based)', 'minimum': 0}, 'tags': {'type': 'string', 'description': 'Comma-separated list of tags'}, 'title': {'type': 'string', 'description': 'Section title'}, 'usageDescription': {'type': 'string', 'description': 'Guidance for LLMs on how to use this content'}}}}}, 'required': ['sections'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'bulk_delete_sections', 'description': 'Deletes multiple sections in a single operation', 'parameters': {'type': 'object', 'properties': {'hardDelete': {'type': 'boolean', 'description': 'Whether to permanently delete the sections (true) or soft delete them (false)', 'default': False}, 'ids': {'type': 'array', 'description': 'Array of section IDs to delete', 'items': {'type': 'string', 'description': 'Section ID', 'format': 'uuid'}}}, 'required': ['ids'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'bulk_update_sections', 'description': 'Updates multiple sections in a single operation', 'parameters': {'type': 'object', 'properties': {'sections': {'type': 'array', 'description': 'Array of sections to update', 'items': {'type': 'object', 'required': ['id'], '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': ['sections'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'create_dependency', 'description': 'Creates a new task dependency with validation for task existence, cycle detection, and duplicate prevention.\n \n Dependencies represent relationships between tasks that can affect execution planning and workflow management.\n This tool ensures data integrity by validating all aspects before creation.\n \n Example successful response:\n {\n "success": true,\n "message": "Dependency created successfully",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "fromTaskId": "661e8511-f30c-41d4-a716-557788990000",\n "toTaskId": "772f9622-g41d-52e5-b827-668899101111",\n "type": "BLOCKS",\n "createdAt": "2025-05-10T14:30:00Z"\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation\n - RESOURCE_NOT_FOUND: When one or both tasks don\'t exist\n - CONFLICT_ERROR: When the dependency would create a cycle or already exists\n - DATABASE_ERROR: When there\'s an issue storing the dependency\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'fromTaskId': {'type': 'string', 'description': 'ID of the source task (the task that creates the dependency)', 'format': 'uuid'}, 'toTaskId': {'type': 'string', 'description': 'ID of the target task (the task that is affected by the dependency)', 'format': 'uuid'}, 'type': {'type': 'string', 'description': "Type of dependency: 'BLOCKS' (source blocks target), 'IS_BLOCKED_BY' (source is blocked by target), or 'RELATES_TO' (general relationship)", 'default': 'BLOCKS', 'enum': ['BLOCKS', 'IS_BLOCKED_BY', 'RELATES_TO']}}, 'required': ['fromTaskId', 'toTaskId'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'create_feature', 'description': 'Create a new feature with required and optional fields.\n \n ## Purpose\n Features provide higher-level organization for related tasks, representing coherent\n functionality or project components. They bridge the gap between individual tasks\n and overall project goals.\n \n ## Feature vs Task Decision Guide\n \n **Create a Feature when**:\n - Work involves multiple related tasks (3+ tasks)\n - Functionality represents a user-facing feature or system component\n - Work has distinct phases (planning, development, testing, deployment)\n - Multiple developers or skill sets are involved\n - Work has independent business value or can be delivered as a unit\n \n **Use Direct Tasks when**:\n - Work is a single, focused implementation\n - Maintenance, bug fixes, or small enhancements\n - Infrastructure or tooling improvements\n - Work doesn\'t logically group with other tasks\n \n ## Template Integration Strategy\n \n **RECOMMENDED**: Apply templates at creation for consistent documentation structure.\n \n **Feature-Level Templates** (use `list_templates` with targetEntityType="FEATURE"):\n - Context & Background: Project context and business requirements\n - Requirements Specification: Detailed functional and non-functional requirements\n - Technical Approach: High-level architecture and technical strategy\n \n **Template Combinations for Features**:\n - **Planning Phase**: Context & Background + Requirements Specification\n - **Technical Phase**: Requirements Specification + Technical Approach\n - **Comprehensive**: All three templates for complex features\n \n ## Feature Lifecycle Management\n \n **Status Progression**:\n 1. `planning` - Requirements gathering, design, scope definition\n 2. `in-development` - Active implementation across multiple tasks\n 3. `completed` - All associated tasks completed, feature delivered\n 4. `archived` - Feature complete and no longer under active development\n \n **Priority Guidelines**:\n - `high`: Core functionality, user-facing features, business critical\n - `medium`: Important enhancements, internal tools, performance improvements\n - `low`: Nice-to-have features, experimental functionality\n \n ## Organizing Tasks Under Features\n \n **After creating a feature**, use the featureId in `create_task` to associate tasks:\n ```json\n {\n "title": "Implement OAuth Login",\n "summary": "Create OAuth authentication endpoints",\n "featureId": "feature-uuid-here",\n "templateIds": ["task-template-uuid"]\n }\n ```\n \n **Task Organization Patterns**:\n - **Frontend + Backend**: Separate tasks for UI and API implementation\n - **By Component**: Database, API, UI, Tests as separate tasks\n - **By Phase**: Research, Implementation, Testing, Documentation\n - **By Complexity**: Break large features into manageable task chunks\n \n ## Integration with Project Hierarchy\n \n **Project → Features → Tasks** hierarchy:\n - Use projectId to associate feature with a project\n - Features group related functionality within a project\n - Tasks represent specific implementation work within features\n \n ## Best Practices\n \n **Naming Conventions**:\n - Use noun phrases describing functionality: "User Authentication", "Payment Processing"\n - Avoid implementation details in names: "OAuth Integration" not "Implement OAuth"\n - Be specific enough to distinguish from other features\n \n **Summary Guidelines**:\n - Include business value and user impact\n - Mention key technical components or integrations\n - Define success criteria or completion indicators\n - Keep scope clear and bounded\n \n **Tagging Strategy**:\n - Include functional area: "authentication", "payments", "reporting"\n - Add technical stack: "frontend", "backend", "database", "api"\n - Mark business importance: "core", "enhancement", "experimental"\n - Include user-facing impact: "user-experience", "admin-tools", "internal"\n \n Example successful response:\n {\n "success": true,\n "message": "Feature created successfully with 2 template(s) applied, creating 5 section(s)",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "name": "User Authentication System",\n "summary": "Complete user authentication system with OAuth 2.0, JWT tokens, and social login integration. Provides secure user registration, login, password reset, and session management.",\n "status": "planning",\n "priority": "high",\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T14:30:00Z",\n "tags": ["core", "authentication", "security", "user-experience", "oauth"],\n "appliedTemplates": [\n {\n "templateId": "context-background-uuid",\n "sectionsCreated": 2\n },\n {\n "templateId": "requirements-spec-uuid",\n "sectionsCreated": 3\n }\n ]\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation (empty name/summary)\n - RESOURCE_NOT_FOUND: When specified projectId or templateIds don\'t exist\n - DATABASE_ERROR: When there\'s an issue storing the feature or applying templates\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'name': {'type': 'string', 'description': "Required feature name (e.g., 'User Authentication', 'Data Export')"}, 'priority': {'type': 'string', 'description': "Priority level. Valid values: 'high', 'medium', 'low'", 'default': 'medium', 'enum': ['high', 'medium', 'low']}, 'projectId': {'type': 'string', 'description': "Optional UUID of the project this feature belongs to (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'status': {'type': 'string', 'description': "Feature status. Valid values: 'planning', 'in-development', 'completed', 'archived'", 'default': 'planning', 'enum': ['planning', 'in-development', 'completed', 'archived']}, 'summary': {'type': 'string', 'description': 'Required feature summary describing its purpose and scope'}, 'tags': {'type': 'string', 'description': "Comma-separated list of tags for categorization (e.g., 'frontend,ui,critical')"}, 'templateIds': {'type': 'array', 'description': 'List of template IDs to apply. Use a single-item array for applying just one template.', 'items': {'type': 'string', 'format': 'uuid'}}}, 'required': ['name', 'summary'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'create_project', 'description': 'Implement the CreateProjectTool MCP tool for creating new projects. Define parameter schema and validation for all required and optional fields (name, summary, status, tags). Implement tool execution logic to create and persist project entities.\n \n This tool creates a new Project entity in the MCP Task Orchestrator system. Projects are top-level organizational containers that can group related features and tasks together. Each project requires a name and summary, and can optionally include status information and tags for categorization.\n \n Projects provide a higher level of organization above features, allowing you to manage work across multiple features and their related tasks.\n \n Example successful response:\n {\n "success": true,\n "message": "Project created successfully",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "name": "Mobile App Redesign",\n "summary": "Complete redesign of the mobile application with improved UI/UX",\n "status": "planning",\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T14:30:00Z",\n "tags": ["mobile", "ui", "2025-roadmap"]\n },\n "error": null,\n "metadata": {\n "timestamp": "2025-05-10T14:30:00Z"\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation\n - DATABASE_ERROR: When there\'s an issue storing the project\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'name': {'type': 'string', 'description': "Project name (e.g., 'Mobile App Redesign', 'Backend API')"}, 'status': {'type': 'string', 'description': "Project status. Valid values: 'planning', 'in-development', 'completed', 'archived'", 'default': 'planning', 'enum': ['planning', 'in-development', 'completed', 'archived']}, 'summary': {'type': 'string', 'description': 'Project description explaining its purpose and scope'}, 'tags': {'type': 'string', 'description': "Comma-separated list of tags for categorization (e.g., 'frontend,mobile,2025-roadmap')"}}, 'required': ['name', 'summary'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'create_task', 'description': 'Creates a new task with the specified properties.\n \n ## Purpose\n Tasks are the primary work items in the system and can be organized into Features.\n Each task has basic metadata (title, status, etc.) and can have Sections for detailed content.\n \n ## Template Integration\n RECOMMENDED: Apply templates at creation time using templateIds parameter for consistent\n documentation structure. Use `list_templates` first to find appropriate templates.\n \n Template application creates standardized sections automatically:\n - Use single-item array for one template: ["template-uuid"]\n - Use multiple templates for comprehensive coverage: ["uuid1", "uuid2"]\n - Templates are applied in order, with later templates\' sections appearing after earlier ones\n \n ## Best Practices\n - Use descriptive titles that clearly indicate the work to be done\n - Write comprehensive summaries with acceptance criteria when helpful\n - Set appropriate complexity ratings (1=trivial, 10=highly complex)\n - Use consistent tagging conventions (e.g., "task-type-feature", "task-type-bug")\n - Associate with features when the task is part of larger functionality\n - Apply templates that match the work type (implementation, testing, documentation)\n \n ## Entity Relationships\n - Tasks can belong to Features (use featureId to establish relationship)\n - Tasks can belong to Projects (use projectId for top-level organization)\n - Use dependencies to link related tasks (see create_dependency tool)\n \n ## Workflow Integration\n Tasks integrate with the complete project management workflow:\n 1. Start with get_overview to understand current work\n 2. Create task with appropriate templates and metadata\n 3. Use add_section or bulk_create_sections for additional content\n 4. Update status as work progresses (pending → in_progress → completed)\n 5. Create dependencies between related tasks\n \n Example successful response:\n {\n "success": true,\n "message": "Task created successfully with 2 template(s) applied, creating 6 section(s)",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "title": "Implement OAuth Authentication API",\n "summary": "Create secure API endpoints for OAuth 2.0 authentication with JWT tokens",\n "status": "pending",\n "priority": "high",\n "complexity": 8,\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T14:30:00Z",\n "featureId": "661e8511-f30c-41d4-a716-557788990000",\n "tags": ["task-type-feature", "oauth", "authentication", "api", "security"],\n "appliedTemplates": [\n {\n "templateId": "technical-approach-uuid",\n "sectionsCreated": 3\n },\n {\n "templateId": "implementation-workflow-uuid",\n "sectionsCreated": 3\n }\n ]\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation (empty title/summary, invalid UUIDs)\n - RESOURCE_NOT_FOUND: When specified featureId, projectId, or templateIds don\'t exist\n - DATABASE_ERROR: When there\'s an issue storing the task or applying templates\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'complexity': {'type': 'integer', 'description': 'Task complexity on a scale from 1-10 (1=simplest, 10=most complex)', 'default': 5, 'minimum': 1, 'maximum': 10}, 'featureId': {'type': 'string', 'description': "Optional UUID of the feature this task belongs to (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'priority': {'type': 'string', 'description': "Task priority. Valid values: 'high', 'medium', 'low'", 'default': 'medium', 'enum': ['high', 'medium', 'low']}, 'projectId': {'type': 'string', 'description': "Optional UUID of the project this task belongs to (e.g., '550e8400-e29b-41d4-a716-446655440000')", 'format': 'uuid'}, 'status': {'type': 'string', 'description': "Task status. Valid values: 'pending', 'in-progress', 'completed', 'cancelled', 'deferred'", 'default': 'pending', 'enum': ['pending', 'in_progress', 'completed', 'cancelled', 'deferred']}, 'summary': {'type': 'string', 'description': 'Brief summary of the task content (required for task creation)'}, 'tags': {'type': 'string', 'description': "Comma-separated list of tags for categorization (e.g., 'api,backend,urgent')"}, 'templateIds': {'type': 'array', 'description': 'List of template IDs to apply. Use a single-item array for applying just one template.', 'items': {'type': 'string', 'format': 'uuid'}}, 'title': {'type': 'string', 'description': 'The title of the task (required)'}}, 'required': ['title', 'summary'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'create_template', 'description': 'Creates a new template with required and optional fields.\n \n Templates provide reusable patterns for structuring task and feature documentation.\n Each template has metadata and can contain multiple section definitions.\n \n Example successful response:\n {\n "success": true,\n "message": "Template created successfully",\n "data": {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "name": "User Authentication",\n "description": "Implement secure user authentication system",\n "targetEntityType": "TASK",\n "isBuiltIn": false,\n "isProtected": false,\n "isEnabled": true,\n "createdBy": "Claude",\n "tags": ["security", "login", "user-management"],\n "createdAt": "2025-05-10T14:30:00Z",\n "modifiedAt": "2025-05-10T14:30:00Z"\n }\n }\n \n Common error responses:\n - VALIDATION_ERROR: When provided parameters fail validation\n - CONFLICT_ERROR: When a template with the same name already exists\n - DATABASE_ERROR: When there\'s an issue storing the template\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'createdBy': {'type': 'string', 'description': 'Optional creator identifier (default: null)'}, 'description': {'type': 'string', 'description': 'Required template description explaining its purpose and scope'}, 'isBuiltIn': {'type': 'boolean', 'description': 'Whether this is a built-in template (default: false)', 'default': False}, 'isEnabled': {'type': 'boolean', 'description': 'Whether this template is enabled for use (default: true)', 'default': True}, 'isProtected': {'type': 'boolean', 'description': 'Whether this template is protected from modification (default: false)', 'default': False}, 'name': {'type': 'string', 'description': "Required template name (e.g., 'User Authentication', 'Data Export')"}, 'tags': {'type': 'string', 'description': "Comma-separated list of tags for categorization (e.g., 'frontend,ui,critical')"}, 'targetEntityType': {'type': 'string', 'description': "Type of entity this template is for: 'TASK' or 'FEATURE'", 'enum': ['TASK', 'FEATURE']}}, 'required': ['name', 'description', 'targetEntityType'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'delete_dependency', 'description': 'Deletes task dependencies by dependency ID or by task relationship criteria.\n \n This tool provides flexible dependency deletion capabilities. You can delete dependencies:\n - By specific dependency ID (most precise)\n - By task relationship (fromTaskId and toTaskId with optional type filter)\n - All dependencies for a specific task (using deleteAll parameter)\n \n Example successful response:\n {\n "success": true,\n "message": "Dependency deleted successfully",\n "data": {\n "deletedCount": 1,\n "deletedDependencies": [\n {\n "id": "550e8400-e29b-41d4-a716-446655440000",\n "fromTaskId": "661e8511-f30c-41d4-a716-557788990000",\n "toTaskId": "772f9622-g41d-52e5-b827-668899101111",\n "type": "BLOCKS"\n }\n ]\n }\n }\n \n Common error responses:\n - RESOURCE_NOT_FOUND: When the specified dependency doesn\'t exist\n - VALIDATION_ERROR: When provided parameters fail validation\n - DATABASE_ERROR: When there\'s an issue deleting the dependency\n - INTERNAL_ERROR: For unexpected system errors', 'parameters': {'type': 'object', 'properties': {'deleteAll': {'type': 'boolean', 'description': 'When used with fromTaskId OR toTaskId (not both), deletes all dependencies for that task', 'default': False}, 'fromTaskId': {'type': 'string', 'description': 'ID of the source task (used with toTaskId for relationship-based deletion)', 'format': 'uuid'}, 'id': {'type': 'string', 'description': 'ID of the specific dependency to delete (mutually exclusive with task relationship parameters)', 'format': 'uuid'}, 'toTaskId': {'type': 'string', 'description': 'ID of the target task (used with fromTaskId for relationship-based deletion)', 'format': 'uuid'}, 'type': {'type': 'string', 'description': 'Filter by dependency type when using task relationship deletion (optional)', 'enum': ['BLOCKS', 'IS_BLOCKED_BY', 'RELATES_TO']}}, 'required': [], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'delete_feature', 'description': 'Remove a feature and its associated tasks', 'parameters': {'type': 'object', 'properties': {'cascade': {'type': 'boolean', 'description': 'Whether to delete tasks associated with this feature', 'default': False}, 'force': {'type': 'boolean', 'description': 'Whether to force deletion even with active tasks', 'default': False}, 'hardDelete': {'type': 'boolean', 'description': 'Whether to completely remove the feature from the database', 'default': False}, 'id': {'type': 'string', 'description': 'The unique ID of the feature to delete'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'delete_project', 'description': 'Remove a project and its associated features/tasks', 'parameters': {'type': 'object', 'properties': {'cascade': {'type': 'boolean', 'description': 'Whether to delete all features and tasks associated with this project', 'default': False}, 'force': {'type': 'boolean', 'description': 'Whether to force deletion even with active features or tasks', 'default': False}, 'hardDelete': {'type': 'boolean', 'description': 'Whether to permanently remove the project from the database', 'default': False}, 'id': {'type': 'string', 'description': 'The unique ID of the project to delete'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'delete_section', 'description': 'Deletes a section by its ID', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID of the section to delete', 'format': 'uuid'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'delete_task', 'description': 'Deletes a task by its ID', 'parameters': {'type': 'object', 'properties': {'cascade': {'type': 'boolean', 'description': 'Whether to also delete subtasks', 'default': False}, 'deleteSections': {'type': 'boolean', 'description': 'Whether to also delete associated sections', 'default': True}, 'force': {'type': 'boolean', 'description': 'Whether to delete even if other tasks depend on this one. When true, breaks dependency chains and deletes all associated dependencies.', 'default': False}, 'hardDelete': {'type': 'boolean', 'description': 'Whether to permanently delete the task (true) or soft delete it (false)', 'default': False}, 'id': {'type': 'string', 'description': 'The unique ID of the task to delete', 'format': 'uuid'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'delete_template', 'description': 'Deletes a user-created template. Built-in templates cannot be deleted.\n \n Parameters:\n - id (required): UUID of the template to delete\n - force (optional): Boolean flag to override protection, defaults to false\n \n Validation Rules:\n - Template must exist\n - Built-in templates cannot be deleted\n - If a user attempts to delete a built-in template, they will get back an error message\n instructing them to use \'disable_template\' instead\n \n Example:\n ```json\n {\n "id": "550e8400-e29b-41d4-a716-446655440000"\n }\n ```', 'parameters': {'type': 'object', 'properties': {'force': {'type': 'boolean', 'description': 'Whether to override protection (use with caution)', 'default': False}, 'id': {'type': 'string', 'description': 'The unique ID of the template to delete', 'format': 'uuid'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'disable_template', 'description': 'Disables a template including system templates. Disabled templates are not available for use.\n \n Parameters:\n - id (required): UUID of the template to disable\n \n Validation Rules:\n - Template must exist\n \n Example:\n ```json\n {\n "id": "550e8400-e29b-41d4-a716-446655440000"\n }\n ```', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID of the template to disable', 'format': 'uuid'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}

task-orchestrator

other

{'type': 'function', 'name': 'enable_template', 'description': 'Enables a previously disabled template, making it available for use again.\n \n Parameters:\n - id (required): UUID of the template to enable\n \n Validation Rules:\n - Template must exist\n \n Example:\n ```json\n {\n "id": "550e8400-e29b-41d4-a716-446655440000"\n }\n ```', 'parameters': {'type': 'object', 'properties': {'id': {'type': 'string', 'description': 'The unique ID of the template to enable', 'format': 'uuid'}}, 'required': ['id'], 'additionalProperties': False}, 'strict': True}