Skip to main content
Glama
chaandannn

nable (finops-mcp)

set_business_metrics

Set revenue, user, cash, and burn metrics to link cloud costs to business outcomes. Enables trend tracking and explains cost changes.

Instructions

Store your business metrics so nable can connect cloud costs to business outcomes.

Call this once a month (or whenever metrics change) and nable will track trends over time and answer "so what?" when your cloud spend changes.

Args: arr_usd: Annual Recurring Revenue in USD (e.g. 1_200_000 for $1.2M ARR) mrr_usd: Monthly Recurring Revenue in USD. Use this OR arr_usd, not both. mau: Monthly Active Users dau: Daily Active Users paying_customers: Number of paying customers / accounts api_calls_monthly: Your product's API calls per month (not cloud API calls) employees: Total headcount custom_metrics: Any other metric as a dict, e.g. {"free_signups": 4200, "nps": 42} notes: Free-text context, e.g. "Post Series A, hired 8 engineers" metric_date: Date these metrics apply to (YYYY-MM-DD). Defaults to today. cash_on_hand_usd: Cash in the bank, in USD. Powers runway in get_unit_economics(). last_raise_amount_usd: Size of your last round, in USD. last_raise_date: Date of your last round (YYYY-MM-DD). monthly_opex_usd: Total monthly burn including payroll, in USD. Without this, runway is reported as "infra runway" (excludes payroll); with it, nable reports true company runway.

Calling this repeatedly for the same date MERGES: fields you omit keep their prior value, so you can set revenue one call and cash the next.

Examples: - "Set our MRR to $45,000 and MAU to 1,200" - "Update business metrics: ARR $2.4M, 340 paying customers, 8,200 MAU" - "Set cash on hand to $2.4M and monthly opex to $210k"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dauNo
mauNo
notesNo
arr_usdNo
mrr_usdNo
employeesNo
metric_dateNo
custom_metricsNo
last_raise_dateNo
cash_on_hand_usdNo
monthly_opex_usdNo
paying_customersNo
api_calls_monthlyNo
last_raise_amount_usdNo
Behavior5/5

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

Discloses key behavior: merging on repeated calls, default date (today), effect of monthly_opex_usd on runway calculation. No annotations exist, so the description fully carries this burden. No contradictions.

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

Conciseness4/5

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

Well-structured with purpose, usage, args, merging info, and examples. Front-loaded with key purpose. Slightly verbose but each section earns its place. Could condense arg descriptions slightly, but overall efficient.

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

Completeness5/5

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

Given high parameter count, no required params, merging behavior, and no output schema, the description is remarkably complete. Covers all necessary aspects for an agent to invoke correctly, including edge cases like parameter relationships and default values.

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?

With 0% schema description coverage, the description compensates fully by providing detailed explanations for all 14 parameters, including examples and usage notes (e.g., MRR vs ARR mutual exclusivity). Adds meaning far beyond the schema's property names/types.

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 states the tool stores business metrics to connect cloud costs to outcomes. Verb 'store' and resource 'business metrics' are explicit. Distinguishes from sibling audit/get tools as a write operation. Frequency guidance ('once a month') adds context.

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?

Gives explicit when to call ('once a month or whenever metrics change') and merging behavior ('fields you omit keep prior value'). Does not explicitly state when not to use, but the context is clear and no alternative tool exists for setting metrics.

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