Skip to main content
Glama

assess_ai_readiness

Read-onlyIdempotent

Use when building an internal AI readiness assessment or comparing a team’s evidenced self-assessments. Returns transparent scores, response coverage and prioritised gaps; questionnaire mode returns the versioned questions.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes
generatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that output is 'transparent' and includes coverage and prioritised gaps, plus the mode-dependent return shape — useful but modest, with nothing on how gaps are prioritised or how weights affect scoring.

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, trigger condition first, behavior second. Every clause carries information (trigger, evidence requirement, return contents, mode split) with no filler.

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?

With an output schema present and full schema coverage, the description need not detail return values, yet it still sketches them helpfully. The only residual gap is that the scoring model (weights, thresholds) is unexplained, which matters for an assessment tool.

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%, so a 3 is the baseline, but the description earns more by disambiguating the confusing oneOf shape: it explains that the questionnaire branch returns versioned questions while the responses branch produces scores. It still says nothing about the format or weights parameters beyond their names.

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 pairs a specific resource ('internal AI readiness assessment') with concrete outputs ('transparent scores, response coverage and prioritised gaps') and names a second capability ('questionnaire mode returns the versioned questions'). It is clearly an assessment/scoring tool, but it never contrasts itself with the scoring-adjacent siblings like score_delivery_health.

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

Usage Guidelines4/5

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

'Use when building an internal AI readiness assessment or comparing a team's evidenced self-assessments' gives an explicit trigger condition, including the notable constraint that responses must be evidenced. It stops short of when-not-to-use guidance or naming an alternative tool.

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.