Skip to main content
Glama

事業計画の前提チェック / Business plan assumption check

check_business_plan_assumptions
Read-onlyIdempotent

Review unit economics using acquisition cost, monthly customer revenue, gross margin and churn; optionally include growth and cash runway pairs. Returns lifetime gross profit, acquisition-cost multiple, payback months, optional projections and general reference cautions. 計画の前提を見直すために獲得単価・月売上・粗利率・月解約率と任意の成長・資金を入力し、粗利・倍率・回収月数・注意点を返します。 Set language to 'en' for English output.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customer_acquisition_cost": "<customer_acquisition_cost>",
      "monthly_revenue_per_customer": "<monthly_revenue_per_customer>",
      "gross_margin_percent": "<gross_margin_percent>",
      "monthly_churn_percent": "<monthly_churn_percent>"
    },
    "name": "check_business_plan_assumptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoOutput language: ja (default) or en. / 出力言語。既定は日本語(ja)、英語はen。ja
cash_on_handNoAvailable cash, 0–1 trillion; same currency unit as all other monetary inputs. Specify together with monthly_burn. / 手元資金。0〜1兆。金額はすべて同じ通貨単位。monthly_burnと対で指定。
monthly_burnNoMonthly net cash outflow, 0–1 trillion; same currency unit as all other monetary inputs. Specify together with cash_on_hand. / 月の純資金流出。0〜1兆。金額はすべて同じ通貨単位。cash_on_handと対で指定。
growth_monthsNoGrowth duration, 1–60 months; specify together with monthly_growth_percent. / 成長の月数(1〜60)。monthly_growth_percentと対で指定。
gross_margin_percentYesGross margin percentage, 0–100; 10 means 10%. / 粗利率。0〜100の百分率。10は10%。
monthly_churn_percentYesMonthly churn percentage, greater than 0 and at most 100; 10 means 10%. / 月解約率。0より大きく100以下の百分率。10は10%。
monthly_growth_percentNoRelative monthly growth percentage, -100–1000; 10 means 10%. Specify together with growth_months. / 月の相対成長率。−100〜1000の百分率。10は10%。growth_monthsと対で指定。
customer_acquisition_costYesAcquisition cost per customer, 0–1 trillion; all monetary inputs use the same currency unit. / 顧客獲得単価。0〜1兆。金額はすべて同じ通貨単位。
monthly_revenue_per_customerYesMonthly revenue per customer, 0–1 trillion; all monetary inputs use the same currency unit. / 顧客1人の月売上。0〜1兆。金額はすべて同じ通貨単位。

Output Schema

NameRequiredDescriptionDefault
summaryYesCalculation assumptions and interpretation. / 計算の前提と結果の説明。
warningsYesData cautions and general reference thresholds. / データの注意点と一般的な目安。
payback_monthsYesAcquisition cost divided by monthly gross profit, or null. / 獲得単価を月粗利で割った回収月数。算出不可はnull。
growth_multiplierNoCompound growth multiplier over the specified duration. / 指定月数の複利成長倍率。
cash_runway_monthsNoCash divided by monthly net cash outflow, or null. / 手元資金を月の純資金流出で割った月数。算出不可はnull。
monthly_gross_profitYesMonthly gross profit per customer, in the input currency unit. / 入力と同じ通貨単位での顧客1人の月粗利。
lifetime_gross_profitYesLifetime gross profit per customer, in the input currency unit. / 入力と同じ通貨単位での顧客生涯の粗利。
acquisition_cost_multipleYesLifetime gross profit divided by acquisition cost, or null. / 生涯粗利を獲得単価で割った倍率。算出不可はnull。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds genuine context by noting the paired optional inputs and that outputs include 'general reference cautions' (framing the result as advisory, not a verified forecast), but it says nothing about how sensitive results are to inputs or the limits of the model.

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?

The definition is front-loaded with the purpose, then inputs, then outputs, in three compact sentences. The Japanese mirror and the trailing language instruction are necessary for a bilingual tool rather than filler; nothing is wasted, though the output enumeration partially duplicates the output schema.

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?

With an output schema present, the description covers the remaining needs: inputs, optional pairs, and the advisory nature of the cautions. For a read-only, deterministic calculation over 4 required plus 5 optional parameters, nothing essential is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents ranges, percent conventions and the cash_on_hand/monthly_burn and growth/monthly_growth_percent pairing rules. The description restates the same field list and pairing without adding format or interpretation guidance beyond the schema, so this is the baseline 3.

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

Purpose4/5

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

The description states a specific verb and resource ('Review unit economics') and enumerates the exact drivers used (acquisition cost, monthly customer revenue, gross margin, churn) plus the computed outputs (lifetime gross profit, acquisition-cost multiple, payback months). It is distinguishable from the sibling tools (funnel diagnosis, reverse-KPI targeting) by being a unit-economics assumption check, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the description tells you what to supply and that growth/cash pairs are optional, which implies 'use this to sanity-check plan assumptions.' There is no explicit when-to-use versus when-not guidance, nor any mention of when an agent should instead reach for diagnose_funnel_bottleneck or reverse_kpi_from_revenue_target.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources