Skip to main content
Glama

Sophon Consulting

by consulting.sophon

Triage an AI opportunity

triage_ai_opportunity
Read-onlyIdempotent

Score one proposed AI workflow across bottleneck severity, value capture, integration readiness, and risk posture. Returns a deterministic go-deeper or hold recommendation and a handoff-ready Markdown artifact. Read-only; not for organization-wide readiness reviews or production rollout planning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lensesYes
followUpsNoUp to five questions ranked by how much their answers could change the decision.
confidenceNoOptional confidence override. The rubric supplies a conservative default.
requestedByNoOptional person or team requesting the triage.
workflowNameYesThe specific workflow being evaluated.
decisionContextYesThe concrete decision this triage will inform.
canAnswerTopFollowUpInOneBusinessDayNoNeeded only when the total is 10-13: whether the highest-impact follow-up can plausibly be answered within one business day.

TDQS

A4.6/5.0
Behavior5/5

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

The description adds value beyond annotations by specifying the tool is read-only (consistent with readOnlyHint), deterministic (consistent with idempotentHint), and outputs a Markdown artifact with a go-deeper or hold recommendation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the main action, no redundancy, every word earns its place.

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 tool's complexity (7 params, nested objects) and no output schema, the description covers the main purpose, output, and scope. It omits optional parameters but schema covers them.

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 coverage is 86%, so baseline is 3. The description lists the four lenses but adds no additional parameter semantics beyond what the schema already provides.

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 clearly states the tool scores an AI workflow across four dimensions and returns a recommendation. It explicitly distinguishes from the sibling tool 'assess_ai_readiness' by stating it is not for organization-wide reviews.

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

Usage Guidelines5/5

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

The description explicitly states when to use (score a proposed AI workflow) and when not to use (not for org-wide readiness or production rollout), providing clear context and excluding alternatives.

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

All Sophon Consulting toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Both tools have clearly distinct purposes: one for organization-wide AI readiness assessment, the other for evaluating a single AI opportunity. Each description explicitly states what it is not for, eliminating ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern: 'assess_ai_readiness' and 'triage_ai_opportunity', making them predictable and easy to distinguish.

Tool Count5/5

With only 2 tools, the server is sharply focused on two key consulting activities—organizational readiness and individual opportunity assessment. This is an appropriate scope for the domain.

Completeness4/5

The tools cover the initial assessment and triage phases well, but there is a minor gap: no tool for follow-up actions or detailed implementation planning, which might be needed after the verdict.

Resources