startup-finance-metrics
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| computeFinancialMetricsA | Computes startup financial metrics from structured data. Args: inputs_json: A JSON string containing financial inputs. Preferred: pre-categorized values like 'monthly_revenue', 'monthly_opex', 'cogs', 'sales_marketing_spend', 'business_type', etc. Also accepts a raw 'bank_csv' blob as fallback (basic totals only). Returns: JSON string containing computed metrics and missing inputs diagnostics. |
| generateFinancialReportA | Generates a single unified HTML + Markdown financial report and saves them to disk. Args:
metrics_json: JSON string. Two accepted shapes:
1. Single-month: the direct output from |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyzeFinances | Prompt template to analyze startup finances like an expert CFO. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_coaching_templates | Provides financial coaching templates and advice rules. |
| get_validation_rules | Provides strict validation rules for the metrics engine. |
| get_worked_example | Provides a worked example of financial metric computation. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one computes financial metrics from input data, the other generates a report from those metrics. No overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern using camelCase: computeFinancialMetrics and generateFinancialReport. No mixing of conventions.
With only 2 tools, the server is minimally scoped. While the tools cover the core workflow, the count is at the lower boundary of what is reasonable for a finance metrics domain.
The tools cover computing metrics and generating reports, but lack operations for data input management, historical tracking, or comparisons. Some notable gaps exist.