"Using agents in VSCode to reference library documentation during programming" matching MCP tools:

• BrowseWixRESTDocsMenu

  mcp

  Browse the Wix REST API documentation menu hierarchy. Alternative to SearchWixRESTDocumentation - use this to explore and discover APIs by navigating the menu structure instead of searching by keywords. - Omit the `menuUrl` param to see top-level categories - Pass a `menuUrl` param to drill into a category - copy the URL from previous responses Example `menuUrl` param values for main Wix verticals: - Stores: "https://dev.wix.com/docs/api-reference/business-solutions/stores" - Bookings: "https://dev.wix.com/docs/api-reference/business-solutions/bookings" - CMS: "https://dev.wix.com/docs/api-reference/business-solutions/cms" - CRM: "https://dev.wix.com/docs/api-reference/crm" - eCommerce: "https://dev.wix.com/docs/api-reference/business-solutions/e-commerce" - Events: "https://dev.wix.com/docs/api-reference/business-solutions/events" - Blog: "https://dev.wix.com/docs/api-reference/business-solutions/blog" - Pricing Plans: "https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans" - Restaurants: "https://dev.wix.com/docs/api-reference/business-solutions/restaurants" - Media: "https://dev.wix.com/docs/api-reference/assets/media" - Site Properties: "https://dev.wix.com/docs/api-reference/business-management/site-properties" <agent-mandatory-instructions> YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. <goal> You are an agent that helps the user manage their Wix site. Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed. </goal> <guidelines> if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed. **Exception:** If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and: - If the user **explicitly** mentions a template, Wix Studio, or headless → call CreateWixBusinessGuide directly. - Otherwise → call the WixSiteBuilder tool directly. **Exception:** If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. **Exception:** If the user wants to upload local or attached image files to a Wix site, skip WixREADME and all docs/schema/API flows — call UploadImageToWixSite directly. Do NOT use ExecuteWixAPI, SearchWixAPISpec, or any Media Manager REST API for image uploads. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unless absolutely necessary. </guidelines> <flow-description> Wix MCP Site Management Flows With WixREADME tool: - RECIPE BASED (PREFERRED!): WixREADME() -> find relevant recipe for the user's prompt/task -> read recipe using ReadFullDocsArticle() -> call Wix API using CallWixSiteAPI() based on the recipe - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - EXAMPLE BASED: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - SCHEMA BASED, FALLBACK: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> inspect the method schema using SearchWixAPISpec or ReadFullDocsMethodSchema -> call API using CallWixSiteAPI() based on the schema Without WixREADME tool: - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - METHOD CODE EXAMPLE BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - FULL SCHEMA BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> inspect the method schema using SearchWixAPISpec or ReadFullDocsMethodSchema -> call API using CallWixSiteAPI() based on the schema </flow-description> </agent-mandatory-instructions>

  Connector

• get_pricing

  Almured

  Retrieve pricing entries for yourself or another agent. WHEN TO USE - Before routing a direct consultation to a target agent, to check what they charge. - To verify your own pricing configuration is set correctly. WHEN NOT TO USE - For real-time consultation pricing during an engagement — pricing is dormant during Phase 2-Infra and no payments happen yet. BEHAVIOR - Read-only. Rate-limited to 60 req/min. - agent_id is optional. Omit to retrieve your own pricing (auth required). Provide a UUID to read another agent's pricing. - Returns category, deliverable_type, price_cents, currency for each entry. - Dormant note is always appended during Phase 2-Infra. WORKFLOW - After checking target agent pricing, use ask_consultation with target_agent_id set; at scope_accepted the platform snapshots the price.

  Connector

• roamzy_list_countries

  mcp-server

  List all 192 countries with Roamzy per-MB rates in USDT — reference table of roaming rates. The user gets one universal eSIM; this list is the rate card, not a product catalog. Call this only if the user asks «what countries are supported» or «show me rates» — don't volunteer it during a purchase flow.

  Connector

• query_docs_filesystem_honeydew_documentation

  Honeydew AI Documentation

  Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the Honeydew Documentation documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path (e.g. `/quickstart.mdx`, `/api-reference/create-customer.mdx`) to `head` or `cat`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /api-reference && ls` or `ls /api-reference`). Do NOT assume that `cd` in one call affects the next call. Examples: - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate limit" - `rg -C 3 "apiKey" /api-reference/` — show matches with 3 lines of context around each hit - `head -80 /quickstart.mdx` — read the top 80 lines of a specific page - `head -80 /quickstart.mdx /installation.mdx /guides/first-deploy.mdx` — read multiple pages in one call - `cat /api-reference/create-customer.mdx` — read a full page when you need everything - `cat /openapi/spec.json | jq '.paths | keys'` — list OpenAPI endpoints Output is truncated to 30KB per call. Prefer targeted `rg -C` or `head -N` over broad `cat` on large files. To read only the relevant sections of a large file, use `rg -C 3 "pattern" /path/file.mdx`. Batch multiple file reads into a single `head` or `cat` call whenever possible. When referencing pages in your response to the user, convert filesystem paths to URL paths by removing the `.mdx` extension. For example, `/quickstart.mdx` becomes `/quickstart` and `/api-reference/overview.mdx` becomes `/api-reference/overview`.

  Connector

• aws___read_documentation

  AWS Knowledge

  Read full AWS documentation pages after searching — search results contain partial excerpts only. Use this tool on the URLs returned by `search_documentation` to get complete, accurate information. ## Usage This tool reads documentation pages concurrently and converts them to markdown format. Supports AWS documentation, AWS Amplify docs, AWS GitHub repositories and CDK construct documentation. When content is truncated, a Table of Contents (TOC) with character positions is included to help navigate large documents. ## Best Practices - After searching, read the most relevant URLs to get complete information — search snippets are partial excerpts and often insufficient to answer accurately - Batch 2-5 requests when reading multiple URLs from search results - Use TOC character positions to jump directly to relevant sections in long documents - If a document was truncated and the answer may be in the remaining content, continue reading with `start_index` set to the previous `end_index`. Stop only once you have found the needed information or confirmed it is not present in the document. ## Request Format Each request must be an object with: - `url`: The documentation URL to fetch (required) - `max_length`: Maximum characters to return (optional, default: 10000 characters) - `start_index`: Starting character position (optional, default: 0) For batching you can input a list of requests. ## Example Request ``` { "requests": [ { "url": "https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-management.html", "max_length": 5000, "start_index": 0 }, { "url": "https://repost.aws/knowledge-center/ec2-instance-connection-troubleshooting" } ] } ``` ## URL Requirements Allow-listed URL prefixes: - docs.aws.amazon.com - aws.amazon.com - repost.aws/knowledge-center - docs.amplify.aws - ui.docs.amplify.aws - github.com/aws-cloudformation/aws-cloudformation-templates - github.com/aws-samples/aws-cdk-examples - github.com/aws-samples/generative-ai-cdk-constructs-samples - github.com/aws-samples/serverless-patterns - github.com/awsdocs/aws-cdk-guide - github.com/awslabs/aws-solutions-constructs - github.com/cdklabs/cdk-nag - constructs.dev/packages/@aws-cdk-containers - constructs.dev/packages/@aws-cdk - constructs.dev/packages/@cdk-cloudformation - constructs.dev/packages/aws-analytics-reference-architecture - constructs.dev/packages/aws-cdk-lib - constructs.dev/packages/cdk-amazon-chime-resources - constructs.dev/packages/cdk-aws-lambda-powertools-layer - constructs.dev/packages/cdk-ecr-deployment - constructs.dev/packages/cdk-lambda-powertools-python-layer - constructs.dev/packages/cdk-serverless-clamscan - constructs.dev/packages/cdk8s - constructs.dev/packages/cdk8s-plus-33 - strandsagents.com/ Deny-listed URL prefixes: - aws.amazon.com/marketplace ## Example URLs - https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html - https://docs.aws.amazon.com/lambda/latest/dg/lambda-invocation.html - https://aws.amazon.com/about-aws/whats-new/2023/02/aws-telco-network-builder/ - https://aws.amazon.com/builders-library/ensuring-rollback-safety-during-deployments/ - https://aws.amazon.com/blogs/developer/make-the-most-of-community-resources-for-aws-sdks-and-tools/ - https://repost.aws/knowledge-center/example-article - https://docs.amplify.aws/react/build-a-backend/auth/ - https://ui.docs.amplify.aws/angular/connected-components/authenticator - https://github.com/aws-samples/aws-cdk-examples/blob/main/README.md - https://github.com/awslabs/aws-solutions-constructs/blob/main/README.md - https://constructs.dev/packages/aws-cdk-lib/v/2.229.1?submodule=aws_lambda&lang=typescript - https://github.com/aws-cloudformation/aws-cloudformation-templates/blob/main/README.md - https://strandsagents.com/docs/user-guide/quickstart/overview/index.md ## Output Format Returns a list of results, one per request: - Success: Markdown content with `status: "SUCCESS"`, `total_length`, `start_index`, `end_index`, `truncated`, `redirected_url` (if page was redirected) - Error: Error message with `status: "ERROR"`, `error_code` (not_found, invalid_url, throttled, downstream_error, validation_error) - Truncated content includes a ToC with character positions for navigation - Redirected pages include a note in the content and populate the `redirected_url` field ## Handling Long Documents If the response indicates the document was truncated, you have several options: 1. **Continue Reading**: Make another call with `start_index` set to the previous `end_index` — do this if the answer may be in the remaining content 2. **Jump to Section**: Use the ToC character positions to jump directly to specific sections 3. **Stop when done**: Stop only once you have found the needed information or confirmed it is not present in the document **Example - Jump to Section:** ``` # TOC shows: "Using a logging library (char 3331-6016)" # Jump directly to that section: {"requests":[{"url": "https://docs.aws.amazon.com/lambda/latest/dg/python-logging.html", "start_index": 3331, "max_length": 3000}]} ```

  Connector

• aws___search_documentation

  AWS Knowledge

  # AWS Documentation Search Tool Use this tool to find relevant AWS documentation — always follow up with `read_documentation` to get complete answers. Prefer this over general knowledge for AWS services, features, configurations, troubleshooting, and best practices. ## When to Use This Tool **Always search when the query involves:** - Any AWS service or feature (Lambda, S3, EC2, RDS, etc.) - AWS architecture, patterns, or best practices - AWS CLI, SDK, or API usage - AWS CDK or CloudFormation - AWS Amplify development - AWS errors or troubleshooting - AWS pricing, limits, or quotas - Strands Agents development - "How do I..." questions about AWS - Recent AWS updates or announcements **Only skip this tool when:** - Query is about non-AWS technologies - Question is purely conceptual (e.g., "What is a database?") - General programming questions unrelated to AWS ## Skill Suggestions for Actionable Queries When your search query matches tasks that benefit from domain-specific expertise, this tool will suggest relevant **Agent Skills**. Skills package domain knowledge, workflows, best practices, decision frameworks, and reference materials that make you a specialist in a particular AWS domain. **How it works:** - Your search query is scored against the skills registry using semantic search over skill descriptions and metadata tags - If your query matches a skill's domain, relevant skills are returned alongside documentation results - Skills cover a wide range of domains: deployment, troubleshooting, security, optimization, architecture, and more - To load a suggested skill, use the `retrieve_skill` tool with the `skill_name` - Once loaded, follow the skill's workflows and retrieve any referenced files as needed **Example queries that may return skills:** - "deploy a web application to AWS" — may return a deployment skill with architecture guidance and step-by-step deployment instructions - "debug Lambda cold start issues" — may return a troubleshooting skill with diagnostic workflows - "secure S3 buckets" — may return a security skill with best practices and compliance checklists - "optimize API Gateway latency" — may return a performance skill with decision frameworks - "set up VPC peering" — may return a networking skill with step-by-step procedures ## Quick Topic Selection | Query Type | Use Topic | Example | |------------|-----------|-------| | API/SDK/CLI code | `reference_documentation` | "S3 PutObject boto3", "Lambda invoke API" | | New features, releases | `current_awareness` | "Lambda new features 2024", "what's new in ECS" | | Errors, debugging | `troubleshooting` | "AccessDenied S3", "Lambda timeout error" | | Amplify apps | `amplify_docs` | "Amplify Auth React", "Amplify Storage Flutter" | | CDK concepts, APIs, CLI | `cdk_docs` | "CDK stack props Python", "cdk deploy command" | | CDK code samples, patterns | `cdk_constructs` | "serverless API CDK", "Lambda function example TypeScript" | | CloudFormation templates | `cloudformation` | "DynamoDB CloudFormation", "StackSets template" | | Architecture, blogs, guides | `general` | "Lambda best practices", "S3 architecture patterns" | | Strands Agents | `strands_docs` | "Strands Agents Python structured output", "Strands Agents AWS CDK EC2 Deployment Example" | | Domain expertise, workflows, guided procedures | `agent_skills` | "deploy serverless app", "debug Lambda cold starts", "secure IAM policies" | ## Documentation Topics ### reference_documentation **For: API methods, SDK code, CLI commands, technical specifications** Use for: - SDK method signatures: "boto3 S3 upload_file parameters" - CLI commands: "aws ec2 describe-instances syntax" - API references: "Lambda InvokeFunction API" - Service configuration: "RDS parameter groups" Don't confuse with general—use this for specific technical implementation. ### current_awareness **For: New features, announcements, "what's new", release dates** Use for: - "New Lambda features" - "When was EventBridge Scheduler released" - "Latest S3 updates" - "Is feature X available yet" Keywords: new, recent, latest, announced, released, launch, available ### troubleshooting **For: Error messages, debugging, problems, "not working"** Use for: - Error codes: "InvalidParameterValue", "AccessDenied" - Problems: "Lambda function timing out" - Debug scenarios: "S3 bucket policy not working" - "How to fix..." queries Keywords: error, failed, issue, problem, not working, how to fix, how to resolve ### amplify_docs **For: Frontend/mobile apps with Amplify framework** Always include framework: React, Next.js, Angular, Vue, JavaScript, React Native, Flutter, Android, Swift Examples: - "Amplify authentication React" - "Amplify GraphQL API Next.js" - "Amplify Storage Flutter setup" ### cdk_docs **For: CDK concepts, API references, CLI commands, getting started** Use for CDK questions like: - "How to get started with CDK" - "CDK stack construct TypeScript" - "cdk deploy command options" - "CDK best practices Python" - "What are CDK constructs" Include language: Python, TypeScript, Java, C#, Go **Common mistake**: Using general knowledge instead of searching for CDK concepts and guides. Always search for CDK questions! ### cdk_constructs **For: CDK code examples, patterns, L3 constructs, sample implementations** Use for: - Working code: "Lambda function CDK Python example" - Patterns: "API Gateway Lambda CDK pattern" - Sample apps: "Serverless application CDK TypeScript" - L3 constructs: "ECS service construct" Include language: Python, TypeScript, Java, C#, Go ### cloudformation **For: CloudFormation templates, concepts, SAM patterns** Use for: - "CloudFormation StackSets" - "DynamoDB table template" - "SAM API Gateway Lambda" - "CloudFormation template examples" ### strands_docs **For: Strands Agents API reference, integrations, model providers, session managers, tools, examples, user-guide** Use for: - "Strands Agents Python SDK example" - "Strands Agents AWS integration" - "Strands Agents community contributions" - "Strands Agents usage examples" - "Strands Agents usage guide" ### general **For: Architecture, best practices, tutorials, blog posts, design patterns** Use for: - Architecture patterns: "Serverless architecture AWS" - Best practices: "S3 security best practices" - Design guidance: "Multi-region architecture" - Getting started: "Building data lakes on AWS" - Tutorials and blog posts **Common mistake**: Not using this for AWS conceptual and architectural questions. Always search for AWS best practices and patterns! **Don't use general knowledge for AWS topics—search instead!** ### agent_skills **For: Discovering agent skills — domain-specific expertise packages for AWS workflows** Use for: - Complex tasks that benefit from guided workflows: "deploy a serverless application" - Troubleshooting scenarios: "debug Lambda cold starts", "resolve ECS task failures" - Security and compliance: "secure S3 buckets", "review IAM policies for least privilege" - Architecture and optimization: "optimize API Gateway latency", "design multi-region architecture" - When you need domain expertise beyond what documentation provides Skills go beyond documentation — they provide workflows, decision frameworks, best practices, and may include embedded procedures for critical sub-tasks. **Important**: This topic is meant for discovery. Once you identify the skill you need, use `retrieve_skill` tool with the `skill_name` to load the full skill and its reference materials. **Note**: If combined with other topics, skills will be mixed into the documentation results. Use `agent_skills` alone for a clean skill-only listing. ## Search Best Practices **Be specific with service names:** Good examples: ``` "S3 bucket versioning configuration" "Lambda environment variables Python SDK" "DynamoDB GSI query patterns" ``` Bad examples: ``` "versioning" (too vague) "environment variables" (missing context) ``` **Include framework/language:** ``` "Amplify authentication React" "CDK Lambda function TypeScript" "boto3 S3 client Python" ``` **Use exact error messages:** ``` "AccessDenied error S3 GetObject" "InvalidParameterValue Lambda environment" ``` **Add temporal context for new features:** ``` "Lambda new features 2024" "recent S3 announcements" ``` **If the first search does not return results that directly answer the question, refine your query and search again with different terms, a more specific phrase, or a different topic. Try conceptual/architectural topics (general, blogs) if reference docs are too narrow.** **After searching, use `read_documentation` on the top-ranked URLs to verify and complete your answer.** ## Multiple Topic Selection You can search multiple topics simultaneously for comprehensive results: ``` # For a query about Lambda errors and new features: topics=["troubleshooting", "current_awareness"] # For CDK examples and API reference: topics=["cdk_constructs", "cdk_docs"] # For Amplify and general AWS architecture: topics=["amplify_docs", "general"] # For actionable tasks: topics=["agent_skills"] ``` ## Response Format Results include: - `rank_order`: Relevance score (lower = more relevant) - `url`: Direct documentation link — use with `read_documentation` to get the full page content - `title`: Page title - `context`: Partial excerpt only — not the complete documentation. After reviewing results, call `read_documentation` on the most relevant URLs before answering. Do not answer based on the context excerpt alone. ## Parameters ``` search_phrase: str # Required - your search query topics: List[str] # Optional - up to 3 topics. Defaults to ["general"] limit: int = 5 # Optional - max results per topic ``` --- **Remember: When in doubt about AWS, always search. This tool provides the most current, accurate AWS information. But search is only step 1 — always read the full documentation to give complete answers.**

  Connector

• upload_media

  switch

  Upload one image into the user's Switch library in a single call. Pass `url` (any public https) OR `base64` + `mime`. Switch fetches/decodes it server-side, stores it, and returns a clean public URL plus the new asset id. This is THE way to use a photo the user attached in chat as a reference: pass the returned `url` directly into generate_image's reference_image_urls, OR into generate_video's image_url (image-to-video) or reference_image_urls (reference / omni video). The returned URL is provider-fetchable as-is — no presigned PUT, no curl, no confirm-upload step. Do NOT call get_my_active_references for a chat-attached photo; that strip only holds Studio-managed refs.

  Connector

• get_framework_docs

  main

  Retrieves authoritative documentation directly from the framework's official repository. ## When to Use **Called during i18n_checklist Steps 1-13.** The checklist tool coordinates when you need framework documentation. Each step will tell you if you need to fetch docs and which sections to read. If you're implementing i18n: Let the checklist guide you. Don't call this independently ## Why This Matters Your training data is a snapshot. Framework APIs evolve. The fetched documentation reflects the current state of the framework the user is actually running. Following official docs ensures you're working with the framework, not against it. ## How to Use **Two-Phase Workflow:** 1. **Discovery** - Call with action="index" to see available sections 2. **Reading** - Call with action="read" and section_id to get full content **Parameters:** - framework: Use the exact value from get_project_context output - version: Use "latest" unless you need version-specific docs - action: "index" or "read" - section_id: Required for action="read", format "fileIndex:headingIndex" (from index) **Example Flow:** ``` // See what's available get_framework_docs(framework="nextjs-app-router", action="index") // Read specific section get_framework_docs(framework="nextjs-app-router", action="read", section_id="0:2") ``` ## What You Get - **Index**: Table of contents with section IDs - **Read**: Full section with explanations and code examples Use these patterns directly in your implementation.

  Connector

• execute_sql_readonly

  Google Big Query

  Run a read-only SQL query in the project and return the result. Prefer this tool over `execute_sql` if possible. This tool is restricted to only `SELECT` statements. `INSERT`, `UPDATE`, and `DELETE` statements and stored procedures aren't allowed. If the query doesn't include a `SELECT` statement, an error is returned. For information on creating queries, see the [GoogleSQL documentation](https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax). Example Queries: -- Count the number of penguins in each island. SELECT island, COUNT(*) AS population FROM bigquery-public-data.ml_datasets.penguins GROUP BY island -- Evaluate a bigquery ML Model. SELECT * FROM ML.EVALUATE(MODEL `my_dataset.my_model`) -- Evaluate BigQuery ML model on custom data SELECT * FROM ML.EVALUATE(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`)) -- Predict using BigQuery ML model: SELECT * FROM ML.PREDICT(MODEL `my_dataset.my_model`, (SELECT * FROM `my_dataset.my_table`)) -- Forecast data using AI.FORECAST SELECT * FROM AI.FORECAST(TABLE `project.dataset.my_table`, data_col => 'num_trips', timestamp_col => 'date', id_cols => ['usertype'], horizon => 30) Queries executed using the `execute_sql_readonly` tool will have the job label `goog-mcp-server: true` automatically set. Queries are charged to the project specified in the `project_id` field.

  Connector

• get_briefed

  VARRD — Statistically Validated Trading Edges + AI Research Engine

  Get a personalized market news briefing based on your validated edge library. Profiles your strategies, searches today's news for the instruments and setups you actually trade, and writes a concise digest connecting each headline to your specific book. Each news item includes a ↳ line tying it to your actual positions and edges (e.g. 'your ES momentum setups', 'your GC mean-reversion edge'). Requires at least 5 strong edges in your library. Costs credits.

  Connector

• microsoft_docs_fetch

  xpay✦ DevTools Collection

  Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.

  Connector

• get_my_library_loans

  ssuMCP

  Returns the authenticated user's current library loans including due dates. Requires mcp_session_id with the LIBRARY provider linked via start_auth. Returns AUTH_REQUIRED with a loginUrl if LIBRARY is not authenticated — show the loginUrl to the user and ask them to open it in a browser, then retry this call with the returned mcp_session_id.

  Connector

• roamzy_country_detail

  mcp-server

  Reference info: the per-MB rate for a specific country. Call ONLY if the user explicitly asks about price for their destination (e.g. «how much in Japan?»). DO NOT call this during purchase — the user does not need to pick a country to buy. The eSIM works in all 192; rates are reference info, not a purchase gate.

  Connector

• examples.get

  AI Design Blueprint Doctrine

  Get one curated example by stable slug. Returns title, summary, source-code links, principle coverage (the principle slugs the example demonstrates), difficulty, library/framework, and implementation notes. Use this when you already have the slug from examples.search, a principles.get response, or a guide cross-link; prefer examples.search when filtering by topic / principle / difficulty / library; prefer guides.get when the caller wants a full walkthrough rather than a single reference example. Returns error_payload on unknown slug.

  Connector

• list_themes

  Slidev MCP

  Get a list of all available themes with style descriptions and recommendations. Call this to decide which theme to use. Returns a guide organized by style (dark, academic, modern, playful, etc.) with "best for" recommendations. After picking a theme, call get_theme with the theme name to read its full documentation (layouts, components, examples) before rendering. This tool does NOT display anything to the user — it is for your own reference when choosing a theme.

  Connector

• examples.get

  AI Design Blueprint

  Get one curated example by stable slug. Returns title, summary, source-code links, principle coverage (the principle slugs the example demonstrates), difficulty, library/framework, and implementation notes. Use this when you already have the slug from examples.search, a principles.get response, or a guide cross-link; prefer examples.search when filtering by topic / principle / difficulty / library; prefer guides.get when the caller wants a full walkthrough rather than a single reference example. Returns error_payload on unknown slug.

  Connector

• ai_filters_test

  DialogBrain

  Test a message against an AI filter to check whether it would match. This tool embeds the provided message using Voyage AI and computes the cosine similarity between the message vector and the filter's stored reference vector. It returns the similarity score, whether the message would match (similarity >= threshold), and the filter's threshold value. Use this to: - Verify a filter works as intended before using it in a trigger - Tune the threshold by testing borderline messages - Debug why a message did or did not match a filter in production Returns: {similarity: float, matched: bool, threshold: float} Note: This tool calls the Voyage AI embedding API to embed the test message.

  Connector

• fetch

  Sofya

  Fetch one or more URLs and return their content as clean markdown. Use this to read articles, documentation, blog posts, or any page where you need the complete text, not just a snippet from search. Also supports PDF, DOCX, and other document formats. Costs 1 credit per URL. Max 10 URLs per request. Failed URLs are not charged. Set include_raw_html=true to also get the raw HTML source in each result. Useful for inspecting embedded URLs, data attributes, iframes, or script tags that are stripped during markdown conversion. Returns null for non-HTML content (PDF, DOCX, etc.). Same cost. Returns: results (array of {title, url, content, raw_html, published_time, success, error}), credits_used, credits_remaining. Args: urls: List of URLs to fetch (max 10) include_raw_html: Include raw HTML source in each result (default false)

  Connector

• resolve-library-id

  xpay✦ DevTools Collection

  Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'query-docs' to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Selection Process: 1. Analyze the query to understand what library/package the user is looking for 2. Return the most relevant match based on: - Name similarity to the query (exact matches prioritized) - Description relevance to the query's intent - Documentation coverage (prioritize libraries with higher Code Snippet counts) - Source reputation (consider libraries with High or Medium reputation more authoritative) - Benchmark Score: Quality indicator (100 is the highest score) Response Format: - Return the selected library ID in a clearly marked section - Provide a brief explanation for why this library was chosen - If multiple good matches exist, acknowledge this but proceed with the most relevant one - If no good matches exist, clearly state this and suggest query refinements For ambiguous queries, request clarification before proceeding with a best-guess match. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.

  Connector

• __unlock_blockchain_analysis__

  mcp-server

  Mandatory initialization step for any session against the Blockscout MCP server. Returns server reference data plus the `blockscout-analysis` skill pointer and URI resolution rule. MANDATORY FOR AI AGENTS: Call this tool first in every session. The returned payload identifies where the operating rules and analysis framework live and how to read referenced skill files before executing further tool calls.

  Connector