Skip to main content
Glama

Consult on a situation

consult

Describe a situation in free text to receive a TOGAF ADM-based diagnosis: relevant phases, techniques, deliverables, actions, and questions. Stated constraints tailor the advice; topics marked off the table are excluded.

Instructions

アーキテクチャ上の状況を自由記述で渡すと、TOGAF ADM の観点で「見立て・着目すべきフェーズ・推奨技法・作るべき成果物・推奨アクション・ステークホルダーへの確認質問」を返す。予算・期限・経営の関与・体制などの条件を本文から読み取り、助言の中身を条件に合わせて変える。「やらないことに決まった」話題は見立てから外す。 / Describe a situation in free text and get a TOGAF-based read: diagnosis, relevant ADM phases, techniques, deliverables, actions, and questions to ask. Constraints stated in the text — budget, deadline, executive engagement, staffing — change what is recommended, and topics you say are off the table are excluded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNo出力言語 / Output languageboth
industryNo業界(任意)。対応業界なら見立てと質問に反映する / Industry, if relevant. Supported industries change the read and the questions. — 最大 300 文字 at most 300 characters
readingsNoあなた(呼び出し側)が既に読み取れている状況(任意)。このサーバーの読み取りは situation の文字列に対する正規表現でしかなく、会話の前のほうで言われたこと・添付文書に書いてあることは見えません。**会話から読み取れているなら、ここに渡すほうが正確です。** 渡した軸はそのまま採用し、渡さなかった軸だけをサーバーが本文から推定します(控え)。各軸には condition と evidence の 2 つを付けてください。evidence は「そう読み取った根拠」で、会話中の発言・文書の該当箇所・ページ番号など、利用者が誤読を正せる形で書きます(空欄・空白だけの evidence は受け付けません)。出力にはどちらが読んだのかを明記し、あなたの読み取りが situation の文面と食い違う場合は両方を並べて示します(片方を黙って捨てません)。 /What you have already read from the conversation (optional). This server only regex-matches the `situation` string, so anything said earlier in the conversation or written in an attached document is invisible to it. **If you can read it from the conversation, passing it here is more accurate.** Axes you pass are used as-is; axes you omit fall back to the server's own guess from the text. Give each axis both a `condition` and an `evidence`: the evidence is why you read it that way — the remark, the passage, the page number — written so the user can correct a misread (blank or whitespace-only evidence is rejected). The output states which side read what, and where your reading contradicts the `situation` text it shows both — neither side is dropped silently.
situationYes状況の自由記述(日本語/英語どちらでも可)。予算・期限・体制・経営の関与など、制約も一緒に書くほど助言が具体的になる / Free-text description of the situation. The more constraints you state — budget, deadline, staffing, executive engagement — the more specific the guidance. — 最大 20,000 文字 at most 20,000 characters
currentPhaseNo現在の ADM フェーズ ID(任意) / Current ADM phase id, if any — 最大 300 文字 at most 300 characters
Install Server

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden, and it does disclose meaningful behavior: constraints in the text (budget, deadline, executive engagement, staffing) change the recommendations, and topics marked off the table are excluded from the read. It does not describe its input-visibility limitation, but that is covered in the schema's readings parameter.

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 description is compact: two short sentences per language, with the output components front-loaded before the adaptive behavior. The bilingual duplication is mild and consistent with the lang=both default, so it does not harm structure.

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?

There is no output schema, so the description usefully enumerates the six returned components. The complex readings object is fully documented in the schema, and the description covers the core contract, leaving only sibling differentiation as a real gap.

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 every parameter, including the nested readings axes, has a description. The tool description adds no parameter-specific semantics beyond restating constraint categories that the situation schema already mentions, so the baseline of 3 is appropriate.

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 names a specific action — free-text situation in, TOGAF-based read out — and enumerates the concrete output components (diagnosis, phases, techniques, deliverables, actions, stakeholder questions). It is clear and useful, though it does not explicitly differentiate itself from related siblings such as next_best_action or assess_readiness.

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 description implies the use case: when an architectural situation needs a TOGAF-based read and the user can supply constraints in free text. It gives no when-not guidance and does not point to any sibling alternative, so an agent gets only implicit selection help.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Waganawa-Megumin/togaf10_EAP_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server