Create-annotation
Create an Annotation on one or more Cost Reports for a specific date. Use this tool when a user asks to add a note, explanation, or event marker to Cost Reports.
Vantage MCP lets agents analyze authorized cloud costs, reports, resources, tags, budgets, anomalies, and optimization recommendations, and perform supported FinOps management actions.
Create an Annotation on one or more Cost Reports for a specific date. Use this tool when a user asks to add a note, explanation, or event marker to Cost Reports.
Creates a new Billing Rule. Billing rules allow you to adjust, exclude, credit, charge, or apply custom modifications to your cost data. The required fields depend on the rule type: - Exclusion rules require charge_type. - Adjustment rules require percentage. Optionally accepts service and category to scope the adjustment. - Charge and Credit rules require service, category, sub_category, amount, and start_date. - Custom rules require sql_query.
Creates a budget based on the parameters specified. This is useful if you have been tasked with managing budgets or you are building a cost report with budgets in mind.
Create a Budget Alert that notifies users or connected channels when one or more Budgets reach a percentage threshold during a monthly time window.
Creates a Canvas based on the parameters specified. A Canvas is an AI-generated cost analysis view created from a natural language prompt. The prompt describes what cost data to analyze (e.g. "Show me monthly costs by provider"). Creating a canvas triggers an asynchronous refresh to generate the data.
Create a new Cost Alert in Vantage. Cost Alerts are threshold-based spending alerts for one or more Cost Reports. Use this tool when a user asks to create, add, or set up a cost alert, spending alert, budget alert, threshold alert, or spend-limit notification. Do not use this for Report Notifications, scheduled report summaries, or recurring Cost Report delivery.
Create a new Cost Report in Vantage. Cost Reports are saved queries that can be used to track and analyze spending over time. They can be filtered using VQL (Vantage Query Language) and configured with various display options. VQL Filtering Guide: All costs originate from a Cost Provider (generally a cloud company like AWS, Azure, Datadog) and then filter on a service that they provide (like EC2, S3, etc). A cost provider is required on every VQL query. VQL is always in parenthesis. Always use single quotes around names that are being queried. Basic VQL Syntax: - Query on a cost provider: (costs.provider = '<provider name>') - Query on a service: (costs.provider = '<provider name>' AND costs.service = '<service name>') - Multiple providers: ((costs.provider = 'aws') OR (costs.provider = 'azure')) - Multiple services: (costs.provider = 'aws' AND costs.service IN ('AWSQueueService', 'AWSLambda')) - Filter by region: (costs.provider = 'aws' AND costs.region = 'us-east-1') - Filter by account: (costs.provider = 'aws' AND costs.account_id = '1000000717') Tag Filtering: - Tag with specific value: (costs.provider = 'aws' AND tags.name = 'environment' AND tags.value = 'production') - Any value of a tag: (costs.provider = 'aws' AND tags.name = 'environment') - Resources without a tag: (costs.provider = 'aws' AND tags.name = NULL) - Multiple tag values: (costs.provider = 'aws' AND tags.name = 'environment' AND (tags.value = 'dev' OR tags.value = 'staging')) Use get-myself to find available workspaces and list-cost-providers/list-cost-services to find valid provider and service names for your VQL queries.
Create a new Dashboard in Vantage. Dashboards are collections of widgets that visualize cost data. You can optionally attach widgets (by their widgetable_token) and saved filters, and you can control the time range using either: - date_interval (recommended), or - start_date + end_date (custom range) Note: start_date/end_date are incompatible with date_interval. The list of supported widgets is: - cost reports - usage reports - resource reports - kubernetes efficiency reports - financial commitment reports - recommendation saved views The token returned in the response can be used to link to the Dashboard in the Vantage Web UI: https://console.vantage.sh/go/<token>
Create a new Financial Commitment Report in Vantage. Financial Commitment Reports track committed spend and on-demand costs over time. They can be filtered using VQL and grouped by dimensions such as commitment type, service, region, or tags. VQL Filtering Guide: Financial Commitment Report VQL uses the financial_commitments namespace. A provider filter should be included in each query, and string values should be wrapped in single quotes. Basic VQL Syntax: - Query on a provider: (financial_commitments.provider = 'aws') - Query on a service: (financial_commitments.provider = 'aws' AND financial_commitments.service = 'AmazonEC2') - Multiple services: (financial_commitments.provider = 'aws' AND financial_commitments.service IN ('AmazonEC2','AmazonRDS')) - Filter by billing account: (financial_commitments.provider = 'aws' AND financial_commitments.provider_account_id = '123456789012') - Filter by region: (financial_commitments.provider = 'aws' AND financial_commitments.region = 'us-east-1') - Filter by tag: (financial_commitments.provider = 'aws' AND financial_commitments.resource_tags->>'environment' = 'production') Use get-myself to find available workspaces. Use the VQL for Financial Commitment Reports resource for the full list of available financial_commitments fields and examples.
Create a folder for organizing Cost Reports or Resource Reports. Set type to CostFolder for Cost Reports or ProviderResourceFolder for Resource Reports.
Creates a saved Network Flow Report for analyzing cloud network traffic by cost or bytes.
Create a new Recommendation View in Vantage. Recommendation Views are saved filters for recommendations. They can be scoped by provider, billing account, cloud account, region, recommendation type, tags, creation date, and minimum potential savings. Use get-myself to find available workspaces. Use list-recommendations to discover valid provider IDs, recommendation types, accounts, regions, tags, and savings ranges before creating a view. Filter examples: - AWS recommendations in production: provider_ids ["aws"], tag_key "environment", tag_value "production" - High-savings recommendations: min_savings 100 - Recommendations created in a date range: start_date "2024-01-01", end_date "2024-06-30"
Create a scenario-model ReportForecast for a Cost Report. Provide at least one of scenario_model_tokens or business_metric_token. Use list-scenario-models and list-business-metrics to discover tokens. Requires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot update the Cost Report.
Create a new Report Notification in Vantage. Report Notifications send scheduled Cost Report summaries to configured users, Slack channels, or Microsoft Teams channels on a daily, weekly, or monthly cadence. Use this tool when a user asks to create, add, or set up scheduled report delivery for an existing Cost Report. Do not use this for Cost Alerts, budget alerts, threshold alerts, or spend-limit notifications. Cost Alerts notify users when spend crosses a configured threshold; Report Notifications deliver scheduled report summaries.
Create a saved Resource Report in Vantage. Resource Reports persist a VQL filter over cloud infrastructure resources so the view can be reopened, shared, added to dashboards, and queried later with list-provider-resources via resource_report_token. Returns the report token; link users to https://console.vantage.sh/go/<token>. Resource Report VQL uses the resources and tags namespaces — not Cost Report costs VQL (create-cost-report). Use list-provider-resources for one-off resource queries without saving a report; use list-resource-reports to browse existing reports.
Create a ScenarioModel with optional periods and provider/service filters. Assign created ScenarioModels to Cost Report forecasts with create-report-forecast or update-report-forecast. Requires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot create models.
Creates a new Virtual Tag (Virtual Tag Config) in Vantage. Do not use this to edit an existing Virtual Tag Config; use update-virtual-tag-config for config settings or value order, and the Virtual Tag Config Value tools for individual values. Virtual Tag Configs define a derived (virtual) tag key and a set of values determined by VQL filters. This is useful for normalizing cost attribution (e.g., mapping multiple provider tag formats into a single tag), collapsing noisy tag keys, and optionally overriding provider-supplied tags. You can optionally: - backfill_until: backfill the virtual tag values to an earliest month - collapsed_tag_keys: collapse values for specific underlying tag keys (optionally scoped by provider) - values: define named values via VQL filters, optionally linked to Business Metrics and/or cost metrics
Adds a new mapping/value to an existing Virtual Tag Config without replacing its other values. Use this to append a mapping while editing a Virtual Tag; new values are added after existing values.
Create a new Workspace in Vantage. Workspaces are isolated environments for organizing cost data and access control across teams.
Delete an Annotation by its token. This action is irreversible. Use list-annotations to find the annotation_token.
Deletes a Billing Rule by its token. This action is irreversible.
Deletes a Budget by its token. This action is irreversible.
Delete a Budget Alert by token. This permanently removes the alert without deleting its monitored Budgets.
Deletes a Canvas by its token. This action is irreversible.
Deletes a Cost Alert by its token. This action is irreversible.
Deletes a cost report by its token. This action is irreversible.
Deletes a Dashboard by its token. This action is irreversible.
Deletes a financial commitment report by its token. This action is irreversible.
Deletes a Folder. Reports within the Folder will not be deleted.
Deletes a Network Flow Report by token.
Deletes a recommendation view by its token. This action is irreversible.
Delete a scenario-model ReportForecast by token. This action is irreversible. Requires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot update the Cost Report.
Deletes a Report Notification by its token. This action is irreversible and stops the scheduled Cost Report summary from being delivered. Use this tool when a user asks to delete, remove, disable, or stop a scheduled report notification. Do not use this for deleting Cost Alerts, budget alerts, threshold alerts, or spend-limit notifications.
Deletes a resource report by its token. This action is irreversible.
Delete a ScenarioModel by token. This action is irreversible and regenerates forecasts that referenced the model. Requires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot delete the model.
Deletes an entire Virtual Tag Config and all of its mappings/values. To remove only one mapping, use delete-virtual-tag-config-value instead.
Deletes exactly one mapping/value from an existing Virtual Tag Config, not the containing tag. Remaining values are preserved without replacement or reordering.
Gets a specific anomaly alert by its token.
Gets a specific Billing Rule by its token. Returns details about the rule including its type, configuration, and applicable dates.
Gets a specific Budget by its token. Optionally includes performance data showing actual spend vs. budget amounts by period. The token of a budget can be used to link the user to the budget in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<BudgetToken>
Get a specific Budget Alert by token. Budget Alerts monitor Budget objects.
Get a specific BusinessMetric by token. BusinessMetrics can be attached to Cost Reports for per-unit cost analysis, and their values can be retrieved with get-business-metric-values or get-business-metric-forecasted-values.
Get forecasted values for a BusinessMetric. Values are returned in descending date order by the Vantage API and can include optional labels. Use start_date to limit results to values on or after a YYYY-MM-DD date. This endpoint is paginated. If the user asks for all values, complete data, or values for a date range such as a month, keep calling this tool with pagination.nextPage until pagination.hasNextPage is false before answering. The API only supports a start_date lower bound. For bounded ranges, such as a specific month, fetch all pages from the requested start date and then filter the returned values to the requested end date locally.
Get historical values for a BusinessMetric. Values default to monthly sums grouped by label. Use day for daily sums or raw to preserve original timestamps, including hourly values; binned sums may not suit gauges or percentages. Values are returned in descending date order by the Vantage API and can include optional labels. When a request depends on labels but exact values are not confirmed, call list-business-metric-labels first and pass the selected values through label_values. Skip label discovery when exact values are already supplied. Use start_date to limit results to values on or after a YYYY-MM-DD date. This endpoint is paginated. If the user asks for all values, complete data, or values for a date range such as a month, keep calling this tool with pagination.nextPage until pagination.hasNextPage is false before answering. The API only supports a start_date lower bound. For bounded ranges, such as a specific month, fetch all pages from the requested start date and then filter the returned values to the requested end date locally.
Gets a specific Canvas by its token. Returns the canvas details including its title, prompt, status, and structured table data. The token of a canvas can be used to link the user to the canvas in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<CanvasToken>
Gets a specific Cost Alert by its token. Use this tool when you already have a cost alert token, such as one returned by list-cost-alerts or referenced in Vantage. Cost Alerts are threshold-based spending alerts for Cost Reports. Do not use this for Report Notifications, scheduled report summaries, or recurring Cost Report delivery.
Gets a specific Cost Alert event by its token. Use after list-cost-alert-events when you need the full trigger record.
Get Cost Provider Accounts in a workspace with human-readable titles. Useful for mapping account IDs to names, or looking up an account_id for VQL.
Gets a specific cost report by its token. The token of a report can be used to generate a link to the report in the Vantage Web UI: https://console.vantage.sh/go/<token> The same token can be used with the get-cost-report-forecast tool to retrieve forecasted future costs for the report.
Given a Cost Report Token, Vantage can forecast the costs for a given time range. Vantage will return costs that are *predicted*, but have not yet been actually incurred. If the user does not set a date, best to pick the next month as the default. The report token can be used to link the user to the report in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<CostReportToken>
Gets a specific dashboard by its token. The token of a dashboard can be used to generate a link to the dashboard in the Vantage Web UI: https://console.vantage.sh/go/<token>
Gets a specific financial commitment report by its token. Use this tool when you already have a financial commitment report token, such as one returned by Vantage or referenced in the Vantage console. The response includes the report's title, workspace, date range, grouping, cost scope, and filter configuration.
Gets a specific Folder by its token.
Get data that is available to the current auth token. This includes the list of Workspaces they have access to. default_workspace_token: The token of the workspace that is set as the default for the user and can be used for queries unless told otherwise.
Gets a saved Network Flow Report by token. Open in the console at https://console.vantage.sh/go/<token>.
Get detailed information about a specific provider resource using its token or UUID. This returns comprehensive details about the resource including: - Resource metadata (instance type, size, configuration, etc.) - Account and billing account information - Provider and region details - Creation timestamp - Optional cost breakdown by category The resource_token can be either a Vantage token (starting with prvdr_rsrc) or the resource's UUID/ARN from the cloud provider. Set include_cost to true to get cost information broken down by category.
Get comprehensive details about a specific cost optimization recommendation using its unique token. This tool provides in-depth information about a single recommendation including: - Full description of the optimization opportunity - Exact potential cost savings amount and currency - Current status (open, resolved, dismissed) - Category and type of recommendation (e.g., ec2_rightsizing_recommender, unused_financial_commitments) - Cloud provider and provider account information - Service being optimized (e.g., EC2, RDS, S3) - Number of resources that would be affected - Creation and last updated timestamps - Additional metadata specific to the recommendation type Use this tool after getting a recommendation token from list-recommendations to understand exactly what optimization is being suggested and the potential impact. The recommendation token can also be used with get-recommendation-resources to see the specific infrastructure resources involved.
Get comprehensive details about a specific infrastructure resource within a cost optimization recommendation, including the exact actions recommended for that resource. This tool provides the deepest level of detail about a single resource that's part of a recommendation. The response includes: - Complete resource identification (resource ID, type, region, account) - Current configuration and specifications - Resource utilization metrics and patterns - Specific recommendation actions for this resource - Estimated cost savings for implementing the recommendations - CLI command for remediating the recommendation - Implementation complexity and effort estimates - Detailed metadata specific to the resource type and recommendation category Use this tool when you need to understand exactly what should be done with a specific resource. For example: - For rightsizing recommendations: shows current vs. recommended instance types, CPU/memory utilization data - For unused resources: shows usage patterns, last activity, and safe termination recommendations - For storage optimization: shows current vs. recommended volume types, IOPS usage, throughput patterns - For Reserved Instance recommendations: shows usage patterns, recommended commitment levels This is the most granular level of recommendation data available and is essential for making informed decisions about implementing specific optimizations. You must have both the recommendation token (from list-recommendations) and the resource token (from get-recommendation-resources) to use this tool.
Get a paginated list of all infrastructure resources affected by a specific cost optimization recommendation. This tool returns the actual cloud resources (instances, volumes, load balancers, etc.) that are involved in a recommendation. Each resource entry includes: - Resource token (unique identifier for the specific resource) - Resource type (e.g., EC2 instance, EBS volume, RDS instance) - Resource identifier (instance ID, volume ID, etc.) - Current configuration details - Resource-specific metadata Use this tool after getting recommendation details to see exactly which resources need attention. For example: - For EC2 rightsizing recommendations: shows the specific instances that are over-provisioned - For unused resource recommendations: shows the idle instances, volumes, or load balancers - For Reserved Instance recommendations: shows the usage patterns and instance families - For storage optimization: shows the volumes that could be optimized Each resource has its own token that can be used with get-recommendation-resource-details to get comprehensive information about that specific resource and what actions are recommended. Use pagination (page parameter) to navigate through large numbers of affected resources.
Gets a specific recommendation view by its token.
Get a specific scenario-model ReportForecast by token. Use list-report-forecasts to discover tokens for a Cost Report. Requires Scenario Models (Enterprise). A 403 means the account is not entitled.
Gets a specific Report Notification by its token. Use this tool when you already have a report notification token, such as one returned by list-report-notifications or referenced in Vantage. The response includes the notification title, Cost Report token, recipients, delivery channels, frequency, and tracked change type. Do not use this for Cost Alerts, budget alerts, threshold alerts, or spend-limit notifications.
Gets a specific resource report by its token. The token of a report can be used to generate a link to the resource report in the Vantage Web UI: https://console.vantage.sh/go/<token>
Get a specific ScenarioModel by token. ScenarioModels define future-cost adjustments that can be assigned to Cost Report forecasts. Use list-scenario-models to discover tokens. The token can also be used with update-scenario-model, delete-scenario-model, and report-forecast tools. Requires Scenario Models (Enterprise). A 403 means the account is not entitled.
Gets a specific team with its token.
Return all Teams that the user has access to.
Gets a specific User by their token. Use get-users to discover user tokens in the workspace.
Return all Users that the user can see in the workspace. Requires account owner permissions; non-owners receive 403 from the API.
Returns one existing Virtual Tag (Virtual Tag Config) with its complete ordered mappings/values. Use this to show all values on a tag and discover value tokens before editing or reordering.
Returns one mapping/value from an existing Virtual Tag Config, including its filter and allocation settings. Use this to inspect one mapping before editing it.
Gets a specific Workspace by its token. Workspaces are isolated environments within Vantage for organizing cost data and access control across teams.
List report annotations available to the authenticated Vantage access token, ordered from newest to oldest. Optionally filter annotations to a specific Cost Report.
Given a token of a Cost Report, look for anomalies in the report. You may optionally pass a Provider, like AWS to filter on. If you do pass a Provider, you can futher filter on a Service, like EC2 or S3. The report token can be used to link the user to the report in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<CostReportToken>
List audit logs visible to the authenticated Vantage access token. Audit logs provide a chronological history of supported changes to user-facing resources in Vantage, such as cost reports, virtual tags, segments, recommendation commitments, and other workspace-related objects. Results are returned in reverse chronological order (newest first). Each audit log entry can include: - The audit log token - The affected object's token, type, and title - The event (`record_created`, `record_updated`, or `record_destroyed`) - The source of the action (`console`, `api`, or `finops_agent`) - The user display name, when available - The workspace title and workspace token, when available - The timestamp when the audit log was created - Field-level change data in `changed_values` and `unchanged_values` Audit logs commonly include actions such as: - Creating, updating, or deleting cost reports - Modifying report filters or related configuration - Creating, updating, or deleting virtual tags - Updating recommendation commitments - Creating, updating, or deleting segments Use pagination with the `page` parameter starting at 1. You can also pass `limit`; if omitted, the API defaults to 100 results per page. Audit logs can be filtered by: - `user`: numeric user ID associated with the action - `workspace_token`: workspace token - `action`: `create`, `update`, or `delete` - `object_type`: `cost_report`, `virtual_tag`, `recommendation_commitment`, or `segment` - `object_name`: exact object title - `object_token`: audited object token - `source`: `console`, `api`, or `finops_agent` - `start_date` and `end_date`: YYYY-MM-DD dates such as `2024-06-01` - `token`: audit log token Use cases for audit logs include: - Compliance and security review - Debugging change history - Change management for reports and configuration - Monitoring actions taken through the API or the Finops Agent
List all billing rules available in the Vantage account. Billing rules allow you to adjust, exclude, or add charges to your cost data. Use the page value of 1 to start.
List Budget Alerts in Vantage. Budget Alerts notify users or connected channels when one or more Budgets reach a percentage threshold during a monthly time window.
List all budgets available in the Vantage account. Budgets help track spending against predefined limits. Use the page value of 1 to start. A budget is built against a Cost Report. The Budget objects returned by this tool will have a "cost_report_token" field that contains the token of the Cost Report. The Cost Report has the "filter" field to know what is the range of providers & services that the budget is tracking. When a user is looking at a Cost Report for a specific date range, they can decide if the providers and services spend is higher than desired by looking at the budgets for that report and the date range of the budget. The token of a budget can be used to link the user to the budget in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<BudgetToken>
List distinct label values for a BusinessMetric. For multi-label metrics, values are flattened across label keys. Use this before get-business-metric-values when a label-dependent request does not provide confirmed exact label values. This endpoint is paginated. If the user needs the complete set of labels, keep calling this tool with pagination.nextPage until pagination.hasNextPage is false.
List all BusinessMetrics available to the current Vantage API token. Use page 1 when calling this tool for the first time. If the user asks for all BusinessMetrics or needs to search across the full set, keep calling this tool with pagination.nextPage until pagination.hasNextPage is false. BusinessMetrics represent business KPIs, such as requests, users, or revenue, that can be attached to Cost Reports for per-unit cost analysis. The token of a BusinessMetric can be used with get-business-metric, list-business-metric-labels, get-business-metric-values, and get-business-metric-forecasted-values.
List all saved Canvases available in the Vantage account. Canvases are AI-generated cost analysis views created from natural language prompts. Use the page value of 1 to start. The token of a canvas can be used to link the user to the canvas in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<CanvasToken>
List events for a Cost Alert. Events are individual alert trigger records and can be filtered by Cost Report token.
List Cost Alerts available in the Vantage account. Cost Alerts are threshold-based spending alerts for Cost Reports. Use this tool when a user asks to list, show, view, or find cost alerts, spending alerts, budget alerts, threshold alerts, or spend-limit notifications. Do not use this for Report Notifications, scheduled report summaries, or recurring Cost Report delivery.
List all cost provider integrations available to provide costs data from and their associated accounts. Integrations are the cost providers that Vantage is configured to connect to and pull cost data from. If a user wants to see their providers in the Vantage Web UI, they can visit https://console.vantage.sh/settings/integrations Note that when 'provider' is 'custom_provider', that has a special case. When doing a VQL query for custom provider, use the 'token' you get back. Here is an example, where the token of the custom provider is "accss_crdntl_07171984": (costs.provider = 'custom_provider:accss_crdntl_07171984')
List of cost providers available to query for a given Workspace. Can be used to filter costs down to a specific provider in VQL queries.
List all cost reports available. Cost reports are already created reports authored by a user in Vantage. If the user isn't asking about a specific report, it's better to use the query-costs tool. When you first call this function, use the "Page" parameter of 1. The 'Title' of a report is a good way to know what the report is about. The 'filter' of a report also gives clues to the data it provides. The 'token' of a report is a unique identifier for the report. It can be used to generate a link to the report in the Vantage Web UI. If a user wants to see a report, you can link them like this: https://console.vantage.sh/go/<token> Vantage offers data related to a cost report: Forecasts. The same report token can be used on the get-cost-report-forecast tool and Vantage will forecast future costs.
List cost service display names for a workspace. These names may NOT match VQL costs.service identifiers used in query-costs filters. Do not copy names from this tool directly into VQL. Use vql_info or costs.service values from a broad query-costs probe instead.
List the cost items inside a report. The Token of a Report must be provided. Use the page value of 1 to start. The report token can be used to link the user to the report in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<CostReportToken> The DateBin parameter controls the time granularity of returned results. When DateBin=day you get a record for each service spend on that day. For DateBin=week you get one entry per week, with the accrued_at field set to the first day of the week, but the spend item represents spend for a full week. Same with DateBin=month, each record returned covers a month of data. This lets you get answers with processing fewer records. If omitted, the API uses the cost report's configured date bin, or day if the report has no override. Cost settings (credits, refunds, discounts, tax, amortization, etc.) default to the report's own settings. Only provide these parameters if you need to override the report's defaults. Use settings_aggregate_by to choose the metric: cost (default), usage, or count. When aggregate_by is count, the response includes total_count and counts (date-binned distinct Group By permutation counts for the full requested period). Count is not supported for segment reports.
List all dashboards available in the Vantage account. Dashboards provide visualizations of cost data. Use the page value of 1 to start. The token of a dashboard can be used to link the user to the dashboard in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<token>
List all financial commitment reports available in the Vantage account. Use the page value of 1 to start.
List folders for Cost Reports or Resource Reports, optionally filtering by title, Workspace, or folder type. Use CostFolder for Cost Report folders and ProviderResourceFolder for Resource Report folders; folder tokens link to https://console.vantage.sh/go/<token>.
Lists saved Network Flow Reports. Use get-network-flow-report for a report's configuration.
List infrastructure provider resources (instances, volumes, load balancers, etc.) from your cloud accounts. Resources can be fetched either from a specific Resource Report or by using VQL filters. When using a resource_report_token, you get the pre-filtered resources from that report. When using VQL filters with workspace_token, you can dynamically query resources across your infrastructure. Provide either resource_report_token or filter (not both). When using filter, workspace_token is required. VQL for Resource Reports enables filtering using two primary namespaces: **Resources Namespace** - Access infrastructure attributes: - resources.provider (AWS, GCP, Azure, etc.) - resources.region (geographic location codes) - resources.account_id and resources.provider_account_id - resources.type (resource classification) - resources.label and resources.uuid (identifiers) - resources.metadata (detailed resource properties using ->> operator, e.g., resources.metadata->>'architecture') **Tags Namespace** - Tag-based filtering: - tags.name (tag key) - tags.value (tag content) VQL supports standard logical operators (AND, OR) and specialized functions: - Pattern Matching: LIKE and NOT LIKE for substring searches - Comparisons: IN/NOT IN for list evaluation; !=, <, >, <=, >= for values - Metadata Queries: >> operator for resource metadata (e.g., resources.metadata->>'architecture') VQL Representation of Resource Types: | Provider | VQL Representation | Friendly Name | |---|---|---| | AWS | aws_auto_scaling_group | Auto Scaling Group | | AWS | aws_cloudtrail | CloudTrail | | AWS | aws_cloudwatch_log_group | CloudWatch Log Group | | AWS | aws_db_instance | RDS Instance (NOT aws_rds_instance) | | AWS | aws_db_snapshot | RDS Snapshot (NOT aws_rds_snapshot) | | AWS | aws_docdb_cluster_instance | DocumentDB Cluster Instance | | AWS | aws_dynamodb_table | DynamoDB Table | | AWS | aws_ebs_volume | EBS Volume | | AWS | aws_instance | EC2 Instance (NOT aws_ec2_instance) | | AWS | aws_ec2_managed_prefix_list | EC2 Managed Prefix List | | AWS | aws_ec2_reserved_instance | EC2 Reserved Instance | | AWS | aws_ecs_service | ECS Service | | AWS | aws_ecs_task_definition | ECS Task Definition | | AWS | aws_egress_only_internet_gateway | Egress-Only Internet Gateway | | AWS | aws_eip | Elastic IP | | AWS | aws_elasticache_cluster | ElastiCache Cluster | | AWS | aws_elasticsearch_domain | Elasticsearch Domain | | AWS | aws_flow_log | Flow Log | | AWS | aws_glacier_vault | Glacier Vault | | AWS | aws_instance_snapshot | EC2 Instance Snapshot (NOT aws_ebs_snapshot) | | AWS | aws_internet_gateway | Internet Gateway | | AWS | aws_kms_key | KMS Key | | AWS | aws_lambda_function | Lambda Function | | AWS | aws_lb | Load Balancer | | AWS | aws_nat_gateway | NAT Gateway | | AWS | aws_rds_reserved_instance | RDS Reserved Instance | | AWS | aws_redshift_cluster | Redshift Cluster | | AWS | aws_s3_bucket | S3 Bucket | | AWS | aws_savings_plan | Savings Plan | | AWS | aws_secretsmanager_secret | Secrets Manager Secret | | AWS | aws_vpc | VPC | | AWS | aws_vpc_endpoint | VPC Endpoint | | AWS | aws_vpn_gateway | VPN Gateway | Example VQL queries: - Multi-provider: (resources.provider IN ('aws', 'gcp')) - Regional: (resources.provider = 'aws' AND resources.region = 'us-east-1') - Resource type: (resources.provider = 'aws' AND resources.type = 'aws_instance') - Metadata: (resources.provider = 'aws' AND resources.metadata->>'architecture' = 'x86_64') - Tags: (resources.provider = 'aws' AND tags.name = 'environment' AND tags.value = 'production') - Untagged resources: (resources.provider = 'aws' AND tags.name = NULL) Set include_cost to true to get cost breakdowns by category for each resource. Use the page parameter starting with 1 for pagination. Resources include metadata specific to their type (EC2 instances show instance type, EBS volumes show size, etc.). Each resource has a unique token that can be used to get more details or link to the Vantage Web UI.
List all recommendation views available in the Vantage account. Recommendation views are saved filters for cost optimization recommendations. Use the page value of 1 to start. The title of a recommendation view is a good way to understand what optimization scope it represents. The token of a recommendation view is its unique identifier and can be used to link the user to the view in the Vantage Web UI. Build the link like this: https://console.vantage.sh/go/<token> The workspace token, date range, providers, accounts, regions, and tag fields provide additional context about which recommendations are included in the view.
List all cost optimization recommendations available in the Vantage account. Recommendations are AI-powered suggestions that help identify opportunities to reduce costs and optimize cloud spending across your infrastructure. Use the page value of 1 to start pagination. Recommendations include various types such as: - EC2 rightsizing (resize overprovisioned instances) - Unused financial commitments (unused Reserved Instances or Savings Plans) - Idle resources (running but unused instances, volumes, load balancers) - Storage optimization (EBS volume type recommendations) - Reserved Instance and Savings Plan purchase recommendations Each recommendation includes: - Potential cost savings amount - Description of what can be optimized - Provider and service information - Number of resources affected - Current status (open, resolved, dismissed) Recommendations can be filtered by: - Status (open shows active recommendations, resolved shows implemented ones, dismissed shows ignored ones) - Cloud provider via provider (single) or provider_ids (multiple; requires workspace_token) — only use these when the user explicitly specifies cloud providers; do not infer or default to all providers - Specific workspace via workspace_token - Provider account ID via provider_account_id (single) or account_ids (multiple; requires workspace_token) - Billing account via billing_account_ids (requires workspace_token) - Region via regions (requires workspace_token) - Tag key/value pair via tag_key + tag_value (both required together; requires workspace_token) — use this when users ask about recommendations for a specific virtual tag, e.g. "recommendations for department=engineering" - Date range via start_date + end_date in YYYY-MM-DD format (both required together; requires workspace_token) - Minimum monthly potential savings via min_savings - Recommendation type via type (case-insensitive fuzzy matching; e.g. "AWS recommendations" -> type=aws; "EC2 rightsizing" -> type=aws:ec2:rightsizing) The token of each recommendation can be used with other recommendation tools to get detailed information and see specific resources affected. For users to view and manage recommendations in the Vantage Web UI, they can visit https://console.vantage.sh/recommendations
List scenario-model ReportForecasts for a Cost Report. ReportForecasts assign ScenarioModels (and optionally a BusinessMetric) to a Cost Report for planning views. Use page 1 when calling this tool for the first time. Keep calling with pagination.nextPage until pagination.hasNextPage is false when listing all forecasts. The token of a ReportForecast can be used with get-report-forecast, update-report-forecast, and delete-report-forecast. Requires Scenario Models (Enterprise). A 403 means the account is not entitled.
List Report Notifications available in the Vantage account. Report Notifications are scheduled deliveries of Cost Report summaries to users, Slack channels, or Microsoft Teams channels. Use this tool when a user asks to list, show, view, or find scheduled report notifications or recurring Cost Report summaries. Use the page value of 1 to start. Do not use this for Cost Alerts, budget alerts, threshold alerts, or spend-limit notifications. Cost Alerts are threshold-based spending alerts; Report Notifications are scheduled report deliveries.
List available columns for a resource type. The resource_type is a required parameter, and must be a valid VQL resource type name.
List all resource reports available. Resource reports are already created reports authored by a user in Vantage. When you first call this function, use the "Page" parameter of 1. The 'Title' of a report is a good way to know what the report is about. The 'filter' of a report also gives clues to the data it provides. The 'token' of a report is a unique identifier for the report. It can be used to generate a link to the report in the Vantage Web UI. If a user wants to see a report, you can link them like this: https://console.vantage.sh/go/<token>
List ScenarioModels available to the current Vantage API token. ScenarioModels define future-cost adjustments (dollar or percent) that can be assigned to Cost Report forecasts via report-forecast tools. Use page 1 when calling this tool for the first time. If the user asks for all ScenarioModels, keep calling with pagination.nextPage until pagination.hasNextPage is false. The token of a ScenarioModel can be used with get-scenario-model, update-scenario-model, delete-scenario-model, and create-report-forecast / update-report-forecast. Requires Scenario Models (Enterprise). A 403 means the account is not entitled.
List values for a tag key. The argument is `key` (the tag key name); the API response fields use `tag_value`. Requires integration settings permission; callers without it receive 403 from the API.
List tags that can be used to filter costs and cost reports. Tags are associated with one or more Cost Providers. Tags can be edited in the Vantage Web UI, or have further details displayed there. Link a user to the tag page like this: https://console.vantage.sh/settings/tags?search_query=<tag> Requires integration settings permission; callers without it receive 403 from the API. Each tag in the response uses the field `tag_key` (not `key`).
Retrieve the unit costs for a given CostReport, with optional paging, date filters, and ordering.
Lists or searches the Virtual Tags (Virtual Tag Configs) the current API token can access, including every mapping/value. Use this to discover config and value tokens or find a tag by key.
List all Workspaces available to the authenticated API token. Workspaces are isolated environments within Vantage for organizing cost data and access control across teams. Use get-myself to see the user's default workspace. Use get-workspace to retrieve details for a specific workspace.
Query for costs in a Vantage Account. These are independent of a cost reports. Use Vantage VQL to structure a query. Queries must be scoped to a Workspace. Use the get-myself tool to know about available workspaces, and the get-cost-integrations tool to know about available cost providers. If the user didn't tell you a workspace it is best to ask them than to guess it. It's best to set a date range of 30 days unless the user specifically wants to query for a longer time period. When a user asks for data from an account, use the "get-cost-provider-accounts" tool to match a name to an account. With that result, always use the account_id in the account_id parameter for this tool. Here is some more detailed info on using VQL: All costs originate from a Cost Provider (generally a cloud company like AWS, Azure, Datadog) and then filter on a service that they provide (like EC2, S3, etc). A cost provider is required on every VQL query. VQL is always in parenthesis. Always use single quotes around names that are being queried. To query on a cost provider, use this syntax: (costs.provider = '<provider name>'). The provider name must come from the list-cost-providers tool. To query on a cost service, use this syntax: (costs.provider = '<provider name>' AND costs.service = '<service name>'). For AWS, costs.service must be a CUR identifier (e.g. 'AmazonEC2', 'AmazonVPC', 'AWSDirectConnect'). Use vql_info to resolve aliases — not display names from list-cost-services. If a query returns no rows, run one broad probe query first (provider only, date_bin=month, wide date range) to learn available months and service identifiers before retrying with a narrower filter. For month-over-month comparisons, span both months in start_date/end_date with date_bin=month and settings_show_previous_period=true instead of separate queries per month. Prefer one query-costs call with all needed groupings (e.g. service, account_id, tag:<key>) over multiple calls that only change groupings. You can only filter against one cost provider at a time. If you want to query for costs from two providers, you need to use the OR operator. Example: ((costs.provider = 'aws') OR (costs.provider = 'azure')) You can otherwise use the IN system to compare against a list of items, like this: (costs.provider = 'aws' AND costs.service IN ('AWSQueueService', 'AWSLambda')) To filter within a cost provider, keep the cost provider part and add a AND section, example: (costs.provider = 'aws' AND costs.service = 'AmazonRDS') Many costs have tags on them. A tag is a "name" and one or more values. To find an AWS cost that has a tag of "environment" the value "production", use this syntax: (costs.provider = 'aws' AND tags.name = 'environment' AND tags.value = 'production') You can also query for any value of the "environment" tag, like this: (costs.provider = 'aws' AND tags.name = 'environment') Items without a tag can also be filtered, example: (costs.provider = 'aws' AND tags.name = NULL) Parenthesis can be nested. Here we surround an OR clause to look for either of two values for a tag: (costs.provider = 'aws' AND tags.name = 'environment' AND (tags.value = 'dev' OR tags.value = 'staging')) A user can have more than one provider account. They can filter on provider accounts if they supply you with the account id. Example: (costs.provider = 'aws' AND costs.account_id = '1000000717') You can also combine top-level queries to find for two providers: ((costs.provider = 'datadog') OR (costs.provider = 'azure')) Some cost providers operate in a specific region, you can filter using the costs.region field. Example: (costs.provider = 'aws' AND costs.region = 'us-east-1') Note that when users want to query a Custom Provider, that has a special case. When doing a VQL query for custom provider, use the 'token' you get back from the 'list-cost-integrations' tool. Here is an example, where the token of the custom provider is "accss_crdntl_07171984": (costs.provider = 'custom_provider:accss_crdntl_07171984') The DateBin parameter controls the time granularity of returned results. When DateBin=day you get a record for each service spend on that day. For DateBin=week you get one entry per week, with the accrued_at field set to the first day of the week, but the spend item represents spend for a full week. Same with DateBin=month, each record returned covers a month of data. This lets you get answers with processing fewer records. If omitted, DateBin defaults to day. Cost settings (credits, refunds, discounts, tax, amortization, etc.) default to the workspace's default report settings. Only provide these parameters if you need to override those defaults. Use settings_aggregate_by to choose the metric: cost (default), usage, or count. When aggregate_by is count, the response includes total_count and counts (date-binned distinct Group By permutation counts for the full requested period).
Queries aggregated network flow log data (costs and bytes). Pass a saved report token or an ad hoc filter. Unlike create/update, custom date ranges use start_date and end_date without date_interval=custom.
Submit feedback on using the Vantage MCP Server. Ask the user if they'd like to provide feedback any time you sense they might be frustrated. Stop suggesting if they say they're not interested in providing feedback.
Update the title, date, message, or associated Cost Reports of an existing Annotation. Providing report_tokens replaces all existing Report associations. Use list-annotations to find the annotation_token.
Updates an existing anomaly alert by its token. Use this to change the status of an anomaly alert (e.g. to archive or ignore it) and optionally provide feedback.
Updates an existing Billing Rule. You can update the title, dates, and type-specific fields. Type-specific fields: - Exclusion: charge_type - Adjustment: percentage, service, category - Charge/Credit: service, category, sub_category, amount, start_date - Custom: sql_query
Updates an existing Budget. You can update the name, linked Cost Report, child Budget tokens for hierarchical budgets, period cadence, or budget periods.
Update an existing Budget Alert's monitored Budgets, percentage threshold, monthly time window, or recipients. Budget Alerts monitor Budget objects.
Updates an existing Canvas. You can update the title, the prompt, or both. Updating the prompt triggers an asynchronous refresh to regenerate the canvas data.
Updates an existing Cost Alert. Use to change the title, threshold, interval, monitored Cost Reports, or notification destinations. Use list-cost-alerts or get-cost-alert to find the cost_alert_token. Do not use this for Report Notifications or recurring Cost Report delivery.
Updates an existing Cost Report. Use to change the title, VQL filter, groupings, date range, chart type, folder, report settings, or attached business metrics. Do not use create-cost-report (creates a new report) or get-cost-report (reads without changing). Use list-cost-reports or get-cost-report to find the cost_report_token.
Updates an existing Dashboard. You can update the title, widgets, saved filters, and date range settings.
Updates an existing Financial Commitment Report. Use this to change the report title, VQL filter, date range, date bucket, on-demand costs scope, or grouping dimensions. Date ranges can be set with either: - date_interval, or - start_date and end_date. Unless date_interval is "custom", date_interval is incompatible with start_date and end_date. VQL filters use financial commitment fields and should follow Vantage Query Language syntax. Additional VQL documentation is available at https://docs.vantage.sh/vql.
Updates a Folder's title, parent, or SavedFilter tokens. Folder type cannot be changed after creation.
Updates a saved Network Flow Report. Use list-network-flow-reports to discover tokens.
Updates an existing Recommendation View. Use this to change the view title or the filters applied to saved recommendation views. Filters can be scoped by provider, billing account, cloud account, region, tag key/value, and recommendation creation date range. Dates must be YYYY-MM-DD formatted. Tag filters should use tag_key and tag_value together.
Update a scenario-model ReportForecast. Providing scenario_model_tokens replaces the assigned models. Send business_metric_token as null to clear the BusinessMetric. Use set_as_default to make this the Cost Report default forecast. Requires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot update the Cost Report.
Updates an existing Report Notification in Vantage. Use this tool to change a scheduled Cost Report notification's title, Cost Report, recipients, Slack or Microsoft Teams channels, delivery frequency, or tracked change type. Report Notifications deliver recurring Cost Report summaries on a daily, weekly, or monthly cadence. Do not use this for Cost Alerts, budget alerts, threshold alerts, or spend-limit notifications. Cost Alerts manage spend thresholds; Report Notifications manage scheduled report delivery.
Updates an existing Resource Report. Use to change the title, VQL filter, table columns, or folder. Do not use create-resource-report (creates a new report) or get-resource-report (reads without changing). Use list-resource-reports or get-resource-report to find the resource_report_token.
Update an existing ScenarioModel. Providing periods replaces the full period set. Use null for priority, provider, service, or period end_at to clear those values. Requires Scenario Models (Enterprise). A 403 means the account is not entitled or the caller cannot update the model.
Updates an existing Virtual Tag's config-level settings or complete ordered mappings/values. Supplying values replaces the entire list in that order, and an empty array clears it; use the value-level tools to append, partially edit, or delete one mapping.
Partially edits one mapping/value in an existing Virtual Tag Config. Omitted fields remain unchanged, display_name set to null clears it, and this tool cannot reorder values.
Update an existing Workspace. You can update the name, currency conversion settings, currency code, and exchange rate date method.
The Vantage MCP integration connects your Dench AI CRM directly to Vantage MCP, so agents can read and act on your Vantage MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
127 actions are available for agents to invoke on your behalf. Every call runs through Vantage MCP's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Vantage MCP and click Connect — you'll authorize access through Vantage MCP's own sign-in flow. No API keys or code required.
Ask an agent to use Vantage MCP in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Vantage MCP integration connects your AI CRM to Vantage MCP, so AI agents can work with your Vantage MCP data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Vantage MCP integration currently exposes 127 actions, including Create-annotation, Create-billing-rule, Create-budget, Create-budget-alert, Create-canvas, and Create-cost-alert. Agents invoke them on your behalf from chat or from automations.
No. You connect Vantage MCP from your Dench workspace using Vantage MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Vantage MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Vantage MCP connection from your workspace settings at any time.