Skip to main content
Glama

売上目標からの逆算 / Revenue target KPI planning

reverse_kpi_from_revenue_target
Read-onlyIdempotent

Plan required volumes from a positive revenue target, unit price, 1–36 months and 1–8 ordered conversion rates. The target is for the whole period, not monthly. Returns rounded-up stage requirements, monthly averages and upstream reductions when each rate improves by 10% relatively. 売上目標の達成に必要な人数を整理するために目標・単価・期間・上流からの率を入力し、段ごとの必要数と改善時の減少数を返します。 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": {
      "target_revenue": "<target_revenue>",
      "unit_price": "<unit_price>",
      "rates": "<rates>"
    },
    "name": "reverse_kpi_from_revenue_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratesYesOrdered, connected stage conversion rates; no repeated stages. / 上流から連続する段の通過率。同じ段の繰り返しは不可。
languageNoOutput language: ja (default) or en. / 出力言語。既定は日本語(ja)、英語はen。ja
unit_priceYesRevenue per sale, greater than 0 and at most 1 trillion; all monetary inputs use the same currency unit. / 成約単価。0より大きく1兆以下。金額はすべて同じ通貨単位。
period_monthsNoWhole-period duration in months, 1–36. / 対象期間の月数(1〜36)。
target_revenueYesRevenue target for the whole period, not monthly; greater than 0 and at most 1 trillion. All monetary inputs use the same currency unit. / 期間全体の売上目標(月額ではない)。0より大きく1兆以下。金額はすべて同じ通貨単位。

Output Schema

NameRequiredDescriptionDefault
stagesYesRequired counts by stage. / 段ごとの必要人数。
summaryYesCalculation assumptions and interpretation. / 計算の前提と結果の説明。
improvementsYesIndependent improvement scenarios ranked by gain or reduction. / 増分または減少数の大きい順の独立した改善試算。
period_monthsYesWhole-period duration in months. / 対象期間の月数。
required_salesYesSales required for the whole period, rounded up. / 期間全体に必要な成約数(切り上げ)。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond them: whole-period target semantics, rounded-up stage requirements, monthly averages, and upstream reductions when each rate improves by 10% relatively. It does not cover error handling, but with annotations and an output schema this is reasonably transparent.

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 English portion is front-loaded and logically ordered: purpose, key semantics, return behavior, then language instruction. The Japanese translation duplicates content and some schema constraints are restated, but the definition remains readable and appropriately sized.

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?

For a five-parameter planning tool with full schema coverage, annotations, and an output schema, the description covers purpose, input context, return behavior, and output language. No critical agent-facing information 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 ranges, defaults, enums, and nested rate fields are already documented. The description reinforces the whole-period target and language selection but adds little syntax or interaction detail beyond what the schema provides. This fits the baseline 3 when the schema does the heavy lifting.

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?

The description opens with a specific verb-resource pair, 'Plan required volumes from a positive revenue target,' and names the exact inputs and output behavior. It also clarifies that the target is whole-period rather than monthly, which prevents a key ambiguity. This makes it clearly distinct from sibling diagnostics and assumption-checking tools.

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?

It gives a clear planning context: calculating required volumes or headcount needed to hit a revenue target using target, price, period, and upstream conversion rates. It does not explicitly compare against sibling tools or state when not to use it, but the usage context is sufficiently clear without exclusions.

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