Skip to main content
Glama
chaandannn

nable (finops-mcp)

subscribe_to_report

Create scheduled report subscriptions to automatically deliver FinOps reports to Slack channels or email addresses on a daily, weekly, or monthly basis.

Instructions

Create a scheduled report subscription. Reports are delivered automatically to Slack channels and/or email addresses on the configured schedule.

Args: name: Report name (e.g. "Platform Team Weekly") sections: List of sections to include. Options: spend, anomalies, scorecard, k8s, commitments, rightsizing, budgets, teams frequency: "daily", "weekday", "weekly", "monthly" (or use cron for custom) slack_channels: List of Slack channel IDs or names (e.g. ["#finops-alerts"]) email_addresses: List of email recipients team: Scope report to a specific team tag value provider: Scope report to a specific cloud provider (aws, azure, gcp) lookback_days: How many days of history to include (default 7) cron: Custom cron expression, overrides frequency (e.g. "0 8 * * 1-5")

Examples: - "Send me a daily Slack report with spend and anomalies to #finops" - "Set up a weekly report for the platform team every Monday" - "Create a monthly rightsizing report emailed to cfo@company.com" - "Subscribe to a daily digest in #cost-alerts with spend, anomalies, and budgets"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cronNo
nameYes
teamNo
providerNo
sectionsYes
frequencyNoweekly
lookback_daysNo
slack_channelsNo
email_addressesNo
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. Description discloses delivery methods and schedule but does not mention permissions, quotas, or side effects like overwriting existing subscriptions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with a clear purpose, parameter list, and multiple examples. No unnecessary text; every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive for a creation tool over 9 parameters and no output schema. Missing description of return value (e.g., subscription ID) but otherwise thorough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage. The description explains all 9 parameters with types, defaults, examples, and valid options, fully compensating for the schema gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly describes creating a scheduled report subscription with delivery to Slack/email. Distinguishes from siblings like cancel_report_subscription and list_report_subscriptions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear use cases and examples. Lacks explicit when-not conditions or alternatives like send_report_now for one-off reports.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chaandannn/finopsmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server