Vantage

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.

Creates a cost alert based on the parameters specified. Cost alerts notify you when spending on one or more cost reports exceeds a specified threshold over a given interval.

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 Folder for organizing Cost Reports. Folders can be nested by specifying a parent_folder_token. SavedFilters can be applied to the Folder so that any Cost Report within it inherits those filters.

Create a Virtual Tag Config in Vantage.

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

Deletes a cost report by its token. This action is irreversible.

Deletes a Folder. Cost Reports within the Folder will not be deleted.

Gets a specific anomaly alert by its token.

Gets a specific cost alert by its token.

Get the list of Cost Provider Accounts that the current user has access to in their workspace and their names. This is useful for mapping IDs you have gotten from other endpoints to human-readable names, or if you need to get the ID of a Cost Provider Account to use in places. The account_id in this result can be passed as the account_id in VQL queries.

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 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 workspace for the user and can be used for queries unless told otherwise.

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 team with its token.

Return all Teams that the user has access to.

Return all Users that the user can see in the workspace.

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 for actions taken within the Vantage workspace. Audit logs are a chronological record of all changes and activities that occur in your workspace, providing a complete history of who did what, when, and what changed.

Audit logs track various types of actions including:

• Creating, updating, or deleting cost reports
• Modifying report settings, filters, or configurations
• Creating, updating, or deleting virtual tags
• Commitment actions taken manually or autonomously by the Finops Agent (autonomous cost optimization actions)

Each audit log entry contains:

• The user or service token (Team) that performed the action
• The action type (record_created, record_updated, record_destroyed)
• The object that was affected (cost report, virtual tag, commitment, etc.)
• The timestamp when the action occurred
• What values changed (before and after states)
• The source of the action (console, api, developer, finops_agent)
• A scoutAction boolean field that indicates if the action was taken by the Finops Agent (Scout), which is particularly relevant for commitment actions to distinguish agent-driven actions from human actions
• The workspace where the action took place

Use pagination via the "page" parameter starting with 1. The default limit is 100 results per page, which can be adjusted up to 1000.

Audit logs can be filtered by:

• User ID (to see actions by a specific person or service token (Team))
• Workspace token (to scope to a specific workspace)
• Action type (create, update, delete)
• Object type (cost_report, virtual_tag, recommendation_commitment)
• Object name or token (to track changes to a specific resource)
• Source (console, api, developer, finops_agent) - use "finops_agent" to filter for actions specifically taken by the Finops Agent
• Date range (start_date and end_date in ISO 8601 format)
• Audit log token (to retrieve a specific log entry)

Common use cases for audit logs include:

• Compliance and security auditing (tracking who made changes)
• Debugging issues (seeing what changed before a problem occurred)
• Change management (reviewing modifications to reports or configurations)
• Activity monitoring (understanding workspace usage patterns)
• Distinguishing between human actions and autonomous agent actions (via scoutAction field and finops_agent source filter)

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 all cost alerts available in the Vantage account. Cost alerts notify you when spending exceeds a specified threshold for a given cost report. Use the page value of 1 to start.

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 of cost services available to query for a given Workspace. Can be used to filter costs down to a specific service in VQL queries.

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 will let you get the information with fewer 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. Only use day/week if needed, otherwise DateBin=month is preferred, and month is the value set if you pass no value for DateBin.

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 Folders for organizing Cost Reports. Folders can be nested within other Folders via the parent_folder_token field. When you first call this function, use the "page" parameter of 1. The 'title' of a Folder describes its purpose. The 'saved_filter_tokens' field contains tokens of SavedFilters applied to Cost Reports within the Folder. The 'token' of a Folder can be used to generate a link in the Vantage Web UI: https://console.vantage.sh/go/<token>

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.

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 | | AWS | aws_db_snapshot | RDS Snapshot | | AWS | aws_docdb_cluster_instance | DocumentDB Cluster Instance | | AWS | aws_dynamodb_table | DynamoDB Table | | AWS | aws_ebs_volume | EBS Volume | | AWS | aws_ec2_instance | 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 | | 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_ec2_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 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 (aws, azure, gcp), specific workspace, provider account ID, and recommendation type. Prefer the type parameter when users ask for broad families (e.g. "AWS recommendations" -> type=aws; "EC2 rightsizing" -> type=aws:ec2:rightsizing). The type filter uses case-insensitive fuzzy matching on the recommendation type.

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

Tags can have many values. Use this tool to find the values and service providers that are associated with a tag.

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>

Retrieve the unit costs for a given CostReport, with optional paging, date filters, and ordering.

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>'). The service name must come from the list-cost-services tool. For the AWS provider, always use short names for the services. example: Use 'AmazonEC2' not 'Amazon Elastic Compute Cloud' and 'AmazonRDS' not 'Amazon Relational Database Service'. Again the list-cost-services tool in this MCP can give accurate service names. 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 will let you get the information with fewer 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. Only use day/week if needed, otherwise DateBin=month is preferred, and month is the value set if you pass no value for DateBin.

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.

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 a Folder for organizing Cost Reports. You can update its title, move it to a different parent Folder, or change its SavedFilter tokens.