Skip to main content
Glama

Sophon Consulting

by consulting.sophon

Assess AI readiness

assess_ai_readiness
Read-onlyIdempotent

Assess an organization's readiness to run AI in production across five dimensions (data readiness, workflow ownership, governance and controls, delivery capacity, executive sponsorship), each scored 1-5 with evidence or marked unknown, plus classified candidate use cases. Returns a deterministic verdict — Ready, Ready with conditions, Not yet ready, or Insufficient evidence (thresholds: ready needs no dimension below 3; 2+ dimensions at 2 or below is not yet ready) — with a handoff-ready Markdown assessment. Read-only; not for triaging a single AI idea (use triage_ai_opportunity).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
risksNoOptional risk register entries; scoring gaps should each become one.
useCasesYesCandidate AI use cases, each classified start-now, prepare-first, or defer.
dimensionsYesAll five readiness dimensions, each scored 1-5 with evidence, or marked unknown.
sequencingNoOptional 30-60-90 day sequencing recommendation.
preparedForNoOptional sponsor or requester the assessment is prepared for.
organizationNameYesThe organization or team being assessed.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations (readOnlyHint=true, idempotentHint=true) are consistent with description. Description adds detailed behavioral context: deterministic verdict, threshold logic, and that it's read-only, beyond what annotations provide.

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?

Description is well-structured with front-loaded purpose, detailed thresholds, and sibling reference. Slightly verbose but every sentence adds value; could be more concise but not excessively long.

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?

Despite no output schema and complex nested inputs, the description covers the assessment logic, verdict determination, and output format (Markdown). It is thorough enough for an AI to understand tool behavior and prerequisites.

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

Parameters4/5

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

Schema coverage is 100% and description does not reiterate parameters, but it adds meaning by explaining the dimensions (data readiness, workflow ownership, etc.) and the scoring/verdict logic, which helps the AI understand how to use the input schema effectively.

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?

Description clearly states it assesses an organization's AI readiness across five dimensions, each scored 1-5, with a deterministic verdict and Markdown output. Distinguishes from sibling tool triage_ai_opportunity by specifying when not to use it.

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?

Explicitly states not for triaging a single AI idea and directs to sibling tool triage_ai_opportunity, providing clear when-to-use and when-not-to-use guidance.

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