Skip to main content
Glama
Sign In
togaf10_EAP_MCP

togaf10_EAP_MCP

by Waganawa-Megumin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Next best action

next_best_action

Diagnose a stored engagement to receive 3-5 prioritized actions, each with its rationale, completion condition, and tool to use.

Instructions

保存済みの案件の状態(フェーズ・関係者・リスク・アクション・作業パッケージ・移行状態)を診断し、優先度順に 3〜5 個の具体的な行動を、根拠・完了条件・使うツールつきで返す。「第 7 章を読め」ではなく「今週これをやれ」を返すためのツール。 / Diagnose the stored engagement — phases, stakeholders, risks, actions, work packages, transitions — and return 3-5 concrete actions in priority order, each with the reason it is next, the condition that means it is done, and the tool to use.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "next_best_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo出力言語 / Output languageboth
horizonNo対象期間 / Planning horizon: today, week (default), or monthweek

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden, and it does well: it discloses that the tool analyzes stored engagement state, returns 3-5 actions, includes evidence/completion conditions/tool recommendations, and is prescriptive ('do this this week') rather than theoretical. It does not explicitly state read-only behavior, but 'diagnose and return' implies no mutation.

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 bilingual description is compact and front-loaded: the first clause states the core function, followed by output details and a clarifying intent phrase. The 'not chapter 7 but this week' sentence is illustrative rather than redundant, though the Japanese/English duplication occupies extra space.

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?

Given the absence of an output schema, the description sufficiently characterizes the return value (3-5 prioritized actions with reason, completion condition, and tool). It also signals the prerequisite that an engagement must already be stored/saved. It could be more explicit about error conditions or behavior when no stored engagement exists, but is otherwise complete.

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% and both parameters are self-described enums with defaults (lang, horizon). The description adds no additional parameter guidance, which is acceptable because the schema already handles parameter semantics.

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 states a specific action: diagnose the stored engagement across named dimensions and return 3-5 concrete, prioritized actions with reason, completion condition, and tool. This is far more specific than a generic 'next best action' label and clearly distinguishes it from sibling planning/diagnostic 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?

The phrasing '今週これをやれ' implies it is for users who want actionable next steps rather than generic guidance, but it never explicitly states when to choose this over siblings like prioritize_work_packages, assess_readiness, or check_engagement_health. No exclusions or alternative routing are provided.

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

Deploy Server

Other Tools