Skip to main content
Glama

業務自動化の削減効果試算

estimate_automation_savings
Read-onlyIdempotent

Estimate monthly and annual time savings and JPY equivalents from task assumptions; rank tasks by time saved. Estimates do not guarantee outcomes. 業務ごとの前提から削減時間と円換算を試算します。

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": {
      "tasks": "<tasks>"
    },
    "name": "estimate_automation_savings"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksYes
hourly_cost_jpyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish that this is a safe, idempotent, non-destructive, closed-world read operation. The description adds useful context by noting that estimates are not guarantees and that tasks are ranked by time saved, but it does not explain calculation assumptions, defaults, or rounding behavior.

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 short and front-loaded, stating the core estimate and ranking behavior before the caveat. The Japanese sentence largely duplicates the English content, which is slightly redundant but not harmful for selection.

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

Completeness3/5

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

The tool has a nested task array with several defaults and an output schema, so the description does not need to explain return values. It gives a clear high-level purpose and caveat, but it leaves out parameter meanings and calculation assumptions that would help an agent use it correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden of explaining parameters, but it only refers generically to 'task assumptions' and 'JPY equivalents.' It does not clarify the nested task fields, defaults such as automatible_ratio or hourly_cost_jpy, or the 30-task limit.

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: estimate monthly and annual time savings and JPY equivalents from task assumptions, plus ranking by time saved. It is clearly different in intent from drafting an automation spec, but it does not explicitly distinguish itself from the sibling tools.

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 by the phrase 'from task assumptions' and the ranking output, so an agent can infer this is for savings estimates when task-level assumptions exist. However, there is no explicit when-to-use or when-not-to-use guidance, and alternatives are not discussed.

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